From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser 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 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Luke S Crawford Cc: Christoph Egger , "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On 07/05/2010 22:10, "Luke S Crawford" wrote: > Keir Fraser 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