From: Luke S Crawford <lsc@prgmr.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: "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: 15 Jul 2010 01:40:27 -0400 [thread overview]
Message-ID: <m3sk3ll2us.fsf@luke.xen.prgmr.com> (raw)
In-Reply-To: <C8102100.1408D%keir.fraser@eu.citrix.com>
Keir Fraser <keir.fraser@eu.citrix.com> writes:
> > 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.
>
> Actually I think the attached patch should work, in conjunction with
> specifying no-mce (4.0/unstable) or nomce (3.4) as a Xen boot parameter. Let
> me know if it works okay for you.
>
> I've applied the patch to xen-unstable as c/s 21360.
This still works swimmingly on xen 3.4... but I'm starting to
flirt with xen 4.0/pvops and while it looks like your patch is in there,
nomce, no-mce, mce=off and mce=no all appear to do nothing, and my box
reboots in the same place it did before:
(XEN) Panic on CPU 0:
(XEN) Xen BUG at amd_nonfatal.c:162
next prev parent reply other threads:[~2010-07-15 5:40 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
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 [this message]
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=m3sk3ll2us.fsf@luke.xen.prgmr.com \
--to=lsc@prgmr.com \
--cc=keir.fraser@eu.citrix.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).