Re: [Xen-devel] Getting IOAPIC errors in xl dmesg on old hardware

[Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>]

On Fri, Sep 23, 2011 at 02:39:12PM +0100, Anthony Wright wrote:
> On 23/09/2011 14:33, Konrad Rzeszutek Wilk wrote:
> > 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?
> Yup 512MB
> 
> 3.4.1 with 2.6.18 works fine on it. 4.4.1 with 3.0.4 also seems to work
> fine, though it does seem to use an awful lot of ram (something I'm
> going to have a closer look at shortly). It's just that I get these

Probably Xen-SWIOTLB eating up 64MB, then there are the per_cpu maps
and whole bunch of other stuff..
> error messages in 'xl dmesg', and wondered whether I can safely ignore
> them, or whether they're indicative of a more serious problem.

I am not sure what to tell you. Your hardware is well.. so old
that I am not going to take a look at this (from a Linux kernel perspective)
for a looooong loooooong time.


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel