linux-kernel - Re: clocksource change of behavior in 2.6.22 compared to 2.6.20 causes massive system clock slowdown

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1184088500.30575.9.camel@localhost>
Date:	Tue, 10 Jul 2007 10:28:20 -0700
From:	john stultz <johnstul@...ibm.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Alessandro Suardi <alessandro.suardi@...il.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: clocksource change of behavior in 2.6.22 compared to 2.6.20
	causes massive system clock slowdown

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@...il.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

-
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/