From: Steven Haigh <netwiz@crc.id.au>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: xen-devel@lists.xen.org
Subject: Re: 4.2.3 - xen: vector 0x2 is not implemented
Date: Wed, 09 Oct 2013 12:56:41 +1100 [thread overview]
Message-ID: <5254B7D9.8060108@crc.id.au> (raw)
In-Reply-To: <65451e07-a489-4325-aefa-f6f891a0d2cf@default>
[-- Attachment #1.1: Type: text/plain, Size: 2577 bytes --]
On 9/10/2013 12:53 PM, Boris Ostrovsky wrote:
>
> ----- netwiz@crc.id.au wrote:
>
>> On 9/10/2013 2:56 AM, Boris Ostrovsky wrote:
>>> 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?
>>
>> Correct. I have a buildroot set up for building 3.11.x into RPMs that
>> would take a lot of work to change to 3.12. As this is a problem with
>> 3.11 as well (as I don't run or provide 3.12 anywhere), I'd like to
>> test
>> the fix on 3.11.
>
> I am attaching the patch to 3.11.4 (which is exactly the same as the one
> that went into 3.12 btw). I only compile-tested it to make sure that it builds.
>
>>
>> Eventually, it will need to be fixed in the 3.11 series as well.
>>
>
> It's unlikely to go into 3.11 since it's really a new feature and not a bug fix.
Thanks, I'll test this and see what I can turn up. The problems are
happening in 3.11.2 at this stage - which causes the system to become
unresponsive and a load of 45+. It also causes network traffic to stop.
As such, it should probably be looked at as a bugfix for 3.11. Will try
and get further results and revert back when I can provide more feedback.
--
Steven Haigh
Email: netwiz@crc.id.au
Web: https://www.crc.id.au
Phone: (03) 9001 6090 - 0412 935 897
Fax: (03) 8338 0299
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 834 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-10-09 1:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-09 1:53 4.2.3 - xen: vector 0x2 is not implemented Boris Ostrovsky
2013-10-09 1:56 ` Steven Haigh [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-10-09 2:15 Boris Ostrovsky
2013-10-07 23:50 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
2013-10-09 0:25 ` Steven Haigh
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=5254B7D9.8060108@crc.id.au \
--to=netwiz@crc.id.au \
--cc=boris.ostrovsky@oracle.com \
--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 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.