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

Re: [Xen-devel] dom0 crash with unstable

  • To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
  • 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
  • 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=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

> 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?


Xen-devel mailing list



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