From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 31 08:36:35 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F1EDA16A4CE; Thu, 31 Mar 2005 08:36:34 +0000 (GMT) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id B92E343D41; Thu, 31 Mar 2005 08:36:34 +0000 (GMT) (envelope-from peter@wemm.org) Received: from fw.wemm.org (canning.wemm.org [192.203.228.65]) by canning.wemm.org (Postfix) with ESMTP id 79CE12A910; Thu, 31 Mar 2005 00:36:34 -0800 (PST) (envelope-from peter@wemm.org) Received: from peter-laptop.wemm.org (dhcp49.wemm.org [10.0.0.49]) by fw.wemm.org (Postfix) with ESMTP id 0CE8CE2B5; Thu, 31 Mar 2005 00:36:34 -0800 (PST) (envelope-from peter@wemm.org) Received: from peter-laptop.wemm.org (localhost [127.0.0.1]) by peter-laptop.wemm.org (8.13.3/8.13.3) with ESMTP id j2V8V1TV000822; Thu, 31 Mar 2005 00:31:01 -0800 (PST) (envelope-from peter@wemm.org) Received: from localhost (localhost [[UNIX: localhost]]) by peter-laptop.wemm.org (8.13.3/8.13.3/Submit) id j2V8UvMB000818; Thu, 31 Mar 2005 00:30:57 -0800 (PST) (envelope-from peter@wemm.org) X-Authentication-Warning: peter-laptop.wemm.org: peter set sender to peter@wemm.org using -f From: Peter Wemm To: freebsd-amd64@freebsd.org Date: Thu, 31 Mar 2005 00:30:56 -0800 User-Agent: KMail/1.7.2 References: <20050330223546.GA4705@troutmask.apl.washington.edu> <424B8A4F.7050607@samsco.org> <20050331054911.GN6252@wantadilla.lemis.com> In-Reply-To: <20050331054911.GN6252@wantadilla.lemis.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200503310030.57519.peter@wemm.org> cc: freebsd-stable@freebsd.org cc: noackjr@alumni.rice.edu Subject: Re: Problems with AMD64 and 8 GB RAM? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2005 08:36:35 -0000 On Wednesday 30 March 2005 09:49 pm, Greg 'groggy' Lehey wrote: > On Wednesday, 30 March 2005 at 22:27:43 -0700, Scott Long wrote: > > Jon Noack wrote: > >> On 03/30/05 23:14, Greg 'groggy' Lehey wrote: > >>> On Wednesday, 30 March 2005 at 21:28:36 -0700, Scott Long wrote: > >>>> Greg 'groggy' Lehey wrote: > >>>>> On Wednesday, 30 March 2005 at 23:01:03 -0500, John Baldwin wrote: > >>>>>> It would be interesting to see the contents of your MADT to see if > >>>>>> it's trying to use a 64-bit PA for your APIC. > >>>>> > >>>>> Any suggestions about how to do so? > >>>> > >>>> man acpidump > >>> > >>> How do you run that on a system that won't boot? > >> > >> You said the system worked with 4 GB (albeit detecting only 3.5 > >> GB). > > Yes, this is correct. A number of people have explained why it only > detected 3.5 GB in this configuration. > You're also being confused by the implementation of the 'real memory' report. If you take a 30 second glance at the code, you'll see that it is reporting the same units that the hw.maxmem tunable uses. ie: it is the LIMIT or Highest Address that the system has, not the sum total of all the parts. eg: see the machdep.c comment next to the printf * Maxmem isn't the "maximum memory", it's one larger than the * highest page of the physical address space. It should be * called something like "Maxphyspage". We may adjust this * based on ``hw.physmem'' and the results of the memory test. The SMAP lines are what you need to pay attention to. In the output you posted with 8G, you can see the 4GB going from the 4->8GB range, exactly. SMAP type 1 is "usable memory". -Peter