Non-sleepable locks held. 12 hours old source

Francis Ridder fridder at cse.unl.edu
Sun Nov 16 10:51:01 PST 2003


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

Thanks for the help
Francis

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/octet-stream
Size: 16266 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20031116/6971e5bb/attachment.obj


More information about the freebsd-current mailing list