Date: Fri, 2 Dec 2005 15:47:16 +0100 From: Yuri Khotyaintsev <yuri@irfu.se> To: John Baldwin <jhb@freebsd.org> Cc: freebsd-hackers@freebsd.org, freebsd-stable@freebsd.org Subject: Re: Fatal trap 12: page fault while in kernel mode Message-ID: <200512021547.16841.yuri@irfu.se> In-Reply-To: <200512020854.20959.jhb@freebsd.org> References: <200512021100.03167.yuri@irfu.se> <200512020854.20959.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Friday 02 December 2005 14.54, John Baldwin wrote: > On Friday 02 December 2005 05:00 am, Yuri Khotyaintsev wrote: > > I have the following panic occurring several times a week. The machine = is > > an NFS server, and it usually panics early in the morning, when first > > people try to access it. After reboot it may work OK for 1-2 days, and > > then panics again. I have tried changing memory and replacing disk which > > was exported via NFS, but nothing helped :( > > > > Any suggestion on how to fix this panic will be very much appreciated ! > > This panic (in propagate_priority) is usually caused when a thread goes to > sleep while holding a mutex (which is forbidden). If you enable INVARIAN= TS > and/or WITNESS you should get a better panic, and with WITNESS you will > even be warned when a thread goes to sleep while holding a mutex. Howeve= r, > these options do introduce considerable execution overhead, and sometimes > that overhead changes the timing enough to hide the race. :( I am compiling a new kernel with INVARIANTS and WITNESS now. Will wait for = a=20 "better" panic ;-) =2D-=20 Dr. Yuri Khotyaintsev Institutet f=F6r rymdfysik (IRF), Uppsala
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200512021547.16841.yuri>