From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Wright Subject: Re: Getting IOAPIC errors in xl dmesg on old hardware Date: Fri, 23 Sep 2011 13:04:27 +0100 Message-ID: <4E7C75CB.3010509@overnetdata.com> References: <4E7C60B1.3000901@overnetdata.com> <4E7C803E02000078000578A3@nat28.tlf.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4E7C803E02000078000578A3@nat28.tlf.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jan Beulich Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On 23/09/2011 11:49, Jan Beulich wrote: >>>> On 23.09.11 at 12:34, Anthony Wright wrote: >> I am getting a series of IOAPIC errors in xl dmesg on a Dell OptiPlex >> GX100 machine (bought in 2000). I also get an error from traps.c which >> is very similar to the one in the 'Getting mm.c errors from xl dmesg on >> certain hardware' thread. This happens during system startup with no >> DomUs running. I have attached the xl dmesg log. > Seems like the kernel is trying to use IO-APIC despite the LAPIC being > unavailable. Is this with a pv-ops kernel or a forward port one? Which > version? Sorry - this is xen 4.1.1 with vanilla linux 3.0.4 > Also, did you try following what this message > > (XEN) Local APIC disabled by BIOS -- you can enable it with "lapic" I tried putting lapic on the xen command line, and while I got a message in dmesg saying it had been disabled in the bios, but then re-enabled, the IOAPIC errors were still present.