Date: Sat, 15 Nov 2003 10:14:48 -0600 From: Cosmin Stroe <cosmin@hehipc.phy.uic.edu> To: freebsd-current@freebsd.org Subject: Re: checking stopevent 2! Message-ID: <20031115101448.A6920@hehipc.phy.uic.edu> In-Reply-To: <Pine.NEB.3.96L.1031115092948.25438E-100000@fledge.watson.org>; from rwatson@freebsd.org on Sat, Nov 15, 2003 at 09:38:37AM -0500 References: <20031115160208.D13393@hewey.af.speednet.com.au> <Pine.NEB.3.96L.1031115092948.25438E-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Nov 15, 2003 at 09:38:37AM -0500, Robert Watson wrote: > > On Sat, 15 Nov 2003, Andy Farkas wrote: > > would probably be useful if you could drop to DDB and generate a trace for > the event. > I've done that, in this email message: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=2157067+0+current/freebsd-current > > > > ... > > 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/ > > > > > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" Cosmin Stroe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031115101448.A6920>