From: David Rees <drees76@gmail.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Mika Tiainen <mikat@iki.fi>,
Andreas Herrmann <andreas.herrmann3@amd.com>,
linux-kernel@vger.kernel.org
Subject: Re: Slow clock on AMD 740G chipset
Date: Fri, 24 Apr 2009 18:45:46 -0700 [thread overview]
Message-ID: <72dbd3150904241845q5ed1fe15ob4fa2ba06e96ea72@mail.gmail.com> (raw)
In-Reply-To: <49C919B9.70302@msgid.tls.msk.ru>
On Tue, Mar 24, 2009 at 10:34 AM, Michael Tokarev <mjt@tls.msk.ru> wrote:
> 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.
This is really weird. I earlier posted to the thread saying things
were fine on a Fedora 10 2.6.27.9-159.fc10.x86_64 kernel.
Then mysteriously after a machine reboot to install new hardware[1] on
March 27th on kernel 2.6.27.19-170.2.35.fc10.x86_64 (previous running
kernel was the same), the clock started running slow to the tune of
ntpd resetting the time every 15-18 minutes forward about 2.3 seconds.
Fast forward to today (now running 2.6.29.1-30.fc10.x86_64) and the
clock is still running slow.
> 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.
I don't know - my system (GA-MA74GM-S2 mobo) is still broken.
[1] So the hardware I installed was a SATA SSD (OCZ Vertex). Ever
since then, the clock has been running fast. Previously, the only
thing on the SATA bus was a DVD drive - it has two IDE drives, one
plugged in on board and the other into a Promise IDE card.
When doing so, the sata ports are now running in AHCI mode instead of
native mode. I'll have to try switching later.
-Dave
next prev parent reply other threads:[~2009-04-25 1:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-20 14:16 Mika Tiainen
2009-01-20 18:46 ` David Rees
2009-03-10 10:18 ` Andreas Herrmann
2009-03-11 10:05 ` Andreas Herrmann
2009-03-11 11:59 ` Michael Tokarev
2009-03-11 14:43 ` Mika Tiainen
2009-03-24 17:34 ` Michael Tokarev
2009-03-24 22:27 ` john stultz
2009-04-25 1:45 ` David Rees [this message]
2009-04-30 23:17 ` David Rees
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=72dbd3150904241845q5ed1fe15ob4fa2ba06e96ea72@mail.gmail.com \
--to=drees76@gmail.com \
--cc=andreas.herrmann3@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikat@iki.fi \
--cc=mjt@tls.msk.ru \
/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
Powered by JetHome