On Mon, 15 Jun 2009, Kris Kennaway wrote: > Pav Lucistnik wrote: >> panic: mtx_lock() of destroyed mutex _at_ /usr/src/sys/rpc/clnt_vc.c:953 >> cpuid = 2 >> KDB: enter: panic >> [thread pid 0 tid 100029 ] >> Stopped at kdb_enter+0x3d: movq $0,0x3f5fb8(%rip) >> db> bt >> Tracing pid 0 tid 100029 td 0xffffff00018e1000 >> kdb_enter() at kdb_enter+0x3d >> panic() at panic+0x17b >> _mtx_lock_flags() at _mtx_lock_flags+0xc5 >> clnt_vc_soupcall() at clnt_vc_soupcall+0x273 >> sowakeup() at sowakeup+0xf8 [stuff snipped] >> The box is in kdb on serial console for now. May 9 -CURRENT, I think. >> > > This happened again. The trigger was this (^C of a find on a busy netapp > volume with a lot of other concurrent nfs traffic to the same mountpoint): > > About 5-10 minutes later the machine panicked. I'll try updating to a newer > -CURRENT. > Although there are a couple of krpc fixes still in the pipe and not yet committed, I think the above panic was fixed by r193437. (June 4, 2009.) If your crash was because it slept while rc_lock was held, that patch isn't committed yet. The other known issue for which a patch isn't committed yet is a reference to a bad pointer in strdup() when called from svc_reg(). Hopefully these will be patched soon, rickReceived on Tue Jun 16 2009 - 14:16:53 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:50 UTC