Date: Sun, 16 Nov 2003 11:23:40 -0800 From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: Francis Ridder <fridder@cse.unl.edu> Cc: freebsd-current@freebsd.org Subject: Re: Non-sleepable locks held. 12 hours old source Message-ID: <20031116192340.GA93567@troutmask.apl.washington.edu> In-Reply-To: <BBDD2329.2D1%fridder@cse.unl.edu> References: <20031116082719.6EF5316A4CE@hub.freebsd.org> <BBDD2329.2D1%fridder@cse.unl.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Nov 16, 2003 at 12:50:47PM -0600, Francis Ridder wrote: > Ok, at the tail end of the dmesg file I am getting complaints starting at > boot time of non-sleepable locks held. My source is current as of 12 hours > ago. Pasted here is one of the errors: > > checking stopevent 2 with the following non-sleepable locks held: > exclusive sleep mutex sigacts r = 0 (0xc1d39aa8) locked @ > /usr/src/sys/kern/kern_condvar.c:289 > checking stopevent 2 with the following non-sleepable locks held: > exclusive sleep mutex sigacts r = 0 (0xc1d39aa8) locked @ > /usr/src/sys/kern/subr_trap.c:260 > checking stopevent 2 with the following non-sleepable locks held: > exclusive sleep mutex sigacts r = 0 (0xc1d39aa8) locked @ > /usr/src/sys/kern/subr_trap.c:260 > Re-cvsup and biuld a new kernel. Warner removed the warning message, but the problem still exists. -- Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031116192340.GA93567>