This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] Re: [Xen-users] dom0 hangs in xen 4.0.1-rc3-pre

To: Bruce Edge <bruce.edge@xxxxxxxxx>
Subject: Re: [Xen-devel] Re: [Xen-users] dom0 hangs in xen 4.0.1-rc3-pre
From: Andreas Kinzler <ml-xen-devel@xxxxxx>
Date: Mon, 27 Sep 2010 16:50:51 +0200
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 27 Sep 2010 07:51:41 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AANLkTi=zOvevpMMX1oQCfWQomzvSnrv+qhapx-TNtk3H@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <AANLkTimPVj-AXyR8DuQRxuAwcFwHm0sVkgiXvkA1+f7-@xxxxxxxxxxxxxx> <4C9DE72E.1000006@xxxxxx> <AANLkTi=jxHQp3_GDML9JcoYNNkGTGLR3_okBspWnFdfC@xxxxxxxxxxxxxx> <4CA0A8AF.6010908@xxxxxx> <AANLkTi=zOvevpMMX1oQCfWQomzvSnrv+qhapx-TNtk3H@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv: Gecko/20100915 Thunderbird/3.1.4
On 27.09.2010 16:32, Bruce Edge wrote:
Does this affect all Nehalem chips or only the Lynnfields? The .21 kernel
is  causing grief for us too.  I was wondering if this was related.
I am still researching this. For testing I bought a test system with
Westmere-EP (Xeon E5620) which has ARAT. This system worked stable while
Intel still lists it as having the C6 errata. This leads me to the
conclusion that the HPET timer migration code (called HPET broadcast) from
Xen is the root cause. This affects all CPUs that use it - but mainly
Nehalem because of turbo mode.
Thanks for the info. I'll try disabling turbo mode in the BIOS and see if
that helps.
Let me know if there's anything I can run/do/test/etc.

If you want to check the issue I am referring to then you need to apply my patch from: http://lists.xensource.com/archives/html/xen-devel/2010-09/msg00556.html

Do not modify the BIOS settings in any way.

Regards Andreas

Xen-devel mailing list