On Thu, Feb 26, 2009 at 12:43 PM, Jesper Krogh <jesper@xxxxxxxx> wrote:Linus Torvalds wrote:On Thu, 26 Feb 2009, Jesper Krogh wrote:Non-working:2.6.26.8 doesnt have this problem.What does the frequency calibrate to? It should be in the dmesg. Does it
The "current_clocsource" is the same on both systems.
$ cat /sys/devices/system/clocksource/clocksource0/current_clocksource
tsc
differ by a big amount?
$ dmesg | grep -i freq
[ 0.004007] Calibrating delay loop (skipped), value calculated using
timer frequency.. 4620.05 BogoMIPS (lpj=9240104)
2.6.26.8 doesn't have that information.
I'm surprised the clocksource watchdog isn't catching it.
What's the output from:
cat /sys/devices/system/clocksource/clocksource0/available_clocksource
Also mind sending the full dmesg for both kernels?