linux-kernel - Re: Slow clock on AMD 740G chipset

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]

Date:	Tue, 24 Mar 2009 15:27:53 -0700
From:	john stultz <johnstul@...ibm.com>
To:	Michael Tokarev <mjt@....msk.ru>
Cc:	Mika Tiainen <mikat@....fi>,
	Andreas Herrmann <andreas.herrmann3@....com>,
	linux-kernel@...r.kernel.org
Subject: Re: Slow clock on AMD 740G chipset

On Tue, Mar 24, 2009 at 10:34 AM, Michael Tokarev <mjt@....msk.ru> wrote:
> [resurrecting (hopefully) an old thread.
>  Top-posting to keep old mess around for reference.]
>
> To refresh what has been said.  Several people observed slow clock
> on their - mostly AMD 780g, 740g and 690g-based systems with 2.6.28
> 2.6.27 kernels.  Slow to a point when ntpd wasn't successful to
> keep up with the drift.  It has been said that the motherboards are
> flaky or something and that the clocks has to be calibrated, for
> which there are known procedures available (adjtimex).  Which helped.
> Before the "calibration" the clock were off by ~15 minutes per day.
>
> But today I tried newly released 2.6.29 kernel on one of the affected
> systems - just because I wanted to test something else.  And noticed
> that the clock is running too fast.  After some calculation I see that
> it will run away for about 15 minutes per day, that is, exactly the
> number which was used to compensate for slow clock on 2.6.2[78].
>
> So it seems that with 2.6.29, all the motherboards suddenly become
> non-flaky and the timers need no calibration anymore, working just
> fine.  Other operating systems and kernel versions also agree with
> this conclusion of 2.6.29.
>
> Any comments on this strange phenomenon ? :)

This sounds like the Fast PIT TSC calibration fix that Linus included
fairly late in 2.6.29-rc (commit
a6a80e1d8cf82b46a69f88e659da02749231eb36). The Fast PIT method was
causing some error on some systems, such that the TSC calibrated more
then 500ppm off of its actual value, causing NTP to not be able to
compensate (the adjtimex tick manipulation folks in this thread are
doing just pulls that value back into range where NTP can correct).

See the "Linux 2.6.29-rc6" thread for details.

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/