Lars Eggert wrote:
lock order reversal
1st 0xc6f47a68 vnode interlock (vnode interlock) @
/usr/src/sys/nfsclient/nfs_vnops.c:2629
2nd 0xc04b8640 vm page queue mutex (vm page queue mutex) @
/usr/src/sys/vm/vm_kern.c:424
Still present on yesterday's -current.
Lars
--
Lars Eggert <[EMAIL PROTEC
On 21 Oct, Robert Watson wrote:
>
> On Mon, 21 Oct 2002, Lars Eggert wrote:
>
>> lock order reversal
>> 1st 0xc791bc00 pipe mutex (pipe mutex) @ /usr/src/sys/kern/sys_pipe.c:465
>> 2nd 0xc04974e0 sigio lock (sigio lock) @ /usr/src/sys/kern/kern_sig.c:2156
>
> It strikes me that, for better o
On Mon, 21 Oct 2002, Lars Eggert wrote:
> lock order reversal
> 1st 0xc791bc00 pipe mutex (pipe mutex) @ /usr/src/sys/kern/sys_pipe.c:465
> 2nd 0xc04974e0 sigio lock (sigio lock) @ /usr/src/sys/kern/kern_sig.c:2156
It strikes me that, for better or for worse, the reported "reversal" is
the r
On 21 Oct, Lars Eggert wrote:
> lock order reversal
> 1st 0xc791bc00 pipe mutex (pipe mutex) @ /usr/src/sys/kern/sys_pipe.c:465
> 2nd 0xc04974e0 sigio lock (sigio lock) @ /usr/src/sys/kern/kern_sig.c:2156
I've been complaining about that one for ages. I think I know how I
want to attack it, b
lock order reversal
1st 0xc791bc00 pipe mutex (pipe mutex) @ /usr/src/sys/kern/sys_pipe.c:465
2nd 0xc04974e0 sigio lock (sigio lock) @ /usr/src/sys/kern/kern_sig.c:2156
Debugger("witness_lock")
Stopped at Debugger+0x5a: xchgl %ebx,in_Debugger.0
db> trace
Debugger(c0440ebb,c04974e0,c043a
lock order reversal
1st 0xc6f47a68 vnode interlock (vnode interlock) @
/usr/src/sys/nfsclient/nfs_vnops.c:2629
2nd 0xc04b8640 vm page queue mutex (vm page queue mutex) @
/usr/src/sys/vm/vm_kern.c:424
Debugger("witness_lock")
Stopped at Debugger+0x5a: xchgl %ebx,in_Debugger.0
db> trace