From: "Yu, Ke" <ke.yu@intel.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>,
Carsten Schiers <carsten@schiers.de>,
"Wang, Winston L" <winston.l.wang@intel.com>
Cc: xen-devel <xen-devel@lists.xensource.com>,
JBeulich <JBeulich@novell.com>,
"Jiang, Yunhong" <yunhong.jiang@intel.com>
Subject: RE: AW: Re: ACPI problem, was Xen BUG in mm / Xen 4.0.1 with 2.6.32.18/21 pvops Kernel?
Date: Wed, 15 Sep 2010 09:20:11 +0800 [thread overview]
Message-ID: <33AB447FBD802F4E932063B962385B352A721A4A@shsmsx501.ccr.corp.intel.com> (raw)
In-Reply-To: <4C8FF18F.9010607@goop.org>
CC Winston, who has is working on the Xen ACPI stuff.
Regards
Ke
> -----Original Message-----
> From: Jeremy Fitzhardinge [mailto:jeremy@goop.org]
> Sent: Wednesday, September 15, 2010 6:05 AM
> To: Carsten Schiers
> Cc: JBeulich; xen-devel; Yu, Ke; Jiang, Yunhong
> Subject: Re: AW: Re: [Xen-devel] ACPI problem, was Xen BUG in mm / Xen
> 4.0.1 with 2.6.32.18/21 pvops Kernel?
>
> 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
next prev parent reply other threads:[~2010-09-15 1:20 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-08 12:15 Xen BUG in mm / Xen 4.0.1 with 2.6.32.18/21 pvops Kernel? Carsten Schiers
2010-09-08 12:51 ` Jan Beulich
2010-09-08 20:15 ` AW: " Carsten Schiers
2010-09-09 9:57 ` Jan Beulich
2010-09-09 18:27 ` Carsten Schiers
2010-09-09 18:40 ` Carsten Schiers
2010-09-09 19:04 ` Carsten Schiers
2010-09-10 8:22 ` Jan Beulich
2010-09-10 8:45 ` Jan Beulich
2010-09-14 9:10 ` Carsten Schiers
2010-09-14 9:33 ` Jan Beulich
2010-09-14 21:19 ` AW: Re: ACPI problem, was " Carsten Schiers
2010-09-14 22:05 ` Jeremy Fitzhardinge
2010-09-15 1:20 ` Yu, Ke [this message]
2010-09-15 2:02 ` Wang, Winston L
2010-09-15 5:37 ` Jiang, Yunhong
2010-09-15 7:22 ` AW: " Carsten Schiers
2010-09-15 7:38 ` Jiang, Yunhong
2010-09-15 8:15 ` AW: " Jan Beulich
2010-09-15 8:28 ` Carsten Schiers
2010-09-15 8:36 ` Jiang, Yunhong
2010-09-15 8:50 ` Jiang, Yunhong
2010-10-19 9:59 ` 2.6.34.7 with SUSE patches: Invalid Kernel Carsten Schiers
2010-10-20 16:54 ` Jeremy Fitzhardinge
2010-09-15 17:01 ` AW: Re: ACPI problem, was Xen BUG in mm / Xen 4.0.1 with 2.6.32.18/21 pvops Kernel? Jeremy Fitzhardinge
2010-09-10 8:48 ` AW: " Jan Beulich
2010-09-08 20:16 ` Carsten Schiers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=33AB447FBD802F4E932063B962385B352A721A4A@shsmsx501.ccr.corp.intel.com \
--to=ke.yu@intel.com \
--cc=JBeulich@novell.com \
--cc=carsten@schiers.de \
--cc=jeremy@goop.org \
--cc=winston.l.wang@intel.com \
--cc=xen-devel@lists.xensource.com \
--cc=yunhong.jiang@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.