Date: Sat, 29 Mar 1997 09:15:36 +0000 (GMT) From: Doug Rabson <dfr@nlsystems.com> To: John Polstra <jdp@polstra.com> Cc: current@freebsd.org Subject: Re: Panic: "lockmgr: pid %d, not %s %d unlocking" Message-ID: <Pine.BSF.3.95q.970329091224.4554B-100000@kipper.nlsystems.com> In-Reply-To: <199703290130.RAA08748@austin.polstra.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 28 Mar 1997, John Polstra wrote: > I just got this panic on a -current kernel from March 17th, running > on a 486/66DX2 with 16 MB of RAM: > > #9 0xf01181fa in panic (fmt=0xf0112e4b "lockmgr: pid %d, not %s %d unlocking") > at ../../kern/kern_shutdown.c:366 > #10 0xf01132d8 in lockmgr (lkp=0xf0bc3e34, flags=6, interlkp=0xf0ba5b60, > p=0xf0bf1800) at ../../kern/kern_lock.c:355 > #11 0xf01af9c3 in ufs_unlock (ap=0xefbffd50) at ../../ufs/ufs/ufs_vnops.c:1784 > #12 0xf0165b35 in nfs_inactive (ap=0xefbffd78) at vnode_if.h:843 This looks as if the vnode was recycled unexpectedly from NFS to UFS during the call to vm_object_deallocate. Unfortunately I can't see any obvious way this can happen since the vm_object has a ref to the vnode and it doesn't look like vm_object_deallocate can get re-entered easily. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.95q.970329091224.4554B-100000>