[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090121210726.GK21473@genesis.frugalware.org>
Date: Wed, 21 Jan 2009 22:07:26 +0100
From: Miklos Vajna <vmiklos@...galware.org>
To: john stultz <johnstul@...ibm.com>
Cc: linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>,
"Rafael J. Wysocki" <rjw@...k.pl>,
Gabriel C <nix.or.die@...glemail.com>,
CSÉCSY László <boobaa@...galware.org>
Subject: Re: System clock runs too fast after 2.6.27 -> 2.6.28.1 upgrade
On Wed, Jan 21, 2009 at 12:00:57PM -0800, john stultz <johnstul@...ibm.com> wrote:
> Could you send the output from:
> cat /sys/devices/system/clocksource/clocksource0/current_clocksource
> cat /sys/devices/system/clocksource/clocksource0/available_clocksource
>
> For both kernels on the affected hardware ?
Output when no related kernel parameters are used:
2.6.28.1:
$ cat /sys/devices/system/clocksource/clocksource0/current_clocksource
tsc
$ cat /sys/devices/system/clocksource/clocksource0/available_clocksource
tsc pit jiffies
2.6.27.10:
$ cat /sys/devices/system/clocksource/clocksource0/current_clocksource
acpi_pm
$ cat /sys/devices/system/clocksource/clocksource0/available_clocksource
acpi_pm jiffies tsc
So it seems the problem is that acpi_pm is no longer available.
> Also could you attach the dmesg for 2.6.27 on the same hardware?
dmesg-2.6.27 and config-2.6.27 attached.
View attachment "dmesg-2.6.27" of type "text/plain" (26250 bytes)
View attachment "config-2.6.27" of type "text/plain" (89979 bytes)
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists