[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
From: Luke S Crawford <lsc@xxxxxxxxx>
Date: 15 Jul 2010 04:34:28 -0400
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 15 Jul 2010 01:34:58 -0700
List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Keir Fraser <keir.fraser@xxxxxxxxxxxxx> writes:

> The bug is unavoidable with Xen 4.0.0 release. If you use tip of
> xen-4.0-testing.hg, or one of the 4.0.1 release candidates, then the no-mce
> boot parameter will do the right thing.


Compiling xen-4.0-testing.hg and adding no-mce works great.  thanks.

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

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

Prev by Date: RE: [Xen-devel] granting access to MSI-X table and pending bit array
Next by Date: [Xen-users] how to complie 2.6.34 dom0 kernel to bzImage (Nothing to be done for `bzImage)
Previous by thread: Re: [Xen-devel] (XEN) Xen BUG at amd_nonfatal.c:165 on a new amd g34 board
Next by thread: [Xen-devel] cs:21768 causes guest spend more time on boot up
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.