From: Steven Haigh <netwiz@crc.id.au>
To: xen-devel@lists.xenproject.org
Subject: 4.2.3 - xen: vector 0x2 is not implemented
Date: Tue, 08 Oct 2013 10:50:29 +1100 [thread overview]
Message-ID: <525348C5.5060508@crc.id.au> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 791 bytes --]
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
Kernel is 3.11.2.
Xen is 4.2.3.
I've seen various random reports of this, but never a follow up on what
seemed to be the issue or a fix. The latest was on the ARM platform, but
may be a different issue.
Has anyone come across these before and found a solution?
Xen 4.2.2 seems unaffected.
Bug Report:
http://xen.crc.id.au/bugs/view.php?id=21
--
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: 836 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 reply other threads:[~2013-10-07 23:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-07 23:50 Steven Haigh [this message]
2013-10-08 12:42 ` 4.2.3 - xen: vector 0x2 is not implemented 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
-- 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=525348C5.5060508@crc.id.au \
--to=netwiz@crc.id.au \
--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.