Date: Wed, 30 Mar 2005 23:01:03 -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: <657eb6604d1e00368d77f047a8b5e074@FreeBSD.org> In-Reply-To: <20050331015429.GH6252@wantadilla.lemis.com> References: <20050330222439.GU84137@wantadilla.lemis.com> <20050330223546.GA4705@troutmask.apl.washington.edu> <20050330224445.GW84137@wantadilla.lemis.com> <200503311032.33718.doconnor@gsoft.com.au> <20050331015429.GH6252@wantadilla.lemis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mar 30, 2005, at 8:54 PM, Greg 'groggy' Lehey wrote: >> lapic0: LINT1 trigger: edge >> lapic0: LINT1 polarity: high >> lapic1: Routing NMI -> LINT1 >> lapic1: LINT1 trigger: edge >> lapic1: LINT1 polarity: high >> -ioapic0 <Version 0.3> irqs 0-23 on motherboard >> +ioapic0 <Version 0.0> irqs 0-23 on motherboard >> cpu0 BSP: >> ID: 0x00000000 VER: 0x00040010 LDR: 0x01000000 DFR: 0x0fffffff >> lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff This shows that in the - case the APIC is broken somehow (0.0 isn't a valid I/O APIC version). It would seem that the system has mapped RAM over top of the I/O APIC perhaps? 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. The local APIC portion seems ok though. -- 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?657eb6604d1e00368d77f047a8b5e074>