From: Jan Spitalnik <jan@spitalnik.net>
To: Tim Schmielau <tim@physik3.uni-rostock.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.8.1 slews system clock
Date: Sat, 21 Aug 2004 01:11:53 +0200 [thread overview]
Message-ID: <200408210111.53538.jan@spitalnik.net> (raw)
In-Reply-To: <200408201702.01287.jan@spitalnik.net>
Dne pá 20. srpna 2004 17:02 Jan Spitalnik napsal(a):
> > Which was the last kernel that worked?
>
> 2.6.7 didn't exhibit this problem. I will test 2.6.8-rc's to find which one
> caused this regression.
Hi,
I've did further testing and I've found out that fortunately it's not a kernel
problem (sorry for the buzz :-/ ). adjtimex was the culprit.
adjtimexconfigure said that the CMOS clock is faster by 970secs a day to
system clock. When I disabled adjtimex and rebooted, the system clock is now
rock solid and doesn't slew. Now I wonder what's wrong with adjtimex or my
system. I've tried on several other systems and the it was all the same.
Thanks,
jan
--
Jan Spitalnik
jan@spitalnik.net
prev parent reply other threads:[~2004-08-20 23:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-20 13:27 2.6.8.1 slews system clock Jan Spitalnik
2004-08-20 14:02 ` Tim Schmielau
2004-08-20 15:02 ` Jan Spitalnik
2004-08-20 23:11 ` Jan Spitalnik [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=200408210111.53538.jan@spitalnik.net \
--to=jan@spitalnik.net \
--cc=linux-kernel@vger.kernel.org \
--cc=tim@physik3.uni-rostock.de \
/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