xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Bruce Edge <bruce.edge@gmail.com>
To: Andreas Kinzler <ml-xen-users@hfp.de>
Cc: xen-devel@lists.xensource.com, xen-users@lists.xensource.com
Subject: Re: [Xen-users] dom0 hangs in xen 4.0.1-rc3-pre
Date: Mon, 27 Sep 2010 07:32:30 -0700	[thread overview]
Message-ID: <AANLkTi=zOvevpMMX1oQCfWQomzvSnrv+qhapx-TNtk3H@mail.gmail.com> (raw)
In-Reply-To: <4CA0A8AF.6010908@hfp.de>


[-- Attachment #1.1: Type: text/plain, Size: 1427 bytes --]

On Mon, Sep 27, 2010 at 7:22 AM, Andreas Kinzler <ml-xen-users@hfp.de>wrote:

> On 27.09.2010 16:06, Bruce Edge wrote:
>
>> I saw reproducible hangs in dom0 when the system is under heavy load.
>>>> four dom0s share a nfs server for domU images. a total number of 24
>>>> domUs
>>>> (6
>>>> domUs on each dom0). When the system under heavy load, busy processing
>>>> e-commerce requests, one or two of the dom0s hanged. no input can be
>>>> accepted and reboot is necessary.
>>>> Anyone had the same experience? The causes I can come up are following:
>>>>
>>> Please post your hardware (mainboard, chipset, CPU, RAID controller).
>>> I have found a severe problem on Lynnfield systems.
>>>
>> 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.
>
> Regards Andreas
>

Andreas,
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.

-Bruce

[-- Attachment #1.2: Type: text/html, Size: 2137 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

  reply	other threads:[~2010-09-27 14:32 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-24  4:22 dom0 hangs in xen 4.0.1-rc3-pre Jia Rao
2010-09-24 10:27 ` [Xen-devel] " Pasi Kärkkäinen
2010-09-24 19:08 ` Jeremy Fitzhardinge
2010-09-24 20:48   ` Jia Rao
2010-09-24 21:01     ` Jia Rao
2010-09-25 12:12 ` Andreas Kinzler
2010-09-26  1:12   ` [Xen-users] " Jia Rao
2010-09-27 14:06   ` Bruce Edge
2010-09-27 14:22     ` [Xen-users] " Andreas Kinzler
2010-09-27 14:32       ` Bruce Edge [this message]
2010-09-27 14:50         ` Andreas Kinzler
2010-09-28  1:57           ` [Xen-devel] " Jiang, Yunhong
2010-09-28  8:25             ` Andreas Kinzler
2010-09-28 16:04           ` Bruce Edge
2010-09-29 17:46             ` Andreas Kinzler
2010-09-29 18:01               ` Re: [Xen-users] " Bruce Edge

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='AANLkTi=zOvevpMMX1oQCfWQomzvSnrv+qhapx-TNtk3H@mail.gmail.com' \
    --to=bruce.edge@gmail.com \
    --cc=ml-xen-users@hfp.de \
    --cc=xen-devel@lists.xensource.com \
    --cc=xen-users@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).