From owner-freebsd-hackers Wed Aug 11 11:39:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from io.yi.org (24.66.174.118.bc.wave.home.com [24.66.174.118]) by hub.freebsd.org (Postfix) with ESMTP id 3A4FE155B6 for ; Wed, 11 Aug 1999 11:39:16 -0700 (PDT) (envelope-from jake@checker.org) Received: from io.yi.org (localhost [127.0.0.1]) by io.yi.org (Postfix) with ESMTP id CCA861F57; Wed, 11 Aug 1999 11:39:38 -0700 (PDT) X-Mailer: exmh version 2.0.2 2/24/98 To: dg@root.com Cc: Charles Randall , freebsd-hackers@FreeBSD.ORG, Oleg Derevenetz Subject: Re: mmap bug In-reply-to: Your message of "Wed, 11 Aug 1999 11:19:05 PDT." <199908111819.LAA26998@implode.root.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 11 Aug 1999 11:39:38 -0700 From: Jake Burkholder Message-Id: <19990811183938.CCA861F57@io.yi.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >He's trying to ask if this is a problem with the code in question or 3.2R's > >mmap. > > 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