[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1f1b08da0901211200l88fa89s78a51c4e90878d85@mail.gmail.com>
Date: Wed, 21 Jan 2009 12:00:57 -0800
From: john stultz <johnstul@...ibm.com>
To: Miklos Vajna <vmiklos@...galware.org>
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 9:14 AM, Miklos Vajna <vmiklos@...galware.org> wrote:
> We just recently upgraded from Linux 2.6.27 to 2.6.28.1 and we noticed
> that on some i686 machines the system clocks runs way faster than
> necessary, they count about 70 minutes in an hour.
>
> The strange fact is that using the same config on some other i686
> machines the problem is not reproducible.
>
> We had no messages on boot using the quiet option with 2.6.27, now there
> is a
>
> IO APIC resources could be not be allocated.
>
> with 2.6.28. I'm not sure if this is related or not.
>
> I'm attaching the dmesg of my laptop (where the bug is reproducible),
> the config and the lspci output.
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 ?
Also could you attach the dmesg for 2.6.27 on the same hardware?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists