From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 31 05:49:18 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 C209B16A4CE; Thu, 31 Mar 2005 05:49:18 +0000 (GMT) Received: from blackwater.lemis.com (wantadilla.lemis.com [192.109.197.135]) by mx1.FreeBSD.org (Postfix) with ESMTP id EDC2E43D3F; Thu, 31 Mar 2005 05:49:13 +0000 (GMT) (envelope-from grog@lemis.com) Received: by blackwater.lemis.com (Postfix, from userid 1004) id 4F11A8564F; Thu, 31 Mar 2005 15:19:11 +0930 (CST) Date: Thu, 31 Mar 2005 15:19:11 +0930 From: Greg 'groggy' Lehey To: Scott Long Message-ID: <20050331054911.GN6252@wantadilla.lemis.com> References: <20050330223546.GA4705@troutmask.apl.washington.edu> <20050330224445.GW84137@wantadilla.lemis.com> <200503311032.33718.doconnor@gsoft.com.au> <20050331015429.GH6252@wantadilla.lemis.com> <657eb6604d1e00368d77f047a8b5e074@FreeBSD.org> <20050331040811.GL6252@wantadilla.lemis.com> <424B7C74.4060203@samsco.org> <20050331051458.GM6252@wantadilla.lemis.com> <424B8A94.5070300@alumni.rice.edu> <424B8A4F.7050607@samsco.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="djJN5oi3zFpblwUd" Content-Disposition: inline In-Reply-To: <424B8A4F.7050607@samsco.org> User-Agent: Mutt/1.4.2.1i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 cc: freebsd-stable@FreeBSD.org cc: FreeBSD-amd64@FreeBSD.org cc: noackjr@alumni.rice.edu cc: John Baldwin 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 05:49:18 -0000 --djJN5oi3zFpblwUd Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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. >> My perception of this whole ACPI thing is that it is fixed in your >> BIOS (although it can be overridden by the OS). As such, the >> amount of RAM you have in the machine shouldn't change acpidump >> results. Is that not correct? > > This is absolutely correct. Ah, so you meant to say that the output from the system running with 4 GB memory is useful? That wasn't in the man page you pointed to. What it does say is: > When invoked with the -t flag, the acpidump utility dumps contents of > the following tables: > > ... MADT This may be the case, but between man page and output some terminology must have changed. I can't see any reference to anything like an MADT there. Does that mean that there isn't one, or that ACPI can't find it, or does the section APIC refer to/dump the MADT? Here's the complete output of acpidump -t, anyway: /* RSD PTR: OEM=3DVIAK8, ACPI_Rev=3D1.0x (0) RSDT=3D0xdfee3000, cksum=3D97 */ /* RSDT: Length=3D44, Revision=3D1, Checksum=3D4, OEMID=3DVIAK8, OEM Table ID=3DAWRDACPI, OEM Revision=3D0x42302e31, Creator ID=3DAWRD, Creator Revision=3D0x0 Entries=3D{ 0xdfee3040, 0xdfee7b40 } */ /* FACP: Length=3D116, Revision=3D1, Checksum=3D255, OEMID=3DVIAK8, OEM Table ID=3DAWRDACPI, OEM Revision=3D0x42302e31, Creator ID=3DAWRD, Creator Revision=3D0x0 FACS=3D0xdfee0000, DSDT=3D0xdfee30c0 INT_MODEL=3DPIC Preferred_PM_Profile=3DUnspecified (0) SCI_INT=3D9 SMI_CMD=3D0x402f, ACPI_ENABLE=3D0xa1, ACPI_DISABLE=3D0xa0, S4BIOS_R= EQ=3D0x0 PSTATE_CNT=3D0x0 PM1a_EVT_BLK=3D0x4000-0x4003 PM1a_CNT_BLK=3D0x4004-0x4005 PM_TMR_BLK=3D0x4008-0x400b GPE0_BLK=3D0x4020-0x4023 P_LVL2_LAT=3D101 us, P_LVL3_LAT=3D1001 us FLUSH_SIZE=3D0, FLUSH_STRIDE=3D0 DUTY_OFFSET=3D0, DUTY_WIDTH=3D1 DAY_ALRM=3D125, MON_ALRM=3D126, CENTURY=3D50 IAPC_BOOT_ARCH=3D Flags=3D{WBINVD,PROC_C1,SLP_BUTTON,RTC_S4,RESET_REG} RESET_REG=3D0x00000000:0[0] (Memory), RESET_VALUE=3D0x44 */ /* FACS: Length=3D64, HwSig=3D0x00000000, Firm_Wake_Vec=3D0x00000000 Global_Lock=3D Flags=3D Version=3D0 */ /* DSDT: Length=3D19020, Revision=3D1, Checksum=3D28, OEMID=3DVIAK8, OEM Table ID=3DAWRDACPI, OEM Revision=3D0x1000, Creator ID=3DMSFT, Creator Revision=3D0x100000e */ /* APIC: Length=3D104, Revision=3D1, Checksum=3D145, OEMID=3DVIAK8, OEM Table ID=3DAWRDACPI, OEM Revision=3D0x42302e31, Creator ID=3DAWRD, Creator Revision=3D0x0 Local APIC ADDR=3D0xfee00000 Flags=3D{PC-AT} Type=3DLocal APIC ACPI CPU=3D0 Flags=3D{ENABLED} APIC ID=3D0 Type=3DLocal APIC ACPI CPU=3D1 Flags=3D{ENABLED} APIC ID=3D1 Type=3DIO APIC APIC ID=3D2 INT BASE=3D0 ADDR=3D0x00000000fec00000 Type=3DINT Override BUS=3D0 IRQ=3D0 INTR=3D2 Flags=3D{Polarity=3Dconforming, Trigger=3Dconforming} Type=3DINT Override BUS=3D0 IRQ=3D9 INTR=3D9 Flags=3D{Polarity=3Dactive-lo, Trigger=3Dlevel} Type=3DLocal NMI ACPI CPU=3D0 LINT Pin=3D1 Flags=3D{Polarity=3Dactive-hi, Trigger=3Dedge} Type=3DLocal NMI ACPI CPU=3D1 LINT Pin=3D1 Flags=3D{Polarity=3Dactive-hi, Trigger=3Dedge} */ Since I don't know anything about ACPI, this doesn't say too much to me. Suggestions welcome. If the APIC section is the MADT, it looks as if we should update the docco. Greg --=20 See complete headers for address and phone numbers. --djJN5oi3zFpblwUd Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFCS49XIubykFB6QiMRAsrtAJ9Su5scTK77GwMfpNlY9226M3PmBgCeJAuW jnGEA6QAiww8SWKmY9EftpM= =qNE4 -----END PGP SIGNATURE----- --djJN5oi3zFpblwUd--