From: Sid Boyce <sboyce@blueyonder.co.uk>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.10-rc3 vs clock
Date: Sat, 18 Dec 2004 00:06:05 +0000 [thread overview]
Message-ID: <41C3746D.8090308@blueyonder.co.uk> (raw)
Bill Davidsen wrote:
Gene Heskett wrote:
>> At -rc2 my clock kept fairly decent time, but -rc3 is running
fast, about 30 seconds an hour fast.
>>
>> I've been using ntpdate, is that now officially deprecated?
> Running ntpd used to keep the clock dead on, now my 2.6 systems all
drift one way or the other. I suspect that the system calls used by ntpd
> have changed somehow, but until I find the time to look harder I
can't > say that except as conjecture.
>
> The sad thing is that most of the systems have quite good hardware
clocks...
Gene Heskett suggested I play around with tickadj and I found that a
value of 9962 on this SuSE 9.2/XP3000+ has kept it rock solid over the
last 4 days. On the x86_64 laptop with XP3000+-Mobile, it's never been
out, both of them running 2.6.10-rc3 and using ntpd to keep in step. On
the other box with Mandrake 10.1/XP2800+ and 2.6.10-rc3, I had to set it
to 9958. Something has definitely changed with 2.6.10-rc3.
Regards
Sid.
--
Sid Boyce .... Hamradio G3VBV and keen Flyer
=====LINUX ONLY USED HERE=====
next reply other threads:[~2004-12-18 0:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-18 0:06 Sid Boyce [this message]
2004-12-18 0:38 ` 2.6.10-rc3 vs clock Gene Heskett
2004-12-18 2:38 ` Sid Boyce
2004-12-18 3:33 ` Gene Heskett
-- strict thread matches above, loose matches on Subject: below --
2004-12-13 23:30 Sid Boyce
2004-12-14 1:59 ` Gene Heskett
2004-12-14 4:15 ` Sid Boyce
2004-12-04 16:11 Gene Heskett
2004-12-06 19:19 ` john stultz
2004-12-13 12:29 ` David Weinehall
2004-12-13 14:04 ` Rafael J. Wysocki
2004-12-13 15:01 ` Gene Heskett
2004-12-16 17:02 ` Bill Davidsen
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=41C3746D.8090308@blueyonder.co.uk \
--to=sboyce@blueyonder.co.uk \
--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