Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 31 Mar 2005 08:02:07 -0500
From:      John Baldwin <jhb@FreeBSD.org>
To:        "Greg 'groggy' Lehey" <grog@FreeBSD.org>
Cc:        FreeBSD-amd64@FreeBSD.org
Subject:   Re: Problems with AMD64 and 8 GB RAM?
Message-ID:  <7e7866bad9099b3d8a8e0f174b6229ce@FreeBSD.org>
In-Reply-To: <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> <20050331054911.GN6252@wantadilla.lemis.com>

next in thread | previous in thread | raw e-mail | index | archive | help

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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7e7866bad9099b3d8a8e0f174b6229ce>