From: Andreas Haumer <andreas@xss.co.at>
To: john stultz <johnstul@us.ibm.com>
Cc: Andy Pfiffer <andyp@osdl.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.72: wall-clock time advancing too rapidly?
Date: Fri, 20 Jun 2003 17:02:59 +0200 [thread overview]
Message-ID: <3EF32223.6000207@xss.co.at> (raw)
In-Reply-To: <1056058206.18644.532.camel@w-jstultz2.beaverton.ibm.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi!
john stultz wrote:
> On Thu, 2003-06-19 at 09:10, Andy Pfiffer wrote:
>
>>I have a uniproc P3-800 system running 2.5.72, and time (from that
>>system's point of view) is racing ahead rapidly.
>>
>>By "racing ahead rapidly", I mean this:
>>
>> % date ; sleep 60 ; date
>> Thu Jun 19 09:04:29 PDT 2003
>> Thu Jun 19 09:05:29 PDT 2003
>> %
>>
>>returns in 35 seconds (measured with my eyeballs and cheap wristwatch).
>>
>>Has anyone else seen this?
>
>
> Well, variants on a theme. Can I get more hardware info? Is this a
> laptop? Are we running w/ Speed Step?
>
I had this symptom recently on an Asus PR-DLS533 mainboard
(ServerWorks GCLE chipset) with linux-2.4.21 and found out
it happens only if I had BIOS "USB legacy support" enabled.
As soon as I disabled this BIOS option, the phenomenon
disappeard.
For more info look for lkml thread with subject "system clock
speed too high?", Message-ID <3EDBA83B.5050406@xss.co.at>
HTH
- - andreas
- --
Andreas Haumer | mailto:andreas@xss.co.at
*x Software + Systeme | http://www.xss.co.at/
Karmarschgasse 51/2/20 | Tel: +43-1-6060114-0
A-1100 Vienna, Austria | Fax: +43-1-6060114-71
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQE+8yIhxJmyeGcXPhERAoyRAKDD+bmvWsdoHXtsAUnmQpOivdYlRwCfZZox
gofL6W64SQ+Hy8xQMehLeS8=
=GEhC
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2003-06-20 14:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-19 16:10 2.5.72: wall-clock time advancing too rapidly? Andy Pfiffer
2003-06-19 21:30 ` john stultz
2003-06-20 14:01 ` Wiktor Wodecki
2003-06-20 18:09 ` john stultz
2003-06-20 15:02 ` Andreas Haumer [this message]
2003-06-20 23:28 ` Andy Pfiffer
2003-06-20 23:31 ` john stultz
2003-06-21 0:07 ` john stultz
2003-06-24 0:16 ` 2.5.7[23]: " Andy Pfiffer
2003-06-24 0:37 ` john stultz
2003-06-24 16:09 ` Andy Pfiffer
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=3EF32223.6000207@xss.co.at \
--to=andreas@xss.co.at \
--cc=andyp@osdl.org \
--cc=johnstul@us.ibm.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