From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: xen-devel@lists.xensource.com,
Philippe Simonet <philippe.simonet@bluewin.ch>
Subject: Re: Xen 4 TSC problems
Date: Thu, 15 Sep 2011 09:24:43 -0700 [thread overview]
Message-ID: <4E7226CB.2020706@goop.org> (raw)
In-Reply-To: <20110915082402.GC24888@phenom.oracle.com>
On 09/15/2011 01:24 AM, Konrad Rzeszutek Wilk wrote:
> On Tue, Sep 13, 2011 at 09:16:27AM +0200, Philippe Simonet wrote:
>> Hi Xen developers
> Lets try this again, this time Cc-ing Jeremy.
>> i just would like to inform you that I have exactly the same problem
>> with Debian squeeze and xen, with
>> 50 seconds time jump on my dom0 and domu. NTP is running on all
>> dom0/domuU, clocksource is 'xen'
>> everywhere.
>>
>> some messages :
>> syslog :
>> Sep 11 13:56:50 dnsit22 kernel: [571603.359863] Clocksource tsc
>> unstable (delta = -2999662111513 ns)
>>
>> xm dmesg :
>> ...
>> (XEN) Platform timer is 14.318MHz HPET
>> ...
>> (XEN) Platform timer appears to have unexpectedly wrapped 10 or more times.
>> (XEN) TSC marked as reliable, warp = 0 (count=2)
>> ...
>>
>> I had some contact with Olivier Hanesse and it indicates that he
>> doesn't have any solution for this problem,
>> and all what was proposed in February didn't solved this problem.
That looks like Xen itself is having problems keeping track of time. If
it can't manage it, then there's not much the guest kernels can do about it.
>
> Which was the max_cstate=0 ?
> ..
>> config :
>> --------------------------------------
>> Linux dnsit22.swissptt.ch 2.6.32-5-xen-amd64 #1 SMP Tue Jun 14
>> 12:46:30 UTC 2011 x86_64 GNU/Linux
>> --------------------------------------
>> HP DL385
>> --------------------------------------
>> vendor_id : AuthenticAMD
>> cpu family : 16
>> model : 9
>> model name : AMD Opteron(tm) Processor 6174
>> stepping : 1
>> cpu MHz : 3058776.574
> OK, that is really messed up. Your house must be on fire for the machine
> to be running at 3058GHz!
>
> Jeremy, this sounds familiar - did we have a patch for this in
> your 2.6.32 tree?
Not that I can think of. All I can suggest from the kernel side is that
perhaps some of the ACPI power stuff isn't being set up properly, and
that makes the CPU do very strange things with its TSC/power states in
general.
J
next prev parent reply other threads:[~2011-09-15 16:24 UTC|newest]
Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-23 10:49 Xen 4 TSC problems Olivier Hanesse
2011-02-23 16:16 ` [Xen-devel] " Dan Magenheimer
2011-02-23 17:19 ` Keir Fraser
2011-02-23 19:04 ` Olivier Hanesse
2011-02-24 7:16 ` Keir Fraser
2011-02-24 9:59 ` Olivier Hanesse
2011-02-24 10:59 ` Jan Beulich
2011-02-24 11:30 ` [Xen-devel] " Keir Fraser
2011-02-24 11:57 ` Olivier Hanesse
2011-02-24 12:37 ` Jan Beulich
2011-02-24 14:20 ` Olivier Hanesse
2011-02-24 14:52 ` [Xen-devel] " Keir Fraser
2011-02-24 17:43 ` Dan Magenheimer
2011-02-24 17:58 ` Olivier Hanesse
2011-02-24 19:01 ` [Xen-devel] " Jeremy Fitzhardinge
2011-02-28 14:37 ` Olivier Hanesse
2011-02-28 15:00 ` Keir Fraser
2011-02-28 15:14 ` [Xen-devel] " Dan Magenheimer
2011-02-28 15:23 ` Olivier Hanesse
2011-02-28 15:30 ` Dan Magenheimer
2011-02-28 15:54 ` Olivier Hanesse
2011-04-15 7:51 ` andre.arnold
2011-04-15 16:31 ` Olivier Hanesse
2012-09-27 15:54 ` [Xen-devel] " Mauro
2012-09-27 19:27 ` [Xen-users] " Dan Magenheimer
2012-09-27 21:28 ` Olivier Hanesse
2012-09-27 21:42 ` [Xen-devel] " Mauro
2012-09-29 8:08 ` [Xen-users] " Olivier Hanesse
2012-09-29 9:41 ` [Xen-devel] " Mauro
2012-09-29 12:19 ` Mauro
2012-09-30 15:13 ` [Xen-users] " Pasi Kärkkäinen
2012-09-30 19:23 ` [Xen-devel] " Mauro
2012-09-30 20:19 ` Mauro
2012-10-15 7:39 ` [Xen-users] " Olivier Hanesse
2012-10-15 8:05 ` Philippe.Simonet
2012-10-15 9:39 ` Mauro
2012-10-15 10:32 ` Jan Beulich
2012-10-15 11:24 ` [Xen-devel] " Mauro
2012-10-15 12:49 ` [Xen-users] " Jan Beulich
2012-10-15 14:25 ` Mauro
2012-10-17 16:15 ` Keir Fraser
2012-10-18 7:40 ` Ian Campbell
2012-10-18 7:55 ` Keir Fraser
2012-10-18 8:33 ` Ian Campbell
2012-10-18 8:56 ` [Xen-devel] " Mauro
2012-10-18 9:36 ` [Xen-users] " Ian Campbell
2012-10-18 13:45 ` Philippe.Simonet
2012-10-18 16:43 ` Keir Fraser
2012-10-21 20:52 ` [Xen-devel] " Mauro
2012-10-22 6:54 ` [Xen-users] " Jan Beulich
2012-10-22 9:17 ` [Xen-devel] " Mauro
2012-10-22 9:27 ` [Xen-users] " Jan Beulich
2012-10-22 10:40 ` [Xen-devel] " Mauro
2012-10-22 12:06 ` [Xen-users] " Jan Beulich
2012-10-23 7:19 ` Mauro
[not found] ` <CAE17a0VU3H8UmUWZv1+t98ME8LFgCZAWWBC1nhzM=ecbu6_GaQ@mail.gmail.com>
2012-10-23 7:58 ` Jan Beulich
2012-10-23 8:40 ` Mauro
2012-10-23 8:50 ` Jan Beulich
2012-10-23 11:50 ` Konrad Rzeszutek Wilk
2012-10-23 14:07 ` Mauro
2012-10-23 14:43 ` Jan Beulich
2012-10-23 14:46 ` Mauro
2012-10-23 15:34 ` Mauro
2012-10-23 15:49 ` Jan Beulich
2012-10-01 11:39 ` Zary Matej
2011-02-28 15:39 ` [Xen-devel] " Keir Fraser
2012-09-29 15:13 ` Mauro
2011-09-13 7:16 ` Philippe Simonet
2011-09-15 8:23 ` Konrad Rzeszutek Wilk
2011-09-15 8:24 ` Konrad Rzeszutek Wilk
2011-09-15 16:24 ` Jeremy Fitzhardinge [this message]
2011-09-16 6:03 ` Philippe.Simonet
2011-09-16 22:40 ` Jeremy Fitzhardinge
2011-09-19 5:45 ` Philippe Simonet
2011-09-15 10:36 ` George Dunlap
2011-09-15 18:38 ` Dan Magenheimer
2011-09-19 10:39 ` George Dunlap
2011-09-22 12:07 ` Jan Beulich
2011-09-30 6:33 ` Philippe.Simonet
2011-09-30 9:36 ` tommics
2011-09-30 17:16 ` Dan Magenheimer
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=4E7226CB.2020706@goop.org \
--to=jeremy@goop.org \
--cc=konrad.wilk@oracle.com \
--cc=philippe.simonet@bluewin.ch \
--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 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).