Re: [Xen-devel] (XEN) Xen BUG at amd_nonfatal.c:165 on a new amd

Keir Fraser <keir.fraser@xxxxxxxxxxxxx> writes:
> > 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.
> 
> 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.  

Thanks.  

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread]

Current Thread

[Next in Thread>

Previous by Date:

Re: [Xen-devel] XCP: python SR plugin questions, YAMAMOTO Takashi

Next by Date:

[Xen-devel] [PATCH] p2m: move phystable into p2m, Christoph Egger

Previous by Thread:

Re: [Xen-devel] (XEN) Xen BUG at amd_nonfatal.c:165 on a new amd g34 board, Keir Fraser

Next by Thread:

Re: [Xen-devel] (XEN) Xen BUG at amd_nonfatal.c:165 on a new amd g34 board, Keir Fraser

Indexes:

[Date] [Thread] [Top] [All Lists]