WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Xen panics with 2.6.32.11

To: "Keir Fraser" <keir.fraser@xxxxxxxxxxxxx>, "Jeremy Fitzhardinge" <jeremy@xxxxxxxx>
Subject: Re: [Xen-devel] Xen panics with 2.6.32.11
From: "Jan Beulich" <JBeulich@xxxxxxxxxx>
Date: Mon, 12 Apr 2010 11:04:34 +0100
Cc: Bastian Blank <waldi@xxxxxxxxxx>, Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 12 Apr 2010 03:05:28 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4BBBB6C0.6050006@xxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4BBBB1EC.1030403@xxxxxxxx> <4BBBB6C0.6050006@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
>>> Jeremy Fitzhardinge <jeremy@xxxxxxxx> 07.04.10 00:33 >>>
>On 04/06/2010 03:13 PM, Jeremy Fitzhardinge wrote:
>> Current xen-unstable crashes when booting xen/stable-2.6.32.x 
>> (2.6.32.11).  I haven't
>> verified it yet, but I guess this is Bastian's patch (537451477469).  
>> Or could it be Jan's 4f796e29987c?
>
>Looks like 4f796e29987c is the culprit; reverting it lets the kernel 
>boot again.

Oh, looks like the spin_lock() needs to be a spin_lock_irqsave() there.

>Before the crash, I also see lots of complaints from Xen while setting 
>up interrupts:

That suggests your kernel might run through both (IO-APIC write and
hypercall) paths (or one of them more than once), which would seem
more like a kernel problem.

Jan


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>