Getting IOAPIC errors in xl dmesg on old hardware

Getting IOAPIC errors in xl dmesg on old hardware

[Anthony Wright]

[-- Attachment #1: Type: text/plain, Size: 331 bytes --]

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.

[-- Attachment #2: dell-optiplex-gx100-xl-dmesg.log --]
[-- Type: text/plain, Size: 3714 bytes --]

 __  __            _  _    _   _ 
 \ \/ /___ _ __   | || |  / | / |
  \  // _ \ '_ \  | || |_ | | | |
  /  \  __/ | | | |__   _|| |_| |
 /_/\_\___|_| |_|    |_|(_)_(_)_|
                                 
(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)
(XEN) ACPI: RSDP 000FD790, 0014 (r0 DELL  )
(XEN) ACPI: RSDT 000FD7A4, 0028 (r1 DELL    GX100          7 ASL        61)
(XEN) ACPI: FACP 000FD7CC, 0074 (r1 DELL    GX100          7 ASL        61)
(XEN) ACPI: DSDT FFFE5000, 1801 (r1   DELL    dt_ex     1000 MSFT  100000B)
(XEN) ACPI: FACS 1FEAE000, 0040
(XEN) Xen heap: 9MB (9784kB)
(XEN) Domain heap initialised
(XEN) Table is not found!
(XEN) Local APIC disabled by BIOS -- you can enable it with "lapic"
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 595.063 MHz processor.
(XEN) I/O virtualisation disabled
(XEN) TSC only partially writable
(XEN) Platform timer is 3.579MHz ACPI PM Timer
(XEN) Allocated console ring of 16 KiB.
(XEN) Brought up 1 CPUs
(XEN) xenoprof: Initialization failed. No APIC
(XEN) *** LOADING DOMAIN 0 ***
(XEN)  Xen  kernel: 32-bit, PAE, lsb
(XEN)  Dom0 kernel: 32-bit, PAE, lsb, paddr 0x1000000 -> 0x1b38000
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN)  Dom0 alloc.:   000000001c000000->000000001e000000 (107972 pages to be allocated)
(XEN)  Init. ramdisk: 000000001f4ef000->000000001fdffca4
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN)  Loaded kernel: c1000000->c1b38000
(XEN)  Init. ramdisk: c1b38000->c2448ca4
(XEN)  Phys-Mach map: c2449000->c24bcb54
(XEN)  Start info:    c24bd000->c24bd47c
(XEN)  Page tables:   c24be000->c24d7000
(XEN)  Boot stack:    c24d7000->c24d8000
(XEN)  TOTAL:         c0000000->c2800000
(XEN)  ENTRY ADDRESS: c173e000
(XEN) Dom0 has maximum 1 VCPUs
(XEN) Scrubbing Free RAM: done.
(XEN) Xen trace buffers: disabled
(XEN) Std. Loglevel: Errors and warnings
(XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
(XEN) Xen is relinquishing VGA console.
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen)
(XEN) Freed 188kB init memory.
(XEN) traps.c:2388:d0 Domain attempted WRMSR 000000c1 from 0x0000000000000000 to 0x000000000000abcd.
(XEN) ERROR: Unable to locate IOAPIC for GSI 13
(XEN) No IOAPIC for GSI 13
(XEN) ERROR: Unable to locate IOAPIC for GSI 8
(XEN) No IOAPIC for GSI 8
(XEN) ERROR: Unable to locate IOAPIC for GSI 6
(XEN) No IOAPIC for GSI 6
(XEN) ERROR: Unable to locate IOAPIC for GSI 1
(XEN) No IOAPIC for GSI 1
(XEN) ERROR: Unable to locate IOAPIC for GSI 12
(XEN) No IOAPIC for GSI 12
(XEN) ERROR: Unable to locate IOAPIC for GSI 4
(XEN) No IOAPIC for GSI 4
(XEN) ERROR: Unable to locate IOAPIC for GSI 3
(XEN) No IOAPIC for GSI 3
(XEN) ERROR: Unable to locate IOAPIC for GSI 7
(XEN) No IOAPIC for GSI 7
(XEN) ERROR: Unable to locate IOAPIC for GSI 11
(XEN) No IOAPIC for GSI 11
(XEN) ERROR: Unable to locate IOAPIC for GSI 10
(XEN) No IOAPIC for GSI 10
(XEN) ERROR: Unable to locate IOAPIC for GSI 5
(XEN) No IOAPIC for GSI 5
(XEN) ERROR: Unable to locate IOAPIC for GSI 5
(XEN) No IOAPIC for GSI 5

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

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

Re: Getting IOAPIC errors in xl dmesg on old hardware

[Jan Beulich]

>>> On 23.09.11 at 12:34, Anthony Wright <anthony@overnetdata.com> 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?

Also, did you try following what this message

(XEN) Local APIC disabled by BIOS -- you can enable it with "lapic"

is suggesting?

Jan

Re: Getting IOAPIC errors in xl dmesg on old hardware

[Anthony Wright]

On 23/09/2011 11:49, Jan Beulich wrote:
>>>> On 23.09.11 at 12:34, Anthony Wright <anthony@overnetdata.com> 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.

Re: Getting IOAPIC errors in xl dmesg on old hardware

[Konrad Rzeszutek Wilk]

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?

Re: Getting IOAPIC errors in xl dmesg on old hardware

[Anthony Wright]

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
error messages in 'xl dmesg', and wondered whether I can safely ignore
them, or whether they're indicative of a more serious problem.

Re: Getting IOAPIC errors in xl dmesg on old hardware

[Konrad Rzeszutek Wilk]

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.

Re: Getting IOAPIC errors in xl dmesg on old hardware

[Anthony Wright]

On 26/09/2011 14:59, Konrad Rzeszutek Wilk wrote:
> 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.
I can understand where you're coming from, and since the system seems to
work fine despite the errors I'm not too worried, but please don't
discount systems just because they're old. Despite the fact that the
system is over 10 years old, it's still quite a capable machine, I can
run (or could with 3.4.1) dom0 in 128MB of ram leaving 380MB for DomUs.
I've got a fair number of low memory, low cpu, paravirtualized DomUs
that run quite happily on the machine.