From: Josip Rodin <joy@entuzijast.net>
To: Andreas Kinzler <ml-xen-devel@hfp.de>
Cc: Philippe.Simonet@swisscom.com, xen-devel@lists.xensource.com
Subject: Re: (XEN) Platform timer appears to have unexpectedly wrapped 10 or more times.
Date: Tue, 10 Apr 2012 16:07:57 +0200 [thread overview]
Message-ID: <20120410140757.GA24893@entuzijast.net> (raw)
In-Reply-To: <4F843CCE.7010307@hfp.de>
On Tue, Apr 10, 2012 at 03:59:42PM +0200, Andreas Kinzler wrote:
> >On Tue, Apr 10, 2012 at 02:33:18PM +0200, Andreas Kinzler wrote:
> >>I have the same problem. Do you use ntpd? Which version? I suspect
> >>some link between the problem and ntpd.
> >But ntpd is still a userland program, shouldn't the kernel exert the
> >ultimate control over who gets to screw with the system's clock source?
> >In any case, I did a quick grep of ntpd sources and found references to
> >RDTSC only in the Windows port, so the link doesn't seem obvious.
>
> Right, there is no obvious link (but which hard to reproduce bug is
> obvious?) but see
> "http://lists.xen.org/archives/html/xen-devel/2011-10/msg01269.html".
> There seems to be some connection.
>From that (garbled) log, I don't see it - you didn't even post the matching
kernel log message with timestamp, so it's impossible to see if and when
it coincided when the ntpd messages.
Over here we're running ntpd, obviously, in dom0 and in domU, but the only
observed interaction of this problem with ntpd is that they become useless
with this kind of a major drift.
--
2. That which causes joy or happiness.
prev parent reply other threads:[~2012-04-10 14:07 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
2012-04-10 13:05 ` Josip Rodin
2012-04-10 13:59 ` Andreas Kinzler
2012-04-10 14:07 ` Josip Rodin [this message]
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=20120410140757.GA24893@entuzijast.net \
--to=joy@entuzijast.net \
--cc=Philippe.Simonet@swisscom.com \
--cc=ml-xen-devel@hfp.de \
--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).