Re: Problems with AMD64 and 8 GB RAM?

From: John Baldwin (jhb_at_FreeBSD.org)
Date: 03/31/05

  • Next message: John Baldwin: "Re: Problems with AMD64 and 8 GB RAM?"
    Date: Thu, 31 Mar 2005 08:02:07 -0500
    To: "Greg 'groggy' Lehey" <grog@FreeBSD.org>
    
    

    On Mar 31, 2005, at 12:49 AM, Greg 'groggy' Lehey wrote:

    > 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:

    MADT is the name of the table (Multiple APIC Descriptor Table or some
    such), but "APIC" is the 4 character signature of the MADT, hence
    seeing 'APIC' output from acpidump -t when looking at the MADT.
    Similarly, the MP Table is known as the MP Table, but the signature for
    the table that you search for in the BIOS is "_MP_".

    > /*
    > 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}
    > */

    Nothing strange here, and it is giving a 64-bit PA for the I/O APIC,
    albeit one that is < 4GB. One thing to verify is that the physical
    addresses listed here for the APICs (0xfec00000 and 0xfee00000) aren't
    included in the SMAP as valid RAM addresses in both cases. It might be
    useful to boot an i386 CD with 8GB in the machine to see if the MADT
    looks any different in that case.

    -- 
    John Baldwin <jhb@FreeBSD.org>  <><  http://www.FreeBSD.org/~jhb/
    "Power Users Use the Power to Serve"  =  http://www.FreeBSD.org
    _______________________________________________
    freebsd-stable@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-stable
    To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
    

  • Next message: John Baldwin: "Re: Problems with AMD64 and 8 GB RAM?"

    Relevant Pages

    • Re: panic: probing for non-PCI bus
      ... then FreeBSD won't find any APICs and won't be ... >> able to trust ACPI PCI interrupt routing. ... >> the MADT isn't found and used. ... drivers so that for your case the mptable PCI bridge drivers ...
      (freebsd-current)
    • Re: HEADSUP: New i386 interrupt and SMP code..
      ... >> for this is that ACPI's APIC enumerator needs to be able ... The MP Table provides PCI interrupt routing information ... in addition to enumerating APICs. ... is not listed in the MADT, but in _PRT objects in the ACPI namespace. ...
      (freebsd-arch)
    • Re: panic: probing for non-PCI bus
      ... ACPI has worked before, and it still ... acpu_cpu is not the same thing as CPUs listed in the MADT. ... then FreeBSD won't find any APICs and won't be ... able to trust ACPI PCI interrupt routing. ...
      (freebsd-current)
    • Re: panic: probing for non-PCI bus
      ... > acpu_cpu is not the same thing as CPUs listed in the MADT. ... then FreeBSD won't find any APICs and won't be ... > able to trust ACPI PCI interrupt routing. ...
      (freebsd-current)
    • panic: resource_list_add: resource entry is busy
      ... It boots fine with ACPI disabled. ... APIC: Using the MADT enumerator. ... CPU: IntelPentiumM processor 1.60GHz ... ioapic0: intpin 2 trigger: edge ...
      (freebsd-current)