From: Patrick Moor <pmoor@netpeople.ch>
To: linux-kernel@vger.kernel.org
Subject: time jumps (again)
Date: Mon, 04 Aug 2003 18:35:07 +0200 [thread overview]
Message-ID: <3F2E8B3B.3070003@netpeople.ch> (raw)
Hi
Some days ago I started noticing strange time jumps on my Athlon system.
(Asus board, VIA chipset, AMD Athlon 650MHz processor). I haven't
noticed them before and I am pretty sure there weren't any for the last
few years! Uptime of the machine is now 218 days, and problems began
appearing after 215 days approximately.
What happens: when doing a
$ while true; do date; done
I'm noticing time jumps _exactly_ at the beginning of a "new" second (or
at the end of an "old" one). the jump is exactly 4294 (4295) seconds
into the future. Example:
...
Mon Aug 4 18:11:06 CEST 2003
Mon Aug 4 18:11:06 CEST 2003
Mon Aug 4 19:22:41 CEST 2003
Mon Aug 4 19:22:41 CEST 2003
Mon Aug 4 19:22:41 CEST 2003
Mon Aug 4 18:11:07 CEST 2003
Mon Aug 4 18:11:07 CEST 2003
...
I've found some previous discussions about this about a year ago:
http://www.ussg.iu.edu/hypermail/linux/kernel/0203.3/0557.html
http://www.ussg.iu.edu/hypermail/linux/kernel/0206.0/1505.html
What seems strange to me is, that these jumps have never occured before.
The machine is running a plain 2.4.20 kernel.
So my question is: will disabling the CONFIG_X86_TSC option and passing
"notsc" as boot parameter fix the problem? Or did I get something wrong
there?
thanks
patrick
next reply other threads:[~2003-08-04 16:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-04 16:35 Patrick Moor [this message]
2003-08-04 16:37 ` time jumps (again) Alan Cox
2003-08-04 21:49 ` Tim Schmielau
2003-08-04 22:38 ` george anzinger
2003-08-05 1:08 ` Andries Brouwer
2003-08-06 18:16 ` Timothy Miller
2003-08-06 18:55 ` George Anzinger
2003-08-07 0:29 ` Andries Brouwer
2003-08-05 10:32 ` Jan Niehusmann
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=3F2E8B3B.3070003@netpeople.ch \
--to=pmoor@netpeople.ch \
--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;
as well as URLs for NNTP newsgroup(s).