Help!

These messages spew onto my console and into syslogd once every second:

...
Nov 15 16:05:44 <kern.crit> hummer kernel: checking stopevent 2 with the following 
non-sleepable locks held:
Nov 15 16:05:44 <kern.crit> hummer kernel: exclusive sleep mutex sigacts r = 0 
(0xc4656aa8) locked @ /hummer/src-current/src/sys/kern/kern_condvar.c:289
Nov 15 16:05:44 <kern.crit> hummer kernel: checking stopevent 2 with the following 
non-sleepable locks held:
Nov 15 16:05:44 <kern.crit> hummer kernel: exclusive sleep mutex sigacts r = 0 
(0xc4656aa8) locked @ /hummer/src-current/src/sys/kern/subr_trap.c:260
Nov 15 16:05:44 <kern.crit> hummer kernel: checking stopevent 2 with the following 
non-sleepable locks held:
Nov 15 16:05:45 <kern.crit> hummer kernel: exclusive sleep mutex sigacts r = 0 
(0xc4656aa8) locked @ /hummer/src-current/src/sys/kern/subr_trap.c:260
Nov 15 16:05:45 <kern.crit> hummer kernel: checking stopevent 2 with the following 
non-sleepable locks held:
Nov 15 16:05:45 <kern.crit> hummer kernel: exclusive sleep mutex sigacts r = 0 
(0xc4663aa8) locked @ /hummer/src-current/src/sys/kern/kern_synch.c:293
Nov 15 16:05:45 <kern.crit> hummer kernel: checking stopevent 2 with the following 
non-sleepable locks held:
Nov 15 16:05:45 <kern.crit> hummer kernel: exclusive sleep mutex sigacts r = 0 
(0xc4663aa8) locked @ /hummer/src-current/src/sys/kern/subr_trap.c:260
Nov 15 16:05:45 <kern.crit> hummer kernel: checking stopevent 2 with the following 
non-sleepable locks held:
Nov 15 16:05:45 <kern.crit> hummer kernel: exclusive sleep mutex sigacts r = 0 
(0xc4663aa8) locked @ /hummer/src-current/src/sys/kern/subr_trap.c:260
Nov 15 16:05:45 <kern.crit> hummer kernel: checking stopevent 2 with the following 
non-sleepable locks held:
Nov 15 16:05:45 <kern.crit> hummer kernel: exclusive sleep mutex sigacts r = 0 
(0xc4656aa8) locked @ /hummer/src-current/src/sys/kern/kern_condvar.c:289
Nov 15 16:05:45 <kern.crit> hummer kernel: checking stopevent 2 with the following 
non-sleepable locks held:
Nov 15 16:05:46 <kern.crit> hummer kernel: exclusive sleep mutex sigacts r = 0 
(0xc4656aa8) locked @ /hummer/src-current/src/sys/kern/subr_trap.c:260
Nov 15 16:05:46 <kern.crit> hummer kernel: checking stopevent 2 with the following 
non-sleepable locks held:
Nov 15 16:05:46 <kern.crit> hummer kernel: exclusive sleep mutex sigacts r = 0 
(0xc4656aa8) locked @ /hummer/src-current/src/sys/kern/kern_condvar.c:289
Nov 15 16:05:46 <kern.crit> hummer kernel: checking stopevent 2 with the following 
non-sleepable locks held:
Nov 15 16:05:46 <kern.crit> hummer kernel: exclusive sleep mutex sigacts r = 0 
(0xc4656aa8) locked @ /hummer/src-current/src/sys/kern/subr_trap.c:260
Nov 15 16:05:46 <kern.crit> hummer kernel: checking stopevent 2 with the following 
non-sleepable locks held:
Nov 15 16:05:46 <kern.crit> hummer kernel: exclusive sleep mutex sigacts r = 0 
(0xc4656aa8) locked @ /hummer/src-current/src/sys/kern/subr_trap.c:260
...



This is latest -current (cvsup'd a few hours ago)


--

 :{ [EMAIL PROTECTED]

        Andy Farkas
    System Administrator
   Speednet Communications
 http://www.speednet.com.au/


_______________________________________________
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to