From owner-freebsd-current@FreeBSD.ORG Wed Nov 23 17:16:35 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E556C16A41F for ; Wed, 23 Nov 2005 17:16:35 +0000 (GMT) (envelope-from eculp@bafirst.com) Received: from bafirst.com (72-12-2-214.wan.networktel.net [72.12.2.214]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6BDCE43D5D for ; Wed, 23 Nov 2005 17:16:27 +0000 (GMT) (envelope-from eculp@bafirst.com) Received: from localhost (localhost [127.0.0.1]) (uid 80) by bafirst.com with local; Wed, 23 Nov 2005 11:16:26 -0600 id 00095804.4384A3EA.000120DC Received: from local4.local.net (local4.local.net [192.168.1.4]) by mail.bafirst.com (Horde MIME library) with HTTP; Wed, 23 Nov 2005 11:16:26 -0600 Message-ID: <20051123111626.ix99g4tm4okg88w4@mail.bafirst.com> Date: Wed, 23 Nov 2005 11:16:26 -0600 From: eculp@bafirst.com To: freebsd-current@freebsd.org References: <20051120183309.ysgk624asksckwow@mail.bafirst.com> <20051121004749.GA39061@xor.obsecurity.org> <43812AC7.3020506@rogers.com> <20051121020816.GA19252@xor.obsecurity.org> <438136B5.9030506@freebsd.org> <20051121131713.bakf4048too0osk0@mail.bafirst.com> In-Reply-To: <20051121131713.bakf4048too0osk0@mail.bafirst.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) 4.1-cvs Subject: Re: avail memory is short by 1G on my FreeBSD 6.0-STABLE MP Dell X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Nov 2005 17:16:36 -0000 Quoting eculp@bafirst.com: > Quoting Paul Saab : > >> Chad Leigh -- Shire.Net LLC wrote: >>> I assume you are talking about the "phenomenon" of RAM "missing" >>> due to PCI and other I/O mapping into the 4GB address space? What >>> struck me about the OP is that the amount of RAM "missing" is more >>> than I have ever seen due to this. My systems are usually >>> 3.4-3.6GB of RAM with 4GB installed, not 2.86GB (3005MB)... So are >>> we sure that the PCI space mapping is the problem? >>> >> Enable PAE and you'll get all your ram. > > Done that but I am going to wait until early tomorrow morning to > reboot because I want to get a verbose boot with this kernel and then > try the PAE kernel, for whatever. For Closure, enable PAE seems to get all ram as Chad said. I found the amounts a bit strange but a heck of a lot better. Boot with PAE now shows: real memory = 5368709120 (5120 MB) avail memory = 4185292800 (3991 MB) Boot withoug PAE shows: real memory = 3220963328 (3071 MB) avail memory = 3151077376 (3005 MB) Of course now I will need to recompile the kernel with the modules that we now load, some of which I forgot but probably a small price for almost a GB more memory and if I'm lucky the kernel might even be a bit faster ;) Thanks again for all your suggestions and comments, it was definitly a learning experience. ed P.S. No problem at all with the kernel booting or anything, just be sure to compile in all the modules that you are now using.