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=VIAK8, ACPI_Rev=1.0x (0) RSDT=0xdfee3000, cksum=97 */ /* RSDT: Length=44, Revision=1, Checksum=4, OEMID=VIAK8, OEM Table ID=AWRDACPI, OEM Revision=0x42302e31, Creator ID=AWRD, Creator Revision=0x0 Entries={ 0xdfee3040, 0xdfee7b40 } */ /* FACP: Length=116, Revision=1, Checksum=255, OEMID=VIAK8, OEM Table ID=AWRDACPI, OEM Revision=0x42302e31, Creator ID=AWRD, Creator Revision=0x0 FACS=0xdfee0000, DSDT=0xdfee30c0 INT_MODEL=PIC Preferred_PM_Profile=Unspecified (0) SCI_INT=9 SMI_CMD=0x402f, ACPI_ENABLE=0xa1, ACPI_DISABLE=0xa0, S4BIOS_REQ=0x0 PSTATE_CNT=0x0 PM1a_EVT_BLK=0x4000-0x4003 PM1a_CNT_BLK=0x4004-0x4005 PM_TMR_BLK=0x4008-0x400b GPE0_BLK=0x4020-0x4023 P_LVL2_LAT=101 us, P_LVL3_LAT=1001 us FLUSH_SIZE=0, FLUSH_STRIDE=0 DUTY_OFFSET=0, DUTY_WIDTH=1 DAY_ALRM=125, MON_ALRM=126, CENTURY=50 IAPC_BOOT_ARCH= Flags={WBINVD,PROC_C1,SLP_BUTTON,RTC_S4,RESET_REG} RESET_REG=0x00000000:0[0] (Memory), RESET_VALUE=0x44 */ /* FACS: Length=64, HwSig=0x00000000, Firm_Wake_Vec=0x00000000 Global_Lock= Flags= Version=0 */ /* DSDT: Length=19020, Revision=1, Checksum=28, OEMID=VIAK8, OEM Table ID=AWRDACPI, OEM Revision=0x1000, Creator ID=MSFT, Creator Revision=0x100000e */ /* APIC: Length=104, Revision=1, Checksum=145, OEMID=VIAK8, OEM Table ID=AWRDACPI, OEM Revision=0x42302e31, Creator ID=AWRD, Creator Revision=0x0 Local APIC ADDR=0xfee00000 Flags={PC-AT} Type=Local APIC ACPI CPU=0 Flags={ENABLED} APIC ID=0 Type=Local APIC ACPI CPU=1 Flags={ENABLED} APIC ID=1 Type=IO APIC APIC ID=2 INT BASE=0 ADDR=0x00000000fec00000 Type=INT Override BUS=0 IRQ=0 INTR=2 Flags={Polarity=conforming, Trigger=conforming} Type=INT Override BUS=0 IRQ=9 INTR=9 Flags={Polarity=active-lo, Trigger=level} Type=Local NMI ACPI CPU=0 LINT Pin=1 Flags={Polarity=active-hi, Trigger=edge} Type=Local NMI ACPI CPU=1 LINT Pin=1 Flags={Polarity=active-hi, Trigger=edge} */ 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 -- See complete headers for address and phone numbers.
pgpd4k8dxjan9.pgp
Description: PGP signature