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

["Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx>]

Andres, a question to your 
http://lists.xensource.com/archives/html/xen-devel/2010-09/msg00556.html mail, 
does your system has interrupt remapping enabled?

Thanks
--jyh

>-----Original Message-----
>From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
>[mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Andreas Kinzler
>Sent: Monday, September 27, 2010 10:51 PM
>To: Bruce Edge
>Cc: xen-devel@xxxxxxxxxxxxxxxxxxx; xen-users@xxxxxxxxxxxxxxxxxxx
>Subject: Re: [Xen-devel] Re: [Xen-users] dom0 hangs in xen 4.0.1-rc3-pre
>
>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
>Xen-devel@xxxxxxxxxxxxxxxxxxx
>http://lists.xensource.com/xen-devel

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