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 10:31:07 -0400 Message-ID: <5254172B.8050803@oracle.com> References: <525348C5.5060508@crc.id.au> <1381236125.3804.75.camel@hastur.hellion.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VTYHI-0001Jc-KU for xen-devel@lists.xenproject.org; Tue, 08 Oct 2013 14:28:48 +0000 In-Reply-To: <1381236125.3804.75.camel@hastur.hellion.org.uk> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Campbell , Steven Haigh Cc: xen-devel@lists.xenproject.org List-Id: xen-devel@lists.xenproject.org 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@lists.xen.org >> http://lists.xen.org/xen-devel > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel