public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Snook <csnook@redhat.com>
To: Marc Perkel <mperkel@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: AMD Quad Core clock problem?
Date: Fri, 11 Apr 2008 17:11:15 -0400	[thread overview]
Message-ID: <47FFD3F3.50107@redhat.com> (raw)
In-Reply-To: <628754.88392.qm@web52501.mail.re2.yahoo.com>

Marc Perkel wrote:
> --- Chris Snook <csnook@redhat.com> wrote:
> 
>> Marc Perkel wrote:
>>> I was just wondering if there were any known
>> issues
>>> with AMD quad core phenom clock drift problems?
>> I';m
>>> running a 2.6.24 kernel and it's losing time. I
>>> remember the first dual core AMD chips had a lot
>> of
>>> clock issues.
>>>
>>> If this is something new let me know what
>> information
>>> to check and post to this list.
>> When reporting clock problems, please post dmesg. 
>> This has all the 
>> interesting timekeeping-related log messages from
>> the kernel.  Please 
>> also describe the drift quantitatively.
>>
>> -- Chris
>>
> 
> OK - thanks Chris.
> 
> The drift is small. It loses a few seconds every hour.
> And it might not be kernel related. I just remembered
> the early dual core days when this took months to get
> right. I'm running several dual core computers and the
> only one drifting is the quad. All are running the
> same OS and kernel.

With the older chips, each core had its own TSC, which caused 
synchronization problems.  The Barcelona generation chips (including 
your Phenom) have a constant frequency TSC on the northbridge, so they 
should be immune to these problems.

If it's steadily losing a few seconds every hour, it's probably just 
slightly mis-calibrated hardware.  ntp should fix this right up.  If the 
drift is more extreme than ntp can correct for, or the drift keeps 
changing, or time is jumping around, that is definitely something that 
could be a bug.

> hpet clockevent registered
> TSC calibrated against HPET
> Marking TSC unstable due to TSCs unsynchronized

It's possible that in future kernels we'll be a few clock cycles more 
accurate in calibrating this on Barcelona chips, but calibration is only 
as good as the standard of comparison.  There will always be hardware 
that's slightly off, so run ntp, or use a nightly ntpdate cronjob.  If 
your time starts drifting drastically or jumping around, please yell 
really loud.

-- Chris

  reply	other threads:[~2008-04-11 21:11 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-11 18:27 AMD Quad Core clock problem? Marc Perkel
2008-04-11 18:35 ` H. Willstrand
2008-04-11 18:38 ` Chris Snook
2008-04-11 20:28   ` Marc Perkel
2008-04-11 21:11     ` Chris Snook [this message]
2008-04-11 21:36       ` Marc Perkel
2008-04-11 21:38         ` Lennart Sorensen
2008-04-13 19:35           ` H. Peter Anvin
2008-04-14 15:12             ` Lennart Sorensen
2008-04-14 16:23               ` H. Peter Anvin
2008-04-14 16:29                 ` Lennart Sorensen
2008-04-15  1:11               ` Krzysztof Halasa
2008-04-15  1:24                 ` H. Peter Anvin
2008-04-15  1:45                   ` Krzysztof Halasa
2008-04-15  2:40                     ` H. Peter Anvin
2008-04-11 21:46         ` Krzysztof Halasa
2008-04-11 22:09       ` Marc Perkel
2008-04-13  8:19         ` Bart Van Assche
2008-04-12  1:04       ` Marc Perkel
2008-04-14 19:16         ` Chris Snook
2008-04-14 20:46           ` Marc Perkel
2008-04-15  6:11           ` Bart Van Assche
2008-04-16 21:44             ` Marc Perkel
2008-04-17  6:17               ` Bart Van Assche
2008-04-17 18:03                 ` Marc Perkel
2008-04-18 11:56                   ` Bart Van Assche
2008-06-17 21:09           ` Marc Perkel
2008-04-14 13:40       ` Marc Perkel

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=47FFD3F3.50107@redhat.com \
    --to=csnook@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mperkel@yahoo.com \
    /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