Date: Tue, 1 Aug 2006 14:31:54 +0100 (BST) From: Robert Watson <rwatson@FreeBSD.org> To: Graham Menhennitt <gmenhennitt@optusnet.com.au> Cc: freebsd-stable <freebsd-stable@freebsd.org> Subject: Re: Panic Message-ID: <20060801143026.D64452@fledge.watson.org> In-Reply-To: <44C4D3B0.7090705@optusnet.com.au> References: <44BEBA2F.3060403@math.missouri.edu> <20060723135739.M60996@fledge.watson.org> <44C3EC68.6050802@optusnet.com.au> <44C4D3B0.7090705@optusnet.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 25 Jul 2006, Graham Menhennitt wrote: >>> Fatal trap 12: page fault while in kernel mode >>>> current process = 479 (mountd) >>>> >> >> I have the same panic reproducibly. Shutting off nfs_server_enable (i.e. >> mountd) in rc.conf prevents it. This is with 6-STABLE cvsupped yesterday. >> I'll get some more info and follow up the PR. >> > I rebuilt my kernel (to enable debugging) and now it doesn't panic. So it > seems that an old kernel (from around the end of May) with a new mountd > (from Sunday) will crash. But a new kernel with a new mountd won't. FYI, I've managed to reproduce this on a 7-CURRENT kernel, so will try to take a look at this in detail in the next few days. It looks like a race during socket connect/accept for UNIX domain sockets, likely involving simultaneous close, which may be a sign of a bug in mountd (or the like) that triggers it. Of course, the kernel shouldn't panic under those circumstances. :-) Thanks, Robert N M Watson Computer Laboratory University of Cambridge
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060801143026.D64452>