NetBSD-Bugs archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
bin/51505: amd in 7.0_STABLE can segfault
>Number: 51505
>Category: bin
>Synopsis: amd in 7.0_STABLE can segfault
>Confidential: no
>Severity: serious
>Priority: high
>Responsible: bin-bug-people
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Sun Sep 25 05:20:00 +0000 2016
>Originator: Mark Davies
>Release: NetBSD 7.0_STABLE
>Organization:
ECS, Victoria Uni. of Wellington, New Zealand.
>Environment:
System: NetBSD turakirae.ecs.vuw.ac.nz 7.0_STABLE NetBSD 7.0_STABLE (GENERIC) #6: Tue Mar 15 21:15:42 NZDT 2016 mark%turakirae.ecs.vuw.ac.nz@localhost:/local/SAVE/7_64.obj/src/work/7/src/sys/arch/amd64/compile/GENERIC amd64
Architecture: x86_64
Machine: amd64
>Description:
amd will occasionally segfault on various of our machines.
The backtrace on the core file is always:
#0 0x00007f7ff6900610 in strcmp () from /usr/lib/libc.so.12
#1 0x0000000000416387 in find_nfs_srvr ()
#2 0x0000000000407fd0 in amfs_nfsl_ffserver ()
#3 0x000000000040ff7c in locate_mntfs ()
#4 0x000000000040fff9 in find_mntfs ()
#5 0x0000000000406b50 in amfs_lookup_mntfs ()
#6 0x0000000000406e52 in amfs_generic_lookup_child ()
#7 0x0000000000411479 in nfsproc_lookup_2_svc ()
#8 0x000000000041062b in nfs_program_2 ()
#9 0x00007f7ff68c9401 in svc_getreq_common () from /usr/lib/libc.so.12
#10 0x00007f7ff68c9444 in svc_getreqset () from /usr/lib/libc.so.12
#11 0x0000000000410b59 in mount_automounter ()
#12 0x000000000041ba85 in main ()
The last thing amd syslogs prior to core dumping is something
like:
Sep 24 23:44:27 paramount amd[282]: check_pmap_up: failed to contact portmapper on host "XXX": RPC: Timed out
or:
Sep 25 06:17:24 homepages amd[282]: check_pmap_up: failed to contact portmapper on host "XXX": RPC: Timed out
Sep 25 06:17:24 homepages amd[282]: portmapper service not running on XXX
Sep 25 06:17:24 homepages amd[282]: NFS service not running on XXX
>How-To-Repeat:
run amd, automount some nfs filesesytems, wait for some
anomolous condition to occur :-(
>Fix:
Don't know, clearly its not handling some error case.
Some patch already in am-utils 6.2 may fix it.
>Unformatted:
Home |
Main Index |
Thread Index |
Old Index