thr3ads.net - Xen users - Lots of IOAPIC or GSI related errors [Jan 2013]

If this information is useful, please help other people find it:
Share via:

Sven Köhler

2013-Jan-06 07:34 UTC

Lots of IOAPIC or GSI related errors

Hi,

I''m getting lots of IOAPIC and GSI related errors, both in
xen''s and the
dom0 kernel''s dmesg (see below).

It might have to do with the fact, that I added "acpi=ht" to my xen
command line. Previously to adding that, the errors didn''t show up. But
I added it, because it was said to fix my reboot problems. But along
with adding acpi=ht, I also upgraded dom0 to kernel 3.7.1. I''m using
Xen
4.2.

My grub settings are as follows:
kernel /boot/xen.gz dom0_mem=512M acpi=ht vga=mode-0x314
module /boot/vmlinuz root=/dev/md0 ro quiet


Regards,
  Sven



# xm dmesg|egrep -i "apic|gsi"
(XEN) ACPI: APIC BF780390, 00AC (r1 7522MS A7522800 20110319 MSFT       97)
(XEN) Processor #0 7:10 APIC version 21
(XEN) Processor #2 7:10 APIC version 21
(XEN) Processor #4 7:10 APIC version 21
(XEN) Processor #6 7:10 APIC version 21
(XEN) Processor #1 7:10 APIC version 21
(XEN) Processor #3 7:10 APIC version 21
(XEN) Processor #5 7:10 APIC version 21
(XEN) Processor #7 7:10 APIC version 21
(XEN) Enabling APIC mode:  Flat.  Using 1 I/O APICs
(XEN) ENABLING IO-APIC IRQs
(XEN) ERROR: Unable to locate IOAPIC for GSI 9
(XEN) No IOAPIC for GSI 9
(XEN) ERROR: Unable to locate IOAPIC for GSI 8
(XEN) No IOAPIC for GSI 8
(XEN) ERROR: Unable to locate IOAPIC for GSI 13
(XEN) No IOAPIC for GSI 13
(XEN) ERROR: Unable to locate IOAPIC for GSI 4
(XEN) No IOAPIC for GSI 4
(XEN) ERROR: Unable to locate IOAPIC for GSI 1
(XEN) No IOAPIC for GSI 1
(XEN) ERROR: Unable to locate IOAPIC for GSI 17
(XEN) No IOAPIC for GSI 17
(XEN) ERROR: Unable to locate IOAPIC for GSI 17
(XEN) No IOAPIC for GSI 17
(XEN) ERROR: Unable to locate IOAPIC for GSI 16
(XEN) No IOAPIC for GSI 16
(XEN) ERROR: Unable to locate IOAPIC for GSI 21
(XEN) No IOAPIC for GSI 21
(XEN) ERROR: Unable to locate IOAPIC for GSI 19
(XEN) No IOAPIC for GSI 19
(XEN) ERROR: Unable to locate IOAPIC for GSI 18
(XEN) No IOAPIC for GSI 18
(XEN) ERROR: Unable to locate IOAPIC for GSI 23
(XEN) No IOAPIC for GSI 23
(XEN) ERROR: Unable to locate IOAPIC for GSI 19
(XEN) No IOAPIC for GSI 19
(XEN) ERROR: Unable to locate IOAPIC for GSI 18
(XEN) No IOAPIC for GSI 18
(XEN) ERROR: Unable to locate IOAPIC for GSI 23
(XEN) No IOAPIC for GSI 23
(XEN) ERROR: Unable to locate IOAPIC for GSI 19
(XEN) No IOAPIC for GSI 19
(XEN) ERROR: Unable to locate IOAPIC for GSI 16
(XEN) No IOAPIC for GSI 16
(XEN) ERROR: Unable to locate IOAPIC for GSI 18
(XEN) No IOAPIC for GSI 18
(XEN) ERROR: Unable to locate IOAPIC for GSI 23
(XEN) No IOAPIC for GSI 23
(XEN) ERROR: Unable to locate IOAPIC for GSI 16
(XEN) No IOAPIC for GSI 16
(XEN) ERROR: Unable to locate IOAPIC for GSI 21
(XEN) No IOAPIC for GSI 21
(XEN) ERROR: Unable to locate IOAPIC for GSI 19
(XEN) No IOAPIC for GSI 19
(XEN) ERROR: Unable to locate IOAPIC for GSI 23
(XEN) No IOAPIC for GSI 23
(XEN) ERROR: Unable to locate IOAPIC for GSI 19
(XEN) No IOAPIC for GSI 19
(XEN) ERROR: Unable to locate IOAPIC for GSI 18
(XEN) No IOAPIC for GSI 18
(XEN) ERROR: Unable to locate IOAPIC for GSI 18
(XEN) No IOAPIC for GSI 18

# dmesg|egrep -i "apic|gsi"
[    0.000000] ACPI: APIC 00000000bf780390 000AC (v01 7522MS A7522800
20110319 MSFT 00000097)
[    0.000000] ACPI: Local APIC address 0xfee00000
[    0.000000] ACPI: Local APIC address 0xfee00000
[    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
[    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
[    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x04] enabled)
[    0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x06] enabled)
[    0.000000] ACPI: LAPIC (acpi_id[0x05] lapic_id[0x01] enabled)
[    0.000000] ACPI: LAPIC (acpi_id[0x06] lapic_id[0x03] enabled)
[    0.000000] ACPI: LAPIC (acpi_id[0x07] lapic_id[0x05] enabled)
[    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x07] enabled)
[    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x88] disabled)
[    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x89] disabled)
[    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x8a] disabled)
[    0.000000] ACPI: LAPIC (acpi_id[0x0c] lapic_id[0x8b] disabled)
[    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
[    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI
0-23
[    0.000000] nr_irqs_gsi: 40
[    1.853258] xen: registering gsi 9 triggering 0 polarity 0
[    1.853266] xen: --> pirq=9 -> irq=9 (gsi=9)
[    1.853273] Failed to setup GSI :9, err_code:-22
[    1.853277] xen: --> pirq=1 -> irq=1 (gsi=1)
[    1.853279] xen: --> pirq=2 -> irq=2 (gsi=2)
[    1.853281] xen: --> pirq=3 -> irq=3 (gsi=3)
[    1.853283] xen: --> pirq=4 -> irq=4 (gsi=4)
[    1.853285] xen: --> pirq=5 -> irq=5 (gsi=5)
[    1.853287] xen: --> pirq=6 -> irq=6 (gsi=6)
[    1.853289] xen: --> pirq=7 -> irq=7 (gsi=7)
[    1.853291] xen: --> pirq=8 -> irq=8 (gsi=8)
[    1.853293] xen: --> pirq=10 -> irq=10 (gsi=10)
[    1.853295] xen: --> pirq=11 -> irq=11 (gsi=11)
[    1.853298] xen: --> pirq=12 -> irq=12 (gsi=12)
[    1.853300] xen: --> pirq=13 -> irq=13 (gsi=13)
[    1.853302] xen: --> pirq=14 -> irq=14 (gsi=14)
[    1.853303] xen: --> pirq=15 -> irq=15 (gsi=15)
[    2.470162] ACPI: Using IOAPIC for interrupt routing
[    2.579698] xen: registering gsi 8 triggering 1 polarity 0
[    2.579705] Failed to setup GSI :8, err_code:-22
[    2.579741] xen: registering gsi 13 triggering 1 polarity 0
[    2.579744] Failed to setup GSI :13, err_code:-22
[    2.579943] xen: registering gsi 4 triggering 1 polarity 0
[    2.579946] Failed to setup GSI :4, err_code:-22
[    2.580017] xen: registering gsi 1 triggering 1 polarity 0
[    2.580020] Failed to setup GSI :1, err_code:-22
[    2.585215] xen: registering gsi 17 triggering 0 polarity 1
[    2.585227] xen: --> pirq=17 -> irq=17 (gsi=17)
[    2.585230] Failed to setup GSI :17, err_code:-22
[    2.585238] xen: registering gsi 17 triggering 0 polarity 1
[    2.585241] Failed to setup GSI :17, err_code:-22
[    2.586716] xen: registering gsi 16 triggering 0 polarity 1
[    2.586723] xen: --> pirq=16 -> irq=16 (gsi=16)
[    2.586727] Failed to setup GSI :16, err_code:-22
[    2.586755] xen: registering gsi 21 triggering 0 polarity 1
[    2.586760] xen: --> pirq=21 -> irq=21 (gsi=21)
[    2.586762] Failed to setup GSI :21, err_code:-22
[    2.586789] xen: registering gsi 19 triggering 0 polarity 1
[    2.586793] xen: --> pirq=19 -> irq=19 (gsi=19)
[    2.586796] Failed to setup GSI :19, err_code:-22
[    2.586824] xen: registering gsi 18 triggering 0 polarity 1
[    2.586829] xen: --> pirq=18 -> irq=18 (gsi=18)
[    2.586831] Failed to setup GSI :18, err_code:-22
[    2.586876] xen: registering gsi 23 triggering 0 polarity 1
[    2.586883] xen: --> pirq=23 -> irq=23 (gsi=23)
[    2.586886] Failed to setup GSI :23, err_code:-22
[    2.586913] xen: registering gsi 19 triggering 0 polarity 1
[    2.586915] Failed to setup GSI :19, err_code:-22
[    2.586942] xen: registering gsi 18 triggering 0 polarity 1
[    2.586944] Failed to setup GSI :18, err_code:-22
[    2.586972] xen: registering gsi 23 triggering 0 polarity 1
[    2.586975] Failed to setup GSI :23, err_code:-22
[    2.663645] xen: registering gsi 19 triggering 0 polarity 1
[    2.663651] Failed to setup GSI :19, err_code:-22
[    2.759973] xen: registering gsi 16 triggering 0 polarity 1
[    2.759978] Failed to setup GSI :16, err_code:-22
[    2.761097] xen: registering gsi 18 triggering 0 polarity 1
[    2.761102] Failed to setup GSI :18, err_code:-22
[    2.779569] xen: registering gsi 23 triggering 0 polarity 1
[    2.779574] Failed to setup GSI :23, err_code:-22
[    2.799584] xen: registering gsi 16 triggering 0 polarity 1
[    2.799589] Failed to setup GSI :16, err_code:-22
[    2.800308] xen: registering gsi 21 triggering 0 polarity 1
[    2.800313] Failed to setup GSI :21, err_code:-22
[    2.801022] xen: registering gsi 19 triggering 0 polarity 1
[    2.801027] Failed to setup GSI :19, err_code:-22
[    2.801733] xen: registering gsi 23 triggering 0 polarity 1
[    2.801737] Failed to setup GSI :23, err_code:-22
[    2.802431] xen: registering gsi 19 triggering 0 polarity 1
[    2.802435] Failed to setup GSI :19, err_code:-22
[    2.803131] xen: registering gsi 18 triggering 0 polarity 1
[    2.803135] Failed to setup GSI :18, err_code:-22
[    9.120069] xen: registering gsi 18 triggering 0 polarity 1
[    9.120081] Failed to setup GSI :18, err_code:-22

Ian Campbell

2013-Jan-07 11:23 UTC

head link

Re: Lots of IOAPIC or GSI related errors

On Sun, 2013-01-06 at 07:34 +0000, Sven Köhler wrote:> Hi,
> 
> I'm getting lots of IOAPIC and GSI related errors, both in xen's
and the
> dom0 kernel's dmesg (see below).
> 
> It might have to do with the fact, that I added "acpi=ht" to my
xen
> command line. Previously to adding that, the errors didn't show up. But
> I added it, because it was said to fix my reboot problems. But along
> with adding acpi=ht, I also upgraded dom0 to kernel 3.7.1.
Any chance you could separate those two changes and isolatethe one which
causes the problem?

The docs for acpi=ht say:
        Using `acpi=ht` causes Xen to parse the ACPI tables enough to
        enumerate all CPUs, but will not use other ACPI features.  This is not
        common, and only has an effect if your system is blacklisted.

I doubt this is what you want for a reboot issue.

You should probably investigate the reboot= options instead.

Ian.


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

Sven Köhler

2013-Jan-07 15:13 UTC

head link

Re: Lots of IOAPIC or GSI related errors

Am 07.01.2013 12:23, schrieb Ian Campbell:> On Sun, 2013-01-06 at 07:34 +0000, Sven Köhler wrote:
>> Hi,
>>
>> I''m getting lots of IOAPIC and GSI related errors, both in
xen''s and the
>> dom0 kernel''s dmesg (see below).
>>
>> It might have to do with the fact, that I added "acpi=ht" to
my xen
>> command line. Previously to adding that, the errors didn''t
show up. But
>> I added it, because it was said to fix my reboot problems. But along
>> with adding acpi=ht, I also upgraded dom0 to kernel 3.7.1.
> 
> Any chance you could separate those two changes and isolatethe one which
> causes the problem?
It''s a remote server. I''m pretty sure I''m already
annoying the employees
of my hoster enough, as the machine enters some weired state during
reboot, from which it does never recover - even pushing the reset button
(which I can do remotely) doesn''t work. Hence the hoster''s
employees
always have to turn the machine off and on again.
> The docs for acpi=ht say:
>         Using `acpi=ht` causes Xen to parse the ACPI tables enough to
>         enumerate all CPUs, but will not use other ACPI features.  This is
not
>         common, and only has an effect if your system is blacklisted.
> 
> I doubt this is what you want for a reboot issue.
> 
> You should probably investigate the reboot= options instead.
Did that already. Didn''t help.

The problem is actually known to the hoster. They recommended acpi=ht.
The hoster blamed ACPI and said that disabling ACPI would fix the
problem. However, since I added acpi=ht, I haven''t rebootet the machine
yet.


Do you have any clue what these APIC/GSI error are all about? I mean,
even if you can''t explain why they happen, what do they actually mean?


Regards,
  Sven



_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

Ian Campbell

2013-Jan-07 15:22 UTC

head link

Re: Lots of IOAPIC or GSI related errors

On Mon, 2013-01-07 at 15:13 +0000, Sven Köhler wrote:> Am 07.01.2013 12:23, schrieb Ian Campbell:
> > On Sun, 2013-01-06 at 07:34 +0000, Sven Köhler wrote:
> >> Hi,
> >>
> >> I'm getting lots of IOAPIC and GSI related errors, both in
xen's and the
> >> dom0 kernel's dmesg (see below).
> >>
> >> It might have to do with the fact, that I added
"acpi=ht" to my xen
> >> command line. Previously to adding that, the errors didn't
show up. But
> >> I added it, because it was said to fix my reboot problems. But
along
> >> with adding acpi=ht, I also upgraded dom0 to kernel 3.7.1.
> > 
> > Any chance you could separate those two changes and isolatethe one
which
> > causes the problem?
> 
> It's a remote server. I'm pretty sure I'm already annoying the
employees
> of my hoster enough, as the machine enters some weired state during
> reboot, from which it does never recover - even pushing the reset button
> (which I can do remotely) doesn't work. Hence the hoster's
employees
> always have to turn the machine off and on again.
> 
> > The docs for acpi=ht say:
> >         Using `acpi=ht` causes Xen to parse the ACPI tables enough to
> >         enumerate all CPUs, but will not use other ACPI features. 
This is not
> >         common, and only has an effect if your system is blacklisted.
> > 
> > I doubt this is what you want for a reboot issue.
> > 
> > You should probably investigate the reboot= options instead.
> 
> Did that already. Didn't help.
> 
> The problem is actually known to the hoster. They recommended acpi=ht.
> The hoster blamed ACPI and said that disabling ACPI would fix the
> problem. However, since I added acpi=ht, I haven't rebootet the machine
yet.
> 
> 
> Do you have any clue what these APIC/GSI error are all about? I mean,
> even if you can't explain why they happen, what do they actually mean?
GSIs are interrupts, the ACPI tables contain mappings from interrupts to
APICs, which are the interrupt controllers. The message is basically
saying it can't determine which APIC is responsible for the given
interrupt -- since you've explicitly asked Xen not to use ACPI for
anything other than hyperthreading that isn't unexpected.

I think there is an older pre-ACPI table which is supposed to also
contains a subset of this mapping, but they are often incomplete or
buggy on systems which supports ACPI (or more specifically, where
Windows would use ACPI). That's getting a bit outside the stuff I can
recall off the top of my head though I'm afraid.

Turning off ACPI on any half-way modern system is generally not going to
result in everything working properly.

Ian.



_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

Sven Köhler

2013-Jan-07 15:45 UTC

head link

Re: Lots of IOAPIC or GSI related errors

Am 07.01.2013 16:22, schrieb Ian Campbell:> Turning off ACPI on any half-way modern system is generally not going to
> result in everything working properly.
Well, I can''t switch the hardware. It''s an MSI X58 Pro-E
board. If you
dig the archive, you''ll find a thread about my reboot issues. And
nobody
came up with a solution. Problem is, that kernel on bare metal reboots
fine, but kernel + xen doesn''t. I compared the reboot code of Xen and
the Linux kernel, and it was identical. No surprise there.

To be honest, I still suspect that Xen (maybe Xen''s ACPI
implementation?) is less compatible with a probably broken MSI BIOS. But
for now, I have to somehow try to the downtime caused by the machine
hanging in some mysterious undefined state during reboot.


I really want to take it seriously when you say that if ACPI is turned
off, something wouldn''t work properly (and the GSI errors worry me!)
but
what do you expect to be broken? It''s a server machine. I really
don''t
care about loosing the ability to adjust the CPU frequency or suspend to
RAM or anything fancy. The machine must run without crashing, and reboot
once in a while for xen/kernel upgrade.


I''m also not sure what happens, if acpi=ht is passed to the dom0 kernel
only, but not the hypervisor. Currently, both hypervisor and dom0 kernel
use acpi=ht.



Regards,
  Sven



_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

Ian Campbell

2013-Jan-07 15:50 UTC

head link

Re: Lots of IOAPIC or GSI related errors

On Mon, 2013-01-07 at 15:45 +0000, Sven Köhler wrote:> I really want to take it seriously when you say that if ACPI is turned
> off, something wouldn't work properly (and the GSI errors worry me!)
but
> what do you expect to be broken? It's a server machine. I really
don't
> care about loosing the ability to adjust the CPU frequency or suspend to
> RAM or anything fancy. The machine must run without crashing, and reboot
> once in a while for xen/kernel upgrade.
I'd expect that some devices don't receive interrupts properly (or at
all). If you haven't noticed any devices misbehaving then maybe none of
the affected devices are ones you care about.

Ian.



_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

Xen users - Jan 2013 - Lots of IOAPIC or GSI related errors

Lots of IOAPIC or GSI related errors

Re: Lots of IOAPIC or GSI related errors

Re: Lots of IOAPIC or GSI related errors

Re: Lots of IOAPIC or GSI related errors

Re: Lots of IOAPIC or GSI related errors

Re: Lots of IOAPIC or GSI related errors