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/
Home Products Support Community News


Re: [Xen-devel] dom0 hang in xen-4.0.0-rc5 - possible acpi issue? [WAS:

To: "Nadolski, Ed" <Ed.Nadolski@xxxxxxx>
Subject: Re: [Xen-devel] dom0 hang in xen-4.0.0-rc5 - possible acpi issue? [WAS: Using xen-unstable, dom0 hangs during boot]
From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Date: Wed, 3 Mar 2010 13:18:41 -0500
Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxx>, "Xen-devel@xxxxxxxxxxxxxxxxxxx" <Xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 03 Mar 2010 10:45:20 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <8115AF16522A3D4383C1FF753036713F9B21EB9C@xxxxxxxxxxxxxxxxx>
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: <8115AF16522A3D4383C1FF753036713F9B1B522B@xxxxxxxxxxxxxxxxx> <4B8703B9.9000207@xxxxxxxx> <8115AF16522A3D4383C1FF753036713F9B1B52D8@xxxxxxxxxxxxxxxxx> <20100226144622.GP2761@xxxxxxxxxxx> <8115AF16522A3D4383C1FF753036713F9B1B54B0@xxxxxxxxxxxxxxxxx> <8115AF16522A3D4383C1FF753036713F9B21E600@xxxxxxxxxxxxxxxxx> <20100301151005.GA7881@xxxxxxxxxxxxxxxxxxx> <8115AF16522A3D4383C1FF753036713F9B21EB9C@xxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.19 (2009-01-05)
> I've found out a bit more.  First, I've upgraded to Xen 4.0.0-rc5, but the 
> problem persists. 

> I've pasted some more trace below, including a WARN_ON() before the call to 
> msleep().  The jumps in the timestamps show where msleep() hung and I hit the 
> power button to force it to resume.
> Looks like the serial8250 driver gets IRQ 3 for ttyS1.  I'm not clear what 
> the "will not share" message for IRQ 0 means -- maybe it means Xen won't 
> allow the IRQ to be shared with a guest?  It seems to happen in a loop that 
> is initializing all the IRQs, not just the IRQ for the serial port.
> Interestingly, I can make the hang go away by specifying 
> "acpi_skip_timer_override" to xen in grub.conf.  AFAICT this is meant for 
> some BIOS issues, but I don't think this system has a problem BIOS, since it 
> cleanly boots Xen 3.4.1 & CentOS 5.3 dom0 without acpi_skip_timer_override.  
> Does that sound like maybe some kind of issue in the recent ACPI code?  Would 
> that be in Xen or in the dom0 Linux?  

Well, to be fair, 5.3 is a bit ancient. And since then the ACPI code in
2.6.31 handles much more - it might be that you are hitting something new.

I don't remember, but did you try just booting bare-metal with the
pv-ops kernel? No Xen, just pv-ops by itself. Did it boot but without
the serial console?

Also can you try booting the kernel with Xen, with 'initcall_debug' for
your kernel command line? That "Xen: Cannot share IRQ0 with guest" is troubling
me and I want to have an idea what part of the kernel code triggers

Xen-devel mailing list