mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: john stultz <johnstul@us.ibm.com>
To: Miklos Vajna <vmiklos@frugalware.org>
Cc: linux-kernel@vger.kernel.org,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"Ingo Molnar" <mingo@redhat.com>,
	"H. Peter Anvin" <hpa@zytor.com>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	"Gabriel C" <nix.or.die@googlemail.com>,
	"CSÉCSY László" <boobaa@frugalware.org>
Subject: Re: System clock runs too fast after 2.6.27 -> 2.6.28.1 upgrade
Date: Wed, 21 Jan 2009 12:00:57 -0800	[thread overview]
Message-ID: <1f1b08da0901211200l88fa89s78a51c4e90878d85@mail.gmail.com> (raw)
In-Reply-To: <20090121171423.GI21473@genesis.frugalware.org>

On Wed, Jan 21, 2009 at 9:14 AM, Miklos Vajna <vmiklos@frugalware.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?

  reply	other threads:[~2009-01-21 20:01 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-21 17:14 Miklos Vajna
2009-01-21 20:00 ` john stultz [this message]
2009-01-21 21:07   ` Miklos Vajna
2009-01-21 21:34     ` john stultz
2009-01-22 19:51       ` Miklos Vajna
2009-01-22 19:55         ` Ingo Molnar
2009-01-23  0:12           ` Miklos Vajna
2009-01-22 20:03         ` john stultz
2009-01-22 23:57           ` Miklos Vajna
2009-01-23  1:43             ` john stultz
2009-01-23 11:04               ` Ingo Molnar
2009-01-24  1:36                 ` john stultz
2009-01-24  9:14                   ` Ingo Molnar
2009-01-25 11:18                     ` Florian Fainelli
2009-01-25 15:03                       ` Ingo Molnar
2009-01-25 15:38                         ` Florian Fainelli
2009-01-25 16:00                           ` Ingo Molnar
2009-01-25 11:17                   ` Florian Fainelli
2009-01-25 15:02                     ` Ingo Molnar
2009-01-25 14:59                   ` Robert Schwebel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1f1b08da0901211200l88fa89s78a51c4e90878d85@mail.gmail.com \
    --to=johnstul@us.ibm.com \
    --cc=boobaa@frugalware.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=nix.or.die@googlemail.com \
    --cc=rjw@sisk.pl \
    --cc=tglx@linutronix.de \
    --cc=vmiklos@frugalware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®