All of lore.kernel.org
 help / color / mirror / Atom feed
From: john stultz <johnstul@us.ibm.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Alessandro Suardi <alessandro.suardi@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: clocksource change of behavior in 2.6.22 compared to 2.6.20 causes massive system clock slowdown
Date: Tue, 10 Jul 2007 10:28:20 -0700	[thread overview]
Message-ID: <1184088500.30575.9.camel@localhost> (raw)
In-Reply-To: <20070710002935.f082b7c3.akpm@linux-foundation.org>

On Tue, 2007-07-10 at 00:29 -0700, Andrew Morton wrote:
> On Mon, 9 Jul 2007 16:27:59 +0200 "Alessandro Suardi" <alessandro.suardi@gmail.com> wrote:
> 
> > My oldish AMD K7-800's clock began falling behind after
> >  rebooting from 2.6.20 (and 109 days uptime with a spotless
> >  clock) into 2.6.22; time lost is about four minutes each hour.
> > 
> > Turns out that 2.6.22 marks my TSC as unstable and starts
> >  using PIT instead. Rebooting 2.6.22 with clocksource=tsc
> >  gets the original stable system time back.

Alessandro,
Can you send me dmesg output for 2.6.20 and 2.6.22 (without
clocksource=tsc)?

thanks
-john


  reply	other threads:[~2007-07-10 17:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-09 14:27 clocksource change of behavior in 2.6.22 compared to 2.6.20 causes massive system clock slowdown Alessandro Suardi
2007-07-10  7:29 ` Andrew Morton
2007-07-10 17:28   ` john stultz [this message]
2007-07-10 23:31     ` Alessandro Suardi
2007-07-11 21:06       ` john stultz
2007-07-12 11:03         ` Tilman Schmidt
2007-07-17 22:31         ` Alessandro Suardi
2007-07-17 22:40           ` john stultz
2007-07-18 21:31             ` Alessandro Suardi

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=1184088500.30575.9.camel@localhost \
    --to=johnstul@us.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=alessandro.suardi@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.