From owner-freebsd-current@FreeBSD.ORG Mon Nov 21 19:11:16 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 4D85916A41F for ; Mon, 21 Nov 2005 19:11:16 +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 BCF9543D4C for ; Mon, 21 Nov 2005 19:11:15 +0000 (GMT) (envelope-from eculp@bafirst.com) Received: from localhost (localhost [127.0.0.1]) (uid 80) by bafirst.com with local; Mon, 21 Nov 2005 13:11:15 -0600 id 0009580F.43821BD3.0000605E Received: from local4.local.net (local4.local.net [192.168.1.4]) by mail.bafirst.com (Horde MIME library) with HTTP; Mon, 21 Nov 2005 13:11:14 -0600 Message-ID: <20051121131114.p7ed53lnkk4ckk4w@mail.bafirst.com> Date: Mon, 21 Nov 2005 13:11:14 -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> <20051121030915.GC41629@dan.emsphone.com> <43813BBE.2010302@freebsd.org> <20051121034025.GD41629@dan.emsphone.com> In-Reply-To: <20051121034025.GD41629@dan.emsphone.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: Mon, 21 Nov 2005 19:11:16 -0000 Quoting Dan Nelson : > In the last episode (Nov 20), Paul Saab said: >> Dan Nelson wrote: >> >In the last episode (Nov 20), Paul Saab said: >> >>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. >> > >> >Anyone know if it's possible for the kernel to determine if any RAM >> >is mapped above the 4gb point and warn the user about how much >> >memory is unaccessable without PAE? >> >> You mean like it does now? >> "262144K of memory above 4GB ignored" > > That line didn't show up the the original poster's dmesg, though ( > http://unixmania.com/dmesg_20051120.txt ). Maybe a verbose boot would > shed more light. Thanks to all who have answered and I apologize for not finding this when searching google. I obviously needed to filter it more. As always now that I know what the problem probably is it is easy. I'm currently building kernel with PAE although it does make me a bit nervious to remotely reboot. I think I will first reboot enabling verbose with the debug.bootverbose sysctl variable since I only have remote access to the machine and no serial console. I will report back this weekend after rebooting with the PAE kernel that will hopefully work as expected. Thanks to everyone and again apologizes for not finding the solution in my searches. ed > > -- > Dan Nelson > dnelson@allantgroup.com > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >