From: Shawn Willden <shawn-lkml@willden.org>
To: linux-kernel@vger.kernel.org
Cc: john stultz <johnstul@us.ibm.com>
Subject: Re: 2.6.8 Thinkpad T40, clock running too fast
Date: Tue, 2 Nov 2004 17:58:12 -0700 [thread overview]
Message-ID: <200411021758.16313.shawn-lkml@willden.org> (raw)
In-Reply-To: <1099441631.9139.36.camel@cog.beaverton.ibm.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tuesday 02 November 2004 05:27 pm, john stultz wrote:
> Not really, the problem is that the sleep call returns after so many
> timer ticks, so even if the wrong amount of time has passed, you'll see
> the same number of interrupts.
Ah, right. Nothing like measuring a ruler with itself.
> It would be best if you checked the time
> on your watch, waited 5 minutes and checked again, or better, did
> something similar w/ ntpdate. I just wanted to eyeball it to make sure
> you weren't running away w/ way too many timer interrupts.
I'll do that
> PS: If you wouldn't mind, CC me next time.
I am. BTW, in case you didn't see my other e-mail, I'm now running with 2.6.9
and cpufreq off. No significant change.
Shawn.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
iD8DBQFBiC0o6d8WxFy/CWcRAv2RAJ9ZhrXkIAoiEpZ9PrFK+jAQLMKyhQCfXkai
YhtDAgHFdjIR+WpV3XdG5Ss=
=kO2+
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-11-03 1:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-02 22:51 Shawn Willden
2004-11-02 23:06 ` john stultz
2004-11-03 0:03 ` Shawn Willden
2004-11-03 0:27 ` john stultz
2004-11-03 0:58 ` Shawn Willden [this message]
2004-11-03 0:38 ` Shawn Willden
2004-11-03 12:29 ` Stefan Seyfried
-- strict thread matches above, loose matches on Subject: below --
2004-11-02 22:18 Shawn Willden
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=200411021758.16313.shawn-lkml@willden.org \
--to=shawn-lkml@willden.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
all inboxes | Powered by JetHome®