From: "Bart Van Assche" <bart.vanassche@gmail.com>
To: "Marc Perkel" <mperkel@yahoo.com>
Cc: "Chris Snook" <csnook@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: AMD Quad Core clock problem?
Date: Sun, 13 Apr 2008 10:19:22 +0200 [thread overview]
Message-ID: <e2e108260804130119r27a2ccb8sc7f03b43c6177d33@mail.gmail.com> (raw)
In-Reply-To: <735874.9676.qm@web52502.mail.re2.yahoo.com>
On Sat, Apr 12, 2008 at 12:09 AM, Marc Perkel <mperkel@yahoo.com> wrote:
>
> Is it possible due to calibration that ntpd isn't able
> to correct the problem? Is there a setting to make ntp
> more agressive?
Clock crystals typically have an error between 20 and 200 ppm. ntpd
can correct clock crystal errors of maximum 500 ppm. If I remember
correctly the kernel limits frequency adjustments to 512 ppm. It's not
a good idea to try to change this limit -- large clock crystal errors
slow down convergence of ntpd's algorithms significantly.
Bart.
next prev parent reply other threads:[~2008-04-13 8:19 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
2008-04-13 8:19 ` Bart Van Assche [this message]
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=e2e108260804130119r27a2ccb8sc7f03b43c6177d33@mail.gmail.com \
--to=bart.vanassche@gmail.com \
--cc=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
all inboxes | Powered by JetHome®