From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andreas Kinzler Subject: Re: Re: [Xen-users] dom0 hangs in xen 4.0.1-rc3-pre Date: Mon, 27 Sep 2010 16:50:51 +0200 Message-ID: <4CA0AF4B.7040308@hfp.de> References: <4C9DE72E.1000006@hfp.de> <4CA0A8AF.6010908@hfp.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed 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: Bruce Edge Cc: xen-devel@lists.xensource.com, xen-users@lists.xensource.com List-Id: xen-devel@lists.xenproject.org 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