[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090121171423.GI21473@genesis.frugalware.org>
Date: Wed, 21 Jan 2009 18:14:23 +0100
From: Miklos Vajna <vmiklos@...galware.org>
To: linux-kernel@...r.kernel.org
Cc: 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: System clock runs too fast after 2.6.27 -> 2.6.28.1 upgrade
Hi,
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.
Before I started to write this mail I tried the followings:
- Booting with 'noapic notsc clocksource=pit'.
- Booting with 'noapic notsc clocksource=jiffies'.
- Booting with 'nohz=off'.
Is this a known problem?
Let me know if I missed any required information I should provide.
Thanks!
View attachment "config" of type "text/plain" (96051 bytes)
View attachment "dmesg" of type "text/plain" (36083 bytes)
View attachment "lspci" of type "text/plain" (1949 bytes)
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists