Date: Sun, 07 Apr 2013 15:58:18 +0300 From: Daniel Braniss <danny@cs.huji.ac.il> To: Andriy Gapon <avg@FreeBSD.org> Cc: freebsd-stable@FreeBSD.org Subject: Re: panic: vm_fault_copy_wired: page missing Message-ID: <E1UOpAo-0006ee-UT@kabab.cs.huji.ac.il> In-Reply-To: <516066BF.90103@FreeBSD.org> References: <E1UO31d-000BgS-M9@kabab.cs.huji.ac.il> <516066BF.90103@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> on 05/04/2013 12:33 Daniel Braniss said the following:
> > The system is running FreeBSD-9.1-stable, and is dataless/diskless.
> > the culprit is mlockall(2) which is called from the automounter amd/am-utils,
> > commenting the call, eliminates the panic.
> >
> > I don't know when the problem surfaced, I was last hit by this
> > 2 years ago almost to the day - creepy.
> >
> > I can make this happen by first running firefox, and the trying some
> > command that involves the automounter.
> >
> > so is someone interested in fixing this?
>
> So, is there someone interested in properly reporting the problem first?
> :-)
since it seems to be happening only to me, I wasn't sure if it was a good idea
writing a long message with allot of info that noone would read :-)
so, in the meantime, some more info:
when the root file system is NOT via NFS all seems ok,
when the root is via NFS, no matter is amd is via NFS or not, it panics:
panic: vm_fault_copy_wired: page missing
cpuid = 1
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2a/frame 0xffffff814907a790
kdb_backtrace() at kdb_backtrace+0x37/frame 0xffffff814907a850
panic() at panic+0x1ce/frame 0xffffff814907a950
vm_fault_copy_entry() at vm_fault_copy_entry+0x28e/frame 0xffffff814907a9e0
vmspace_fork() at vmspace_fork+0x553/frame 0xffffff814907aa30
fork1() at fork1+0x328/frame 0xffffff814907aae0
sys_fork() at sys_fork+0x22/frame 0xffffff814907ab10
amd64_syscall() at amd64_syscall+0x540/frame 0xffffff814907ac30
Xfast_syscall() at Xfast_syscall+0xf7/frame 0xffffff814907ac30
--- syscall (2, FreeBSD ELF64, sys_fork), rip = 0x800edd36c, rsp =
0x7fffffffd0c8, rbp = 0 ---
#0 doadump (textdump=1) at /r+d/stable/9/sys/kern/kern_shutdown.c:266
#1 0xffffffff809022b4 in kern_reboot (howto=260)
at /r+d/stable/9/sys/kern/kern_shutdown.c:449
#2 0xffffffff809027a7 in panic (fmt=0x1 <Address 0x1 out of bounds>)
at /r+d/stable/9/sys/kern/kern_shutdown.c:637
#3 0xffffffff80b62e6e in vm_fault_copy_entry (dst_map=0xfffffe001270adc8,
src_map=<value optimized out>, dst_entry=0xfffffe0012bc2348,
src_entry=<value optimized out>, fork_charge=<value optimized out>)
at /r+d/stable/9/sys/vm/vm_fault.c:1356
#4 0xffffffff80b6bb73 in vmspace_fork (vm1=0xfffffe000de90498,
fork_charge=0xffffff814907aaa8) at /r+d/stable/9/sys/vm/vm_map.c:3035
#5 0xffffffff808d1828 in fork1 (td=0xfffffe00122d3920, flags=20, pages=4,
procp=0xffffff814907ab00, procdescp=<value optimized out>,
pdflags=<value optimized out>) at /r+d/stable/9/sys/kern/kern_fork.c:841
#6 0xffffffff808d3272 in sys_fork (td=0xfffffe00122d3920,
uap=<value optimized out>) at /r+d/stable/9/sys/kern/kern_fork.c:110
#7 0xffffffff80c8f330 in amd64_syscall (td=0xfffffe00122d3920, traced=0)
at subr_syscall.c:135
#8 0xffffffff80c79a17 in Xfast_syscall ()
at /r+d/stable/9/sys/amd64/amd64/exception.S:387
#9 0x0000000800edd36c in ?? ()
Previous frame inner to this frame (corrupt stack?)
(kgdb)
cheers
danny
>
> --
> Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E1UOpAo-0006ee-UT>