Date: Wed, 9 Jun 1999 07:33:43 -0500 (EST) From: "John S. Dyson" <toor@dyson.iquest.net> To: hgoldste@bbs.mpcs.com (Howard Goldstein) Cc: dyson@iquest.net, freebsd-hackers@freebsd.org Subject: Re: problem for the VM gurus Message-ID: <199906091233.HAA00173@dyson.iquest.net> In-Reply-To: <14174.21361.773177.526498@penny.south.mpcs.com> from Howard Goldstein at "Jun 9, 99 07:43:45 am"
next in thread | previous in thread | raw e-mail | index | archive | help
> John S. Dyson writes: > > Howard Goldstein said: > > > On Mon, 7 Jun 1999 18:38:51 -0400 (EDT), Brian Feldman <green@unixhelp.org> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199906091233.HAA00173>