From: John Sigler <linux.kernel@free.fr>
To: linux-kernel@vger.kernel.org,
linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: System clock frequency offset changes drastically across reboots
Date: Fri, 27 Jul 2007 13:56:42 +0200 [thread overview]
Message-ID: <46A9DD7A.80104@free.fr> (raw)
Hello everyone,
I'm using 2.6.20.7-rt8 on a P3.
I've noticed that the frequency offset of my system clock (computed
either by ntpd, or by hand) changes drastically across reboots.
By drastically, I mean +/- 60 ppm every time I reboot.
Apparently this is caused by some imprecision in the frequency
estimation done in calculate_cpu_khz() (arch/i386/kernel/tsc.c)
My brutally crude work-around was to skip the computation altogether and
hard-code the "correct" value for cpu_khz.
http://linux.kernel.free.fr/cpu_khz.adlink
Has this issue been investigated more thoroughly by other users?
Regards.
next reply other threads:[~2007-07-27 11:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-27 11:56 John Sigler [this message]
2007-07-30 7:59 ` System clock frequency offset changes drastically across reboots John Sigler
2007-08-03 7:47 ` John Sigler
-- strict thread matches above, loose matches on Subject: below --
2007-09-03 10:21 John Sigler
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=46A9DD7A.80104@free.fr \
--to=linux.kernel@free.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@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