From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Egger Subject: Re: (XEN) Xen BUG at amd_nonfatal.c:165 on a new amd g34 board Date: Thu, 20 May 2010 16:01:52 +0200 Message-ID: <201005201601.52412.Christoph.Egger@amd.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: Luke S Crawford , "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On Thursday 20 May 2010 14:54:14 Keir Fraser wrote: > On 20/05/2010 10:13, "Luke S Crawford" 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. Keir: Thanks for fixing it. I am currently busy with nested virtualization. -- ---to satisfy European Law for business letters: Advanced Micro Devices GmbH Einsteinring 24, 85609 Dornach b. Muenchen Geschaeftsfuehrer: Andrew Bowd, Thomas M. McCoy, Giuliano Meroni Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen Registergericht Muenchen, HRB Nr. 43632