Date: Sat, 15 Nov 2003 16:21:10 +1000 (EST) From: Andy Farkas <andyf@speednet.com.au> To: freebsd-current@FreeBSD.ORG Subject: checking stopevent 2! Message-ID: <20031115160208.D13393@hewey.af.speednet.com.au>
next in thread | raw e-mail | index | archive | help
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)
--
:{ andyf@speednet.com.au
Andy Farkas
System Administrator
Speednet Communications
http://www.speednet.com.au/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031115160208.D13393>