Re: Non-sleepable locks held. 12 hours old source

From: Steve Kargl <sgk_at_troutmask.apl.washington.edu>
Date: Sun, 16 Nov 2003 11:23:40 -0800
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 _at_
> /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 _at_
> /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 _at_
> /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
Received on Sun Nov 16 2003 - 10:23:48 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:29 UTC