From owner-freebsd-hackers Wed Jun 9 5:34:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from iquest3.iquest.net (iquest3.iquest.net [209.43.20.203]) by hub.freebsd.org (Postfix) with SMTP id 9029915425 for ; Wed, 9 Jun 1999 05:33:55 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (qmail 19707 invoked from network); 9 Jun 1999 12:33:50 -0000 Received: from dyson.iquest.net (198.70.144.127) by iquest3.iquest.net with SMTP; 9 Jun 1999 12:33:50 -0000 Received: (from root@localhost) by dyson.iquest.net (8.9.1/8.9.1) id HAA00173; Wed, 9 Jun 1999 07:33:43 -0500 (EST) From: "John S. Dyson" Message-Id: <199906091233.HAA00173@dyson.iquest.net> Subject: Re: problem for the VM gurus In-Reply-To: <14174.21361.773177.526498@penny.south.mpcs.com> from Howard Goldstein at "Jun 9, 99 07:43:45 am" To: hgoldste@bbs.mpcs.com (Howard Goldstein) Date: Wed, 9 Jun 1999 07:33:43 -0500 (EST) Cc: dyson@iquest.net, freebsd-hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > John S. Dyson writes: > > Howard Goldstein said: > > > On Mon, 7 Jun 1999 18:38:51 -0400 (EDT), Brian Feldman wrote: > > > : 4.0-CURRENT > > > > > > 3.2R too... > > > > > I just checked the source (CVS) tree, and something bad happend > > between 1.27 and 1.29 on ufs_readwrite.c. Unless other things > > had been changed to make the problem go away, the recursive vnode > > thing was broken then. > > I can pretty easily test patches and try other stuff out on a couple > of dozen brand new, architecturally (sp) stressed out (memorywise > (zero swap, 16mb RAM, mfsroot) and cpu bandwidth wise (386sx40)) 3.1-R > (switchable to 3.2R) systems, if it'd be helpful. Should it bring out > clues leading to the fix for 'the' golden page-not-present instability > it'd be awesome karma. This very limited environment is especially > fragile and highly susceptible to consistently reproducing the popular > >= 3.1R page not present panics. > BTW, one more thing that is useful for testing limited memory situations is setting the MAXMEM config variable. Last time that I looked, it allows you to set the number of K of avail mem. If you try to run with less than MAXMEM=4096 or MAXMEM=5120, you'll have troubles through. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message