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 _______________________________________________ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
