From mboxrd@z Thu Jan 1 00:00:00 1970 From: Boris Ostrovsky Subject: Re: 4.2.3 - xen: vector 0x2 is not implemented Date: Tue, 08 Oct 2013 11:56:04 -0400 Message-ID: <52542B14.7010700@oracle.com> References: <525348C5.5060508@crc.id.au> <1381236125.3804.75.camel@hastur.hellion.org.uk> <5254172B.8050803@oracle.com> <52541994.1000303@crc.id.au> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <52541994.1000303@crc.id.au> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Steven Haigh Cc: xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org 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