Subject: Re: kern/32409: NetBSD-3.0/i386 vnlock deadlock
To: None <gnats-bugs@NetBSD.org>
From: Michael L. Hitch <mhitch@lightning.msu.montana.edu>
List: netbsd-bugs
Date: 11/15/2006 22:49:04
I just took a quick look at this, and I noticed that the ftpd process that
held the lock was also in vnlock waiting for a different vnode.  If you
can find the process holding that lock the next time, it would be 
interesting to see what it's waiting for.  It may be that the process 
holding the lock on the second vnode is waiting for a lock on the first 
locked vnode.

--
Michael L. Hitch			mhitch@montana.edu
Computer Consultant
Information Technology Center
Montana State University	Bozeman, MT	USA