From: Sid Boyce <sboyce@blueyonder.co.uk>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.10-rc3 vs clock
Date: Tue, 14 Dec 2004 04:15:06 +0000 [thread overview]
Message-ID: <41BE68CA.4090506@blueyonder.co.uk> (raw)
In-Reply-To: <200412132059.01101.gene.heskett@verizon.net>
Gene Heskett wrote:
> On Monday 13 December 2004 18:30, Sid Boyce wrote:
>
>>I'm seeing uptime 11:26pm up 1 day 13:30 and my clock is around 190
>>secs fast, I don't know if this happened only at 2.6.10-rc3, but
>>that's when I noticed it on this XP3000+. On the x86_64 laptop also
>>with 2.6.10-rc3, it's bang on time in uptime 5 days 2:11.
>>Regards
>>Sid.
>
>
> I've been playng with the tickadj command, and am currently set
> at 9926, default is 10,000. And I'm keeping pretty good time now.
> Running ntpdate in slew the clock mode, once per hour, I'm
> logging this now:
> Dec 13 12:35:03 coyote ntpdate[26529]: adjust time server
> 140.142.16.34 offset 0.043227 sec
> Dec 13 13:35:01 coyote ntpdate[27572]: adjust time server
> 18.145.0.30 offset 0.248119 sec
> Dec 13 14:35:05 coyote ntpdate[28624]: adjust time server
> 204.123.2.72 offset 0.156707 sec
> Dec 13 15:35:03 coyote ntpdate[29486]: adjust time server
> 198.30.92.2 offset 0.245309 sec
> Dec 13 16:35:04 coyote ntpdate[30400]: adjust time server
> 164.67.62.194 offset 0.105258 sec
> Dec 13 17:35:01 coyote ntpdate[31320]: adjust time server
> 130.207.244.240 offset 0.036849 sec
> Dec 13 18:35:01 coyote ntpdate[32229]: adjust time server
> 18.145.0.30 offset 0.254626 sec
> Dec 13 19:35:10 coyote ntpdate[741]: adjust time server
> 198.30.92.2 offset 0.276145 sec
> Dec 13 20:35:02 coyote ntpdate[1858]: adjust time server
> 128.252.19.1 offset 0.151181 sec
>
> So while its not perfect, its adequate.
>
> As to whats doing it, I have NDI.
>
Thanks, I set it to 9942 and checking with ptktime and it's looking
good, before it was drifting by 3 seconds by this time - with 9926 it
was losing slightly, 2 secs in about 5 minutes. On the laptops and the
Mandrake box that are rock solid it is set at 10,000, the P-II/333
laptop is using the SuSE 9.2 kernel and the others are on 2.6.10-rc3.
Regards
Sid.
--
Sid Boyce .... Hamradio G3VBV and keen Flyer
=====LINUX ONLY USED HERE=====
next prev parent reply other threads:[~2004-12-14 4:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-13 23:30 2.6.10-rc3 vs clock Sid Boyce
2004-12-14 1:59 ` Gene Heskett
2004-12-14 4:15 ` Sid Boyce [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-18 0:06 Sid Boyce
2004-12-18 0:38 ` Gene Heskett
2004-12-18 2:38 ` Sid Boyce
2004-12-18 3:33 ` Gene Heskett
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=41BE68CA.4090506@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