From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Steven Haigh <netwiz@crc.id.au>
Cc: xen-devel@lists.xen.org
Subject: Re: 4.2.3 - xen: vector 0x2 is not implemented
Date: Tue, 08 Oct 2013 11:56:04 -0400 [thread overview]
Message-ID: <52542B14.7010700@oracle.com> (raw)
In-Reply-To: <52541994.1000303@crc.id.au>
On 10/08/2013 10:41 AM, Steven Haigh wrote:
> On 10/09/2013 01:31 AM, Boris Ostrovsky wrote:
>> On 10/08/2013 08:42 AM, Ian Campbell wrote:
>>> On Tue, 2013-10-08 at 10:50 +1100, Steven Haigh wrote:
>>>> Hi all,
>>>>
>>>> I've had a report of a host starting to give this output:
>>>> Oct 7 19:36:37 kernel: INFO: rcu_sched self-detected stall on CPU { 2}
>>>> (t=273561 jiffies g=17919 c=17918 q=9688)
>>>> Oct 7 19:36:37 kernel: sending NMI to all CPUs:
>>>> Oct 7 19:36:37 kernel: xen: vector 0x2 is not implemented
>>> This bit is just a symptom triggered by the initial rcu stall which is
>>> your real problem.
>>>
>>> That said I thought the NMI thing was fixed recently, which might have
>>> gotten you better debugging on the rcu problem.
>> This went into v3.12-rc1 (commit 6efa20e).
>>
>> Steven, can you try your test with newer kernels that have this fix? With
>> it we should be able to see where the stall is happening.
> Sadly I can't easily rebuild this to 3.12. Is it possible to get a
> version / patch / commit that will work with 3.11.x?
I am not sure I understand what you are asking for. A backport of the
patch to 3.11.x so that you apply it on top of your sources and build it
yourself?
-boris
next prev parent reply other threads:[~2013-10-08 15:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-07 23:50 4.2.3 - xen: vector 0x2 is not implemented Steven Haigh
2013-10-08 12:42 ` Ian Campbell
2013-10-08 14:31 ` Boris Ostrovsky
2013-10-08 14:41 ` Steven Haigh
2013-10-08 15:56 ` Boris Ostrovsky [this message]
2013-10-09 0:25 ` Steven Haigh
-- strict thread matches above, loose matches on Subject: below --
2013-10-09 1:53 Boris Ostrovsky
2013-10-09 1:56 ` Steven Haigh
2013-10-09 2:15 Boris Ostrovsky
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=52542B14.7010700@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=netwiz@crc.id.au \
--cc=xen-devel@lists.xen.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).