[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] 4.2.3 - xen: vector 0x2 is not implemented



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.

-boris


It's a kernel issue rather than a Xen one BTW.

Ian.

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

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


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


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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.