From: Jean-Christian de Rivaz <jc@eclis.ch>
To: Gene Heskett <gene.heskett@verizon.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ntp problems
Date: Thu, 08 Dec 2005 00:34:56 +0100 [thread overview]
Message-ID: <439771A0.1000604@eclis.ch> (raw)
In-Reply-To: <200512071750.20709.gene.heskett@verizon.net>
Gene Heskett a écrit :
> On Wednesday 07 December 2005 16:56, Jean-Christian de Rivaz wrote:
>
>>Gene Heskett a écrit :
>>
>>>And, acpi is on, and ntpd is happy with the new bios. Hurrah!
>>
>>Good news!
>>
>>I wonder if it would be a good idea to add something into the kernel or
>>into ntpd to alert the users that ntpd can't run normaly because of a
>>too fast drift ? Then a BIOS upgrade could be proposed (especially on a
>>nForce2 system). I don't know if it's even realistc.
>>
>>Regards,
>
>
> The drift itself wasn't what I'd call excessive,
> something like 6 minutes in a week, which for
> mainboard quality crystals is pretty darned good.
ntpd work only on system with a drift of maximum +/-500ppm. This post
summarize a lot of informations about the problem:
http://marc.theaimsgroup.com/?l=linux-kernel&m=113105244509795&w=2
It was found later that an issue into the nForce2 is the root of the
problem and that a BIOS update solve it.
6.0 / (60*24*7) * 1e6 = 595.24
6 minutes per week is near 600ppm, it's enough to trigg the problem you
have seen. Even very cheap crystal are 100ppm at commercial temperature
range. 100ppm is about 1 minute per week. Some crystal manufacturers
propose now 30ppm as the default standard at commercial temperature range.
As your watch prove, good cristal can be just a few ppm (about 3.86ppm
for your watch)
Regards,
--
Jean-Christian de Rivaz
next prev parent reply other threads:[~2005-12-07 23:35 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-05 5:31 ntp problems Gene Heskett
2005-12-05 21:39 ` john stultz
2005-12-05 23:33 ` Gene Heskett
2005-12-06 0:14 ` john stultz
2005-12-06 2:07 ` Gene Heskett
2005-12-06 3:20 ` john stultz
2005-12-06 4:01 ` Gene Heskett
2005-12-06 7:33 ` jdow
2005-12-06 16:58 ` Gene Heskett
2005-12-07 0:48 ` jdow
2005-12-06 11:44 ` Jean-Christian de Rivaz
2005-12-06 19:02 ` Gene Heskett
2005-12-06 21:22 ` Gene Heskett
2005-12-07 5:14 ` Kyle Moffett
2005-12-07 6:08 ` Gene Heskett
2005-12-07 21:56 ` Jean-Christian de Rivaz
2005-12-07 22:50 ` Gene Heskett
2005-12-07 23:34 ` Jean-Christian de Rivaz [this message]
2005-12-08 0:14 ` Gene Heskett
2005-12-11 19:05 ` Gene Heskett
2005-12-07 3:44 ` Gene Heskett
-- strict thread matches above, loose matches on Subject: below --
2004-01-24 22:08 NTP problems Shaw, Marco
2004-01-26 8:01 ` Erik Hensema
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=439771A0.1000604@eclis.ch \
--to=jc@eclis.ch \
--cc=gene.heskett@verizon.net \
--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