At Fri, 16 Jan 2004 04:47:06 +0000 (UTC), Damian Gerow wrote: > newhost# truss -o snmpd.out snmpd -DALL -Lf snmpd.debug -f Grr, when I try to do above, I got a panic below. This is old (approx 2004-01-07) -current, so I'm not sure this was already fixed or not. I'm busy in these days for my real job, so I don't want to upgrade to the latest -current which looks unstable around fd... ----- Sleeping on "stopevent" with the following non-sleepable locks held: exclusive sleep mutex sigacts r = 0 (0xd1948aa8) locked _at_ kern/subr_trap.c:260 lock order reversal 1st 0xd1948aa8 sigacts (sigacts) _at_ kern/subr_trap.c:260 2nd 0xce5ade2c process lock (process lock) _at_ kern/kern_synch.c:309 Stack backtrace: backtrace(c0735ad3,ce5ade2c,c0731cdb,c0731cdb,c0732d51) at backtrace+0x17 witness_lock(ce5ade2c,8,c0732d51,135,ce5ade2c) at witness_lock+0x672 _mtx_lock_flags(ce5ade2c,0,c0732d48,135,ffffffff) at _mtx_lock_flags+0xba msleep(ce5adef0,ce5ade2c,5c,c07362ca,0) at msleep+0x794 stopevent(ce5addc0,2,2,823,c07b3120) at stopevent+0x85 issignal(ce5ae930,2,c0732857,bd,1) at issignal+0x168 cursig(ce5ae930,0,c0735222,104,8052000) at cursig+0xe8 ast(ea1bed48) at ast+0x4b0 doreti_ast() at doreti_ast+0x17 Sleeping on "stopevent" with the following non-sleepable locks held: exclusive sleep mutex sigacts r = 0 (0xd1948aa8) locked _at_ kern/subr_trap.c:260 Sleeping on "stopevent" with the following non-sleepable locks held: exclusive sleep mutex sigacts r = 0 (0xc8169aa8) locked _at_ kern/subr_trap.c:260 panic: sleeping thread (pid 54512) owns a non-sleepable lock cpuid = 1; Debugger("panic") -- Jun Kuriyama <kuriyama_at_imgsrc.co.jp> // IMG SRC, Inc. <kuriyama_at_FreeBSD.org> // FreeBSD ProjectReceived on Fri Jan 16 2004 - 05:39:15 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:38 UTC