lkml.org 
[lkml]   [2004]   [Nov]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: 2.6.8 Thinkpad T40, clock running too fast
From
Date
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.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 14:07    [W:0.047 / U:0.664 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site