From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: Getting IOAPIC errors in xl dmesg on old hardware Date: Fri, 23 Sep 2011 09:33:41 -0400 Message-ID: <20110923133341.GD19579@phenom.oracle.com> References: <4E7C60B1.3000901@overnetdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <4E7C60B1.3000901@overnetdata.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: Anthony Wright Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On Fri, Sep 23, 2011 at 11:34:25AM +0100, 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. > __ __ _ _ _ _ > \ \/ /___ _ __ | || | / | / | > \ // _ \ '_ \ | || |_ | | | | > / \ __/ | | | |__ _|| |_| | > /_/\_\___|_| |_| |_|(_)_(_)_| > > (XEN) Xen version 4.1.1 (@[unknown]) (gcc version 4.4.3 (GCC) ) Wed Sep 21 08:25:36 GMT 2011 > (XEN) Latest ChangeSet: unavailable > (XEN) Bootloader: GNU GRUB 0.97 > (XEN) Command line: > (XEN) Video information: > (XEN) VGA is text mode 80x25, font 8x16 > (XEN) VBE/DDC methods: V2; EDID transfer time: 1 seconds > (XEN) Disc information: > (XEN) Found 0 MBR signatures > (XEN) Found 0 EDD information structures > (XEN) Xen-e820 RAM map: > (XEN) 0000000000000000 - 00000000000a0000 (usable) > (XEN) 00000000000f0000 - 0000000000100000 (reserved) > (XEN) 0000000000100000 - 000000001feae000 (usable) > (XEN) 000000001feae000 - 0000000020000000 (reserved) > (XEN) 00000000ffb00000 - 0000000100000000 (reserved) > (XEN) System RAM: 510MB (522552kB) Is that right? 512MB?