On 03-May-01 Matthew Jacob wrote:
> T-o-T about 24 hours ago:
>> lock order reversal
>>  1st lockmgr interlock last acquired @ /usr/src/sys/kern/kern_lock.c:239
>>  2nd 0xfffffe0025df8548 process lock @ /usr/src/sys/kern/kern_exit.c:542
>>  3rd 0xfffffe0000aab8d0 lockmgr interlock @
> /usr/src/sys/kern/kern_lock.c:239

This is new.  We shouldn't be holding the proc lock and dinking with lockmgr at
the same time.  (Well, in theory at least.)

>> acquiring duplicate lock of same type: "allproc"
>>  1st @ /usr/src/sys/kern/kern_proc.c:609
>>  2nd @ /usr/src/sys/kern/kern_proc.c:146

This is old.  This is really a case of recursion, I'm currently hacking on
witness some more which will fix this.

>> lock order reversal
>>  1st vnode interlock last acquired @ /usr/src/sys/ufs/ffs/ffs_vfsops.c:397
>>  2nd 0xfffffc000080f218 mntvnode @ /usr/src/sys/ufs/ffs/ffs_vfsops.c:464
>>  3rd 0xfffffe0026918080 vnode interlock @ /usr/src/sys/kern/vfs_subr.c:1881

This is quite old.  I have some h0h0 patches to fix these, but I'm not sure
that they are actually right:


>> pid 288 (nsrexecd), uid 0: exited on signal 11 (core dumped)
> (oh, yeah, a 4.1 built executable is dying, charming)

Cute. :-/


John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.baldwin.cx/~john/pgpkey.asc
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to