From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: andrew.cooper3@citrix.com, xen-devel@lists.xenproject.org
Subject: Re: IO-APIC interrupts getting stuck
Date: Thu, 15 Jan 2015 11:28:58 +0100 [thread overview]
Message-ID: <54B7966A.6040309@citrix.com> (raw)
In-Reply-To: <54A6C55D02000078000C4B03@mail.emea.novell.com>
El 02/01/15 a les 17.20, Jan Beulich ha escrit:
>>>> Roger Pau Monné<roger.pau@citrix.com> 12/22/14 7:44 PM >>>
>> No, the same box I have with Linux doesn't use the IO-APIC re-route
>> quirk. I've also tested this on different hardware and when using
>> FreeBSD with the new IO APIC Ack method I always end up in this stuck
>> state, so I don't think it's a hardware errata/issue.
>
> Understood. I'm afraid there's not much we can do here without you gathering
> more data - one particularly useful thing would be kind of a trace of states for
> the first respective IRQ delivery inside Xen, allowing to then compare the
> progress with PVH Linux and FreeBSD. There must be a difference after all.
What I said above was not completely true, the other box I've used for
testing was also a Nehalem with two IO-APICs. Now I've tested on a
Nehalem (X3450) with a single IO-APIC and it works fine. I'm still not
sure if this issue is limited to the Nehalem family with two IO-APICs,
or if newer families also have the same issue if more than one IO-APIC
is present. Switching to the "old" IO-APIC ack mode seems to solve the
problem (or at least mitigate it).
This is quite bad on those systems because as soon as one of the IO-APIC
IRQs gets stuck everything starts falling apart and MSI interrupts also
get stuck.
Roger.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2015-01-15 10:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-16 17:34 IO-APIC interrupts getting stuck Roger Pau Monné
2014-12-16 17:59 ` Andrew Cooper
2014-12-17 11:40 ` Roger Pau Monné
2014-12-17 12:51 ` Roger Pau Monné
2014-12-18 10:41 ` Jan Beulich
2014-12-22 18:43 ` Roger Pau Monné
2015-01-02 16:20 ` Jan Beulich
2015-01-15 10:28 ` Roger Pau Monné [this message]
2015-01-05 8:50 ` Jan Beulich
2015-01-05 10:14 ` Roger Pau Monné
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54B7966A.6040309@citrix.com \
--to=roger.pau@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.