From: Andreas Kinzler <ml-xen-devel@hfp.de>
To: Philippe.Simonet@swisscom.com
Cc: xen-devel@lists.xensource.com, joy@entuzijast.net
Subject: Re: (XEN) Platform timer appears to have unexpectedly wrapped 10 or more times.
Date: Tue, 10 Apr 2012 14:33:18 +0200 [thread overview]
Message-ID: <4F84288E.1070407@hfp.de> (raw)
In-Reply-To: <FF93AF260AC2BB499A119CC65B092CF73123E467@sg000713.corproot.net>
I have the same problem. Do you use ntpd? Which version? I suspect some
link between the problem and ntpd.
Andreas
On 05.01.2012 10:39, Philippe.Simonet@swisscom.com wrote:
> Hi
>
> I have the same problem with 4 machines (hp dl385, AMD), the problem appears one time per machine and per month ...
> No chance to re-produce it faster. On some other machine with another AMD processor, I never had this problem. Olivier Hanesse
> reported the problem on some Intel CPU and not on other processor.
>
> I'm using debian squeeze, with
>
> xen-hypervisor-4.0-amd64 4.0.1-4
> linux-image-2.6.32-5-xen-amd64 2.6.32-38 (dom0)
>
> that last changes that I have done is to add cpuidle=0 to hypervisor command line. stable since 3-4 weeks (...)
>
> I have e test system that runs 20 paravirt. domus, with wheezy, with same problematic HW, with
> xen-hypervisor-4.1-amd64 4.1.2-2
> linux-image-3.1.0-1-amd64 3.1.6-1 (dom0)
> and this system never had the TSC jump problem. but test system are test system ....
>
> I would be happy if you could reproduce the problem faster a me, so testing new xen / dom0 version could be
> easier ...
>
> thanks and regards
>
> Philippe
>
>
>
>
>> -----Original Message-----
>> From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-
>> bounces@lists.xensource.com] On Behalf Of Josip Rodin
>> Sent: Wednesday, January 04, 2012 6:24 PM
>> To: xen-devel@lists.xensource.com
>> Subject: [Xen-devel] (XEN) Platform timer appears to have unexpectedly
>> wrapped 10 or more times.
>>
>> Hi,
>>
>> Sometimes, seemingly randomly, long-running Xen domains, using
>> clocksource xen, have their clock shift by ~3000 or ~36000 seconds, often
>> with the dom0 complaining about clocksource tsc. The number changes if the
>> hypervisor is explicitly told to use clocksource=pit, but it still happens. It
>> doesn't seem to be particularly hardware-specific.
>>
>> See also http://bugs.debian.org/599161
>>
>> I see from the archives that others have reported this problem here in
>> February last year, but I couldn't find a resolution. Can anyone help?
>>
>> (Please Cc: responses, I'm not subscribed.)
>>
>> --
>> 2. That which causes joy or happiness.
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2012-04-10 12:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-04 17:23 (XEN) Platform timer appears to have unexpectedly wrapped 10 or more times Josip Rodin
2012-01-05 9:39 ` Philippe.Simonet
2012-04-10 12:33 ` Andreas Kinzler [this message]
2012-04-10 13:05 ` Josip Rodin
2012-04-10 13:59 ` Andreas Kinzler
2012-04-10 14:07 ` Josip Rodin
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=4F84288E.1070407@hfp.de \
--to=ml-xen-devel@hfp.de \
--cc=Philippe.Simonet@swisscom.com \
--cc=joy@entuzijast.net \
--cc=xen-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.