lock order reversal
1st 0xd3a5c11c process lock @ ../../../vm/vm_glue.c:469
2nd 0xc0e3fe30 lockmgr interlock @ ../../../kern/kern_lock.c:239
This is on relatively old (~ three months) sources. The first lock is
from swapout_procs(); I assume the second lock actually refers to the
call to lockmgr(&vm->vm_map.lock, ...) further down in the same
function. If this has been fixed already, let me know. (It doesn't
seem to have hurt anything.)
-GAWollman
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message