public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Howard Chu <hyc@symas.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Serious time drift - clock running fast
Date: Sat, 24 Sep 2005 09:03:58 -0700	[thread overview]
Message-ID: <433578EE.6070402@symas.com> (raw)
In-Reply-To: <9a8748490509240752436ef7b2@mail.gmail.com>

I'm having the same problem with 2.6.13, AMD64 X2, Asus A8V Deluxe 
motherboard. What's worse is that this is my local net's NTP server, so 
it's taking all my other machines' clocks along for the ride, and I'm 
losing my associations to the upper strata servers because the skew gets 
too great. (So ntpd needs to be restarted periodically.)

I've seen earlier reports on this list about the clock running twice 
normal speed. That's not what I'm seeing here; after several hours it's 
only ahead by 5 minutes at the moment. (The system has been up 20 days, 
but I restarted ntpd a few hours ago, and it resync'd via ntpdate at 
that point.) Maybe it would be running at 2X if I kill ntpd, I haven't 
checked that.

If it matters, I configured a 250Hz clock tick on this kernel.

-- 
  -- Howard Chu
  Chief Architect, Symas Corp.  http://www.symas.com
  Director, Highland Sun        http://highlandsun.com/hyc
  OpenLDAP Core Team            http://www.openldap.org/project/


  reply	other threads:[~2005-09-24 16:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-24  2:18 [PATCH] Unify sys_tkill() and sys_tgkill() Vadim Lobanov
2005-09-24 14:52 ` Jesper Juhl
2005-09-24 16:03   ` Howard Chu [this message]
2005-09-24 16:38   ` Jörn Engel
2005-09-24 19:15     ` Jesper Juhl
2005-09-24 17:47   ` Vadim Lobanov
  -- strict thread matches above, loose matches on Subject: below --
2005-09-18 13:11 Serious time drift - clock running fast Marc Perkel

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=433578EE.6070402@symas.com \
    --to=hyc@symas.com \
    --cc=linux-kernel@vger.kernel.org \
    /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