On Tue, 11 Sep 2007 21:35:15 +0200
"Rafael J. Wysocki" <rjw@sisk.pl> wrote:

quoted text
> > dmesg without the cpuidle patch: http://userweb.kernel.org/~akpm/dmesg-bad.txt
> > dmesg with the cpuidle patch: http://userweb.kernel.org/~akpm/dmesg-good.txt
> > difference: http://userweb.kernel.org/~akpm/dmesg-diff.txt
> > 
> > there doesn't seem to be a lot of difference in the time handling, except
> > there are large changes in when things happen in the bootup sequence.
> 
> Hm, these things look like they may be related to the suspend/resume problems:
> 
> +Marking TSC unstable due to: possible TSC halt in C2.
> 
> +Clocksource tsc unstable (delta = -458965792 ns)

sort-of.  But look:

akpm:/home/akpm> grep -i tsc dmesg-diff.txt 
+Marking TSC unstable due to: possible TSC halt in C2.
+Clocksource tsc unstable (delta = -458965792 ns)
-Marking TSC unstable due to: cpufreq changes.
-Clocksource tsc unstable (delta = -150503296 ns)

the good and bad kernels seem to be doing quite similar things with the
time management.  But they're doing it at quite different places in the
boot process.

-
unsubscribe notice
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/