All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Kinzler <ml-xen-devel@hfp.de>
To: xen-devel@lists.xensource.com
Subject: Possible hint for "Clocksource tsc unstable" problem
Date: Tue, 18 Oct 2011 17:00:48 +0200	[thread overview]
Message-ID: <4E9D94A0.10102@hfp.de> (raw)

Hello,

I made an interesting observation related to the "Clocksource tsc 
unstable (delta = -2999660320319 ns)" problem. In the log of ntpd I found:

Oct  5 03:46:35 greenville-dom0 ntpd[4020]: kernel time sync status 
change 6001
Oct  5 04:03:41 greenville-dom0 ntpd[4020]: kernel time sync status 
change 2001
Oct  5 05:29:03 greenville-dom0 ntpd[4020]: kernel time sync status 
change 6001
Oct  5 05:46:09 greenville-dom0 ntpd[4020]: kernel time sync status 
change 2001
Oct  5 06:54:30 greenville-dom0 ntpd[4020]: synchronized to 
192.53.103.104, stratum 1
Oct  5 06:54:30 greenville-dom0 ntpd[4020]: kernel time sync status 
change 6001
Oct  5 07:28:22 greenville-dom0 ntpd[4020]: kernel time sync status 
change 2001
Oct  5 08:19:35 greenville-dom0 ntpd[4020]: synchronized to 
192.53.103.108, stratum 1
Oct  5 10:53:26 greenville-dom0 ntpd[4020]: kernel time sync status 
change 6001
Oct  5 11:27:32 greenville-dom0 ntpd[4020]: kernel time sync status 
change 2001
Oct  5 12:01:41 greenville-dom0 ntpd[4020]: kernel time sync status 
change 6001
Oct  5 12:18:44 greenville-dom0 ntpd[4020]: kernel time sync status 
change 2001
Oct  5 13:09:58 greenville-dom0 ntpd[4020]: kernel time sync status 
change 6001
Oct  5 13:27:04 greenville-dom0 ntpd[4020]: kernel time sync status 
change 2001
Oct  5 15:26:37 greenville-dom0 ntpd[4020]: kernel time sync status 
change 6001
Oct  5 15:43:41 greenville-dom0 ntpd[4020]: kernel time sync status 
change 2001
Oct  5 17:43:11 greenville-dom0 ntpd[4020]: kernel time sync status 
change 6001
Oct  5 19:08:31 greenville-dom0 ntpd[4020]: synchronized to 
192.53.103.104, stratum 1
Oct  5 19:08:31 greenville-dom0 ntpd[4020]: kernel time sync status 
change 2001
Oct  5 21:23:58 greenville-dom0 ntpd[4020]: no servers reachable
Oct  5 21:40:58 greenville-dom0 ntpd[4020]: synchronized to 
192.53.103.104, stratum 1
Oct  5 21:40:58 greenville-dom0 ntpd[4020]: time correction of -3000 
seconds exceeds sanity limit (1000); set clock manually to the correct 
UTC time.

I had the problem twice on different machines but everytime I saw the 
line "no servers reachable". Could ntpd and/or linux kernel make some 
stupid stuff when ntp upstream servers are unreachable?

Regards Andreas

             reply	other threads:[~2011-10-18 15:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-18 15:00 Andreas Kinzler [this message]
2011-10-18 17:41 ` Possible hint for "Clocksource tsc unstable" problem Dan Magenheimer
     [not found] ` <FF93AF260AC2BB499A119CC65B092CF7311817E2@sg000713.corproot.net>
     [not found]   ` <F1CD4AC5B4A5024AAB60E28A82A8450A046CE5EE@winexch1.office.turtle-entertainment.de>
     [not found]     ` <CABx4GKqodU4FLmX3adiCi3U-eKe5cDMVtNV2ZhzFAMsKL_1uTg@mail.gmail.com>
     [not found]       ` <FF93AF260AC2BB499A119CC65B092CF7311EE626@sg000713.corproot.net>
     [not found]         ` <CABx4GKo7CBCW6cn49Kr2O+NTm78ms7Xnh_ub1EZ7pdt+Cmp=Lg@mail.gmail.com>
2011-12-02 19:53           ` Andreas Kinzler
2011-12-07  7:13             ` Philippe.Simonet

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=4E9D94A0.10102@hfp.de \
    --to=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 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.