On Mon, Feb 07, 2005 at 11:06:46AM -0800, Bill Studenmund wrote:
> On Mon, Feb 07, 2005 at 07:42:36PM +0100, Manuel Bouyer wrote:
> > On Mon, Feb 07, 2005 at 09:49:41AM -0800, Bill Studenmund wrote:
> > > All I can think to do is further discuss this on tech-kern.
> > > 
> > > Oh, I think all the processes in vnlock aren't the core problem. Something 
> > > else has a vnlock and is waiting for some other resource that isn't there. 
> > > Then everything else piles up on the different vnlocks.
> > 
> > Could something with a vnlock try to allocate a new vnode ? If so this
> > is probably the source of the problem.
> 
> I doubt it. It could be true, but I expect it's more likely that the vnode 
> is locked while the fs is trying to do something that's blocking for 
> memory. Then something else ends up waiting on that vnode lock, then 
> something else on the second one, and then you run the race for root. Once 
> the race is done, the root vnode's locked and everything that looks up a 
> path begining with "/" gets to wait. :-|
> 

any further progress on this issue?  Manuel, do you still have this problem?
I've been seeing it on my alpha too.

Thanks
-Dan

--