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] dom0 crash with unstable

To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: Re: [Xen-devel] dom0 crash with unstable
From: "Bryan D. Payne" <bryan@xxxxxxxxxxxx>
Date: Tue, 6 Oct 2009 15:02:46 -0400
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Delivery-date: Tue, 06 Oct 2009 12:03:17 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=ft0EF0P3Cq0qz/QhXrxk8+59CULDdvI5N1T09INAT/8=; b=x0+h31K9SVvlnN735XqEIAHPozKDV/xlTQJBxQcgmKgOxJu7OTbHJCkeTWOv6MbRJ8 p+CqhtrmZwv+RT9e55+0aJ7nhxTmJ2YLljPppsWeAI8qqJiArHbZJzGBxjblz1fCLgdJ T9+htff8LI8GgKvtSD8TCmBBVmqX1DCW+stfg=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=I127eyZfohvPEwJnwAjG6YpyLC7qV47DM29gc0rz3O+gr9wN8hsdJoNxkSJTpq+l2q LiSnT/WKTjxOpi9mFJ7UiAy0nqcmFp5zKsDoaH8dyJDw1em43GYG1EgCEx1J2pbJA2tO aBN+Ktt1BhCDk6syw0Ox+4LlnvGZwzz8Qg4dM=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4ACB92C5.4010204@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: <64bddf0e0909301105l18c6a3f6ie59af261b1532fe2@xxxxxxxxxxxxxx> <4AC3EE07.3010000@xxxxxxxx> <64bddf0e0910010635wc085961tf55000d4305da2bf@xxxxxxxxxxxxxx> <4AC518A1.8080905@xxxxxxxx> <64bddf0e0910060813v2f2d4149wf2898653719d6ba3@xxxxxxxxxxxxxx> <4ACB70F0.5020502@xxxxxxxx> <64bddf0e0910061023t58828929i99da6a63155e82c@xxxxxxxxxxxxxx> <4ACB8462.1040102@xxxxxxxx> <64bddf0e0910061125n51ffa964s3c589d1d59621fe5@xxxxxxxxxxxxxx> <4ACB92C5.4010204@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
> That's almost certainly a kernel panic of some kind.  Working out where
> it came from will be rather tedious: you need to look through the stack
> dump to find code-ish looking addresses then x/i them (they'll be the
> same basic format as 0xffffffff8xxxxxxx).

Nice ;-)  I'll let you know what I find out.

>> (XEN) ----[ Xen-3.5-unstable  x86_64  debug=y  Not tainted ]----
>> (XEN) CPU:    0
>> (XEN) RIP:    e008:[<ffff82c48014fe29>] add_pin_to_irq+0x24/0xcc
>> (XEN) RFLAGS: 0000000000010296   CONTEXT: hypervisor
>
> That shouldn't happen.  Sounds like it might be fall-out from the recent
> interrupt changes in Xen.  Did you supply "noapic" to Xen, dom0 or both?

Just Xen.  Should it go to both?

-bryan

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