mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Marc Perkel <mperkel@yahoo.com>
To: Chris Snook <csnook@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: AMD Quad Core clock problem?
Date: Fri, 11 Apr 2008 15:09:35 -0700 (PDT)	[thread overview]
Message-ID: <735874.9676.qm@web52502.mail.re2.yahoo.com> (raw)
In-Reply-To: <47FFD3F3.50107@redhat.com>


--- Chris Snook <csnook@redhat.com> wrote:

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

Is it possible due to calibration that ntpd isn't able
to correct the problem? Is there a setting to make ntp
more agressive?


Marc Perkel
Junk Email Filter dot com
http://www.junkemailfilter.com

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

  parent reply	other threads:[~2008-04-11 22:09 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-11 18:27 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
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 [this message]
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=735874.9676.qm@web52502.mail.re2.yahoo.com \
    --to=mperkel@yahoo.com \
    --cc=csnook@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    /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