Anthony Wright
2011-Sep-23 10:34 UTC
[Xen-devel] Getting IOAPIC errors in xl dmesg on old hardware
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-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Jan Beulich
2011-Sep-23 10:49 UTC
Re: [Xen-devel] Getting IOAPIC errors in xl dmesg on old hardware
>>> 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 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Anthony Wright
2011-Sep-23 12:04 UTC
Re: [Xen-devel] Getting IOAPIC errors in xl dmesg on old hardware
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. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Konrad Rzeszutek Wilk
2011-Sep-23 13:33 UTC
Re: [Xen-devel] Getting IOAPIC errors in xl dmesg on old hardware
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? _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Anthony Wright
2011-Sep-23 13:39 UTC
Re: [Xen-devel] Getting IOAPIC errors in xl dmesg on old hardware
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. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Konrad Rzeszutek Wilk
2011-Sep-26 13:59 UTC
Re: [Xen-devel] Getting IOAPIC errors in xl dmesg on old hardware
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 theseProbably 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@lists.xensource.com http://lists.xensource.com/xen-devel
Anthony Wright
2011-Sep-26 15:07 UTC
Re: [Xen-devel] Getting IOAPIC errors in xl dmesg on old hardware
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. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel