xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
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: Thu, 20 May 2010 13:54:14 +0100	[thread overview]
Message-ID: <C81AEF86.14ADD%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <m34oi3ndg1.fsf@luke.xen.prgmr.com>

On 20/05/2010 10:13, "Luke S Crawford" <lsc@prgmr.com> wrote:

>> 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.
> 
> So this patch was applied to 3.4-testing now, and it works beautifully.
> I can repeatably remove nomce from the command line, and i get the error.
> I re-add nomce to the command line, and everything works great.

That'll do then, until stomeone who udnerstands the MCE stuff implements a
proper fix.

 Thanks,
 Keir

  reply	other threads:[~2010-05-20 12:54 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 [this message]
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=C81AEF86.14ADD%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).