softdep_flush panic with snapshots



With GENERIC HEAD from Apr 4 14:50 UTC I got this panic:


panic: lockmgr: thread 0xc22a6d80, not exclusive lock holder 0xc240fa20
unlocking
cpuid = 0
KDB: enter: panic
[thread pid 45 tid 100043 ]
Stopped at kdb_enter+0x2b: nop
db> where
Tracing pid 45 tid 100043 td 0xc22a6d80
kdb_enter(c08a1a10) at kdb_enter+0x2b
panic(c089f9af,c22a6d80,c089f999,c240fa20,c22a6d80) at panic+0x14b
lockmgr(c2a54e90,6,c2a54eb4,c22a6d80,cc998c2c) at lockmgr+0x514
vop_stdunlock(cc998c4c,c2941294,c2a54e38,cc998c68,c06c74b4) at
vop_stdunlock+0x22
VOP_UNLOCK_APV(c09475a0,cc998c4c) at VOP_UNLOCK_APV+0x95
vput(c2a54e38,c09caab8,0,c08b9e51,df7) at vput+0xe4
handle_workitem_remove(c2e38280,0) at handle_workitem_remove+0x10f
process_worklist_item(c23fca20,0) at process_worklist_item+0x183
softdep_process_worklist(c23fca20,0,0,c23e3234,c079ab50) at
softdep_process_worklist+0x7c
softdep_flush(0,cc998d38) at softdep_flush+0x132

There's no dump, but I ran the test in single user mode so I hope it's
not totally worthlesss.

http://people.freebsd.org/~pho/stress/log/cons198.html
--
Peter Holm
_______________________________________________
freebsd-current@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@xxxxxxxxxxx"



Relevant Pages

  • Re: 6.1-RELEASE panic / lockmgr?
    ... not exclusive lock holder ... 0xfffffc006052d260 unlocking ... Unfortunately after printing the line with "KDB" the whole thing appears ... Sometimes this increases the reliability of entering the debugger by ...
    (freebsd-stable)
  • Re: 6.1-RELEASE panic / lockmgr?
    ... not exclusive lock holder ... 0xfffffc006052d260 unlocking ... Unfortunately after printing the line with "KDB" the whole thing appears ... Sometimes this increases the reliability of entering the debugger by ...
    (freebsd-stable)
  • Re: 6.1-RELEASE panic / lockmgr?
    ... not exclusive lock holder ... 0xfffffc006052d260 unlocking ... Unfortunately after printing the line with "KDB" the whole thing appears to become completely catatonic:( ... Sometimes this increases the reliability of entering the debugger by avoiding interrupt delivery during the process of entering. ...
    (freebsd-stable)
  • Re: panic: lockmgr on FreeBSD 7.0-RELEASE-p4 amd64
    ... panic: lockmgr: thread 0xffffff0050858350, not exclusive lock holder 0xffffff00074959f0 unlocking ...
    (freebsd-hackers)
  • panic: lockmgr: thread 0x..., not exclusive lock holder 0x... unlocking
    ... panic: lockmgr: thread 0xffffff007b910be0, not exclusive lock holder 0xffffff001c114720 unlocking ... KDB: enter: panic ...
    (freebsd-stable)