tacho> lock order reversal tacho> 1st 0xc03f0140 mntvnode @ /usr/src/sys/ufs/ffs/ffs_vfsops.c:1007 tacho> 2nd 0xcaec972c vnode interlock @ /usr/src/sys/ufs/ffs/ffs_vfsops.c:1016 matusita> Exactly the same kernel message was here. ddb trace output is as follows. db> trace Debugger(c02bd5ae) at Debugger+0x44 witness_lock(c5ce622c,8,c02cde39,3f8) at witness_lock+0x90d ffs_sync(c089f200,3,c05adc00,c5420200,c089f200,2) at ffs_sync+0x175 sync_fsync(c5831f5c) at sync_fsync+0x18f sched_sync(0,c5831fa8) at sched_sync+0x16c fork_exit(c01e839c,0,c5831fa8) at fork_exit+0xb4 fork_trampoline() at fork_trampoline+0x8 db> -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
- lock order reversal Jun Kuriyama
- Re: lock order reversal Jun Kuriyama
- lock order reversal Stanislav Grozev
- Re: lock order reversal Makoto MATSUSHITA
- lock order reversal Giorgos Keramidas
- Re: lock order reversal John Baldwin
- Re: lock order reversal Makoto MATSUSHITA
- Re: lock order reversal John Baldwin
- Re: lock order reversal Makoto MATSUSHITA
- Re: lock order reversal John Baldwin
- Re: lock order reversal Makoto MATSUSHITA
- Re: lock order reversal Jun Kuriyama
- Re: lock order reversal Makoto MATSUSHITA
- Re: lock order reversal John Baldwin
- Lock order reversal Gavin Atkinson
- lock order reversal Herb McNew
- lock order reversal leafy
- Re: lock order reversal Ulrich Spoerlein
- Re: lock order reversal Kris Kennaway
- Re: lock order reversal Daniel C. Sobral
- Lock order reversal Sean Kelly