checking stopevent 2!

From: Andy Farkas <andyf_at_speednet.com.au>
Date: Sat, 15 Nov 2003 16:21:10 +1000 (EST)
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 _at_ /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 _at_ /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 _at_ /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 _at_ /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 _at_ /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 _at_ /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 _at_ /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 _at_ /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 _at_ /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 _at_ /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 _at_ /hummer/src-current/src/sys/kern/subr_trap.c:260
...



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


--

 :{ andyf_at_speednet.com.au

        Andy Farkas
    System Administrator
   Speednet Communications
 http://www.speednet.com.au/
Received on Fri Nov 14 2003 - 21:21:14 UTC

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