Jesper Krogh wrote:
> The "current_clocsource" is the same on both systems.
>
> $ cat /sys/devices/system/clocksource/clocksource0/current_clocksource
> tsc
What selects the "current_clocksource"? I tried to boot one of the
kernels hat have the problem on another piece of hardware and on that
system it ended up defaulting to "acpi_pm" instead of "tsc".
http://krogh.cc/~jesper/dmesg-2.6.28.7.txt
"acpi_pm" seems to be reliable all the time.
--
Jesper
On Sun, Mar 01, 2009 at 04:09:03PM +0100, Jesper Krogh wrote:
> Jesper Krogh wrote:
> >The "current_clocsource" is the same on both systems.
> >
> >$ cat /sys/devices/system/clocksource/clocksource0/current_clocksource
> >tsc
>
> What selects the "current_clocksource"? I tried to boot one of the
> kernels hat have the problem on another piece of hardware and on that
> system it ended up defaulting to "acpi_pm" instead of "tsc".
I believe different clock sources have different priorities based on
their resolution and behaviour. Clock sources's that "go bad" because
hardware interactions are hopefully detected and subsequent "best" clock
sources are then tried.
There was a nice treatment of different clocksourcs in this
kernelnewbies thread:
http://www.mail-archive.com/[email protected]/msg05164.html .
--
Sitsofe | http://sucs.org/~sits/