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


AW: Re: [Xen-devel] ACPI problem, was Xen BUG in mm / Xen 4.0.1 with 2.

To: JBeulich <JBeulich@xxxxxxxxxx>, jeremy <jeremy@xxxxxxxx>
Subject: AW: Re: [Xen-devel] ACPI problem, was Xen BUG in mm / Xen 4.0.1 with pvops Kernel?
From: "Carsten Schiers" <carsten@xxxxxxxxxx>
Date: Tue, 14 Sep 2010 23:19:32 +0200
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 14 Sep 2010 14:20:48 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4C8F5D890200007800015F6E@xxxxxxxxxxxxxxxxxx>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
> But in any case - the root cause is broken firmware.

Getting deeper into it. The faulty entries seems not to be the CPUxCST, 
for CPU2 and up. For a reason I don't know, native booting the kernel 
doesn't run
into this issue. I have managed to get a veeeeery detailed ACPI debug 
output now
from the Xen/Dom0 kernel, will try to do the same with native booted 
Kernel tomorrow.

I know already that the natively booting kernel will also run through 4 
CPUs, even
though my CPU has only 2 cores. So it must be something different. There 
is special
code in the acpi driver section for xen in the pvops kernel...

Jeremy, did you do it? Who could possibly help? I am not a real 

Did not attached the log, in case anybody is interested...it's 31MB.


Xen-devel mailing list

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