From owner-freebsd-hackers Fri Jan 31 18:33:39 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id SAA29412 for hackers-outgoing; Fri, 31 Jan 1997 18:33:39 -0800 (PST) Received: from bsd.fs.bauing.th-darmstadt.de (bsd.fs.bauing.th-darmstadt.de [130.83.63.241]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA29392 for ; Fri, 31 Jan 1997 18:33:33 -0800 (PST) Received: from [195.52.251.6] (apfel.nacamar.de [195.52.251.6]) by bsd.fs.bauing.th-darmstadt.de (8.8.2/8.8.2) with ESMTP id DAA13722; Sat, 1 Feb 1997 03:32:51 +0100 (MET) X-Sender: freebsd@mail.nacamar.de Message-Id: In-Reply-To: <199701292132.WAA21498@pat.idt.unit.no> References: Your message of "Wed, 29 Jan 1997 19:36:58 +0100 (MET)" Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 1 Feb 1997 03:29:57 +0100 To: Tor Egge , petzi@mail.nacamar.de From: Michael Beckmann Subject: Re: 2.2-BETA: options MAXMEM not working (fwd) Cc: hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 22:32 Uhr +0100 29.1.1997, Tor Egge wrote: >> OK, after having built a couple more kernels, I found out that the MAXMEM >> option does not work for me when set to over 128 MB. I now run a kernel >> that uses only 128 MB, though my machine has 192 MB and will have 256 at >> the end of the week. Has this problem been fixed in kernels subsequent to >> 2.2-BETA ? I was using 160 MB just fine with FreeBSD 2.1.5. >> >> Cheers, >> >> Michael > >Is bounce buffer support disabled ? It uses some kernel virtual address space. It was enabled, I disabled it now. >If that does not help, you may want to look at PR kern/1880. I applied your patches. The kernel now recognises all the RAM. I cannot say which of the two changes helped, however, as I made the changes at once :-) Cheers, Michael