mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: john stultz <johnstul@us.ibm.com>
To: Shawn Willden <shawn-lkml@willden.org>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.8 Thinkpad T40, clock running too fast
Date: Tue, 02 Nov 2004 16:27:11 -0800	[thread overview]
Message-ID: <1099441631.9139.36.camel@cog.beaverton.ibm.com> (raw)
In-Reply-To: <200411021703.43453.shawn-lkml@willden.org>

On Tue, 2004-11-02 at 16:03, Shawn Willden wrote:
> On Tuesday 02 November 2004 04:06 pm, john stultz wrote:
> > Does this go away if you disable cpufreq in your kernel config?
> 
> I'll try that next.

Thanks, do let me know if it helps or not.

> > Also, looking at /proc/interrupts, does it look like you're getting more
> > then ~1000 interrupts per second?
> 
> I don't think so.  I'm not sure how to tell.  Running the following:
> 
> prev=0
> while true; do
>     cur=`cat /proc/interrupts| grep timer|cut -d' ' -f 6`
>     (( diff = $cur - $prev ))
>     echo $diff; prev=$cur
>     sleep 1
> done 
> 
> gives interrupt count differences that are between 1003 and 1222 per (rough) 
> second.  The mean is 1016 with a std deviation of 16.  Running the same thing 
> on another machine -- one without clock problems -- yields similar values.
> 
> Is there a better way to measure this?

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. 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. 

thanks
-john

PS: If you wouldn't mind, CC me next time.


  reply	other threads:[~2004-11-03  0:32 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 [this message]
2004-11-03  0:58       ` Shawn Willden
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=1099441631.9139.36.camel@cog.beaverton.ibm.com \
    --to=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shawn-lkml@willden.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®