From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: AW: Re: ACPI problem, was Xen BUG in mm / Xen 4.0.1 with 2.6.32.18/21 pvops Kernel? Date: Tue, 14 Sep 2010 15:05:03 -0700 Message-ID: <4C8FF18F.9010607@goop.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Carsten Schiers Cc: xen-devel , "Yu, Ke" , JBeulich , "Jiang, Yunhong" List-Id: xen-devel@lists.xenproject.org On 09/14/2010 02:19 PM, Carsten Schiers wrote: >> But in any case - the root cause is broken firmware. > Getting deeper into it. The faulty entries seems not to be the CPUxCST, > but CPUxIST > 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 > specialist... > > Did not attached the log, in case anybody is interested...it's 31MB. I'm not really an expert on ACPI at all. I've cc:d some of the Intel folks who've been very helpful in contributing ACPI changes. J