From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Luke S Crawford <lsc@prgmr.com>
Cc: Christoph Egger <Christoph.Egger@amd.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: (XEN) Xen BUG at amd_nonfatal.c:165 on a new amd g34 board
Date: Fri, 7 May 2010 22:45:28 +0100 [thread overview]
Message-ID: <C80A4888.13B50%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <m3r5ln8lka.fsf@luke.xen.prgmr.com>
On 07/05/2010 22:10, "Luke S Crawford" <lsc@prgmr.com> wrote:
> Keir Fraser <keir.fraser@eu.citrix.com> writes:
>
>> Try 'no-mce' on xen-4.0 or xen-unstable command line, or 'nomce' on xen-3.4
>> command line. Looks like MCE support playing up. You probably didn't want
>> the MCE goop enabled anyway. :-)
>
> nomce no-mce and mce=off all appear to do nothing (I'm putting them
> right after kernel xen.gz) I get the same error.
Ah, looks like half the MCE stuff is not even hooked up the mce boot
parameter. Well, I expect Christoph Egger can help: he implemented a lot of
the MCE mechanism, and especially the AMD parts.
I think the mce boot parameter should, when disabled, cause the MCE feature
bits to be removed from Xen's copy of CPUID feature flags. That would easily
disable all MCE logic throughout Xen.
-- Keir
next prev parent reply other threads:[~2010-05-07 21:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-07 1:45 (XEN) Xen BUG at amd_nonfatal.c:165 on a new amd g34 board Luke S Crawford
2010-05-07 7:14 ` Keir Fraser
2010-05-07 21:10 ` Luke S Crawford
2010-05-07 21:45 ` Keir Fraser [this message]
2010-05-12 8:10 ` Keir Fraser
2010-05-20 9:13 ` Luke S Crawford
2010-05-20 12:54 ` Keir Fraser
2010-05-20 14:01 ` Christoph Egger
2010-07-15 5:40 ` Luke S Crawford
2010-07-15 7:04 ` Keir Fraser
2010-07-15 8:34 ` Luke S Crawford
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=C80A4888.13B50%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=Christoph.Egger@amd.com \
--cc=lsc@prgmr.com \
--cc=xen-devel@lists.xensource.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).