> >He's trying to ask if this is a problem with the code in question or 3.2R's
> That's better. It appears to be a classic resource related deadlock that
> is caused by the VFS code needing pages in order to page things out (and thus
> free up pages), but is unable to since no memory is available.
> Matt Dillon was working on deadlocks like this in -current awhile back and
> it would be interesting to know if the hang occurs there as well. I don't
> have a -current machine at the moment so I can't test it myself.
FreeBSD 4.0-CURRENT #14: Mon Aug 9 17:44:35 PDT 1999
It doesn't hang my machine here, I let it go to about 25.
we are but packets in the internet of life
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message