mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: john stultz <johnstul@us.ibm.com>
Cc: Jean-Christian de Rivaz <jc@eclis.ch>,
	linux-kernel@vger.kernel.org, dean@arctic.org
Subject: Re: NTP broken with 2.6.14
Date: Thu, 3 Nov 2005 16:12:43 -0500	[thread overview]
Message-ID: <20051103211243.GU9486@csclub.uwaterloo.ca> (raw)
In-Reply-To: <1131051627.27168.590.camel@cog.beaverton.ibm.com>

On Thu, Nov 03, 2005 at 01:00:27PM -0800, john stultz wrote:
> You could try disabling NTP and running the python script I sent out
> earlier in this thread to determine your systems ppm drift. Outside
> +/-500ppm is def broken, outside of +/-250ppm is probably broken,
> outside +/-100ppm isn't great but correctable and inside +/-100ppm is
> (unfortunately) pretty average for most hardware.

Well with no ntpd running on 2.6.14, it appears that my nforce2 board
matches that bug rather well.  About a second gained every minute or
two.

> Ok, do you want to open your own bug on this and we'll mark them
> duplicate as needed?
> 
> Please attach dmesg output to the bug as well.

Well it seems whatever was wrong with 2.6.12 for me, isnt' a problem in
2.6.14, as it is not gaining 10 to 15 seconds every minute now.  It is
still gaining a bit though.  I have no tried to run without the local
apic in case that makes a difference.

Len Sorensen

  reply	other threads:[~2005-11-03 21:12 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-02 23:05 Jean-Christian de Rivaz
2005-11-02 23:21 ` john stultz
2005-11-02 23:37   ` Jean-Christian de Rivaz
2005-11-03  0:15     ` john stultz
2005-11-03  0:45       ` Jean-Christian de Rivaz
2005-11-03  1:07         ` john stultz
2005-11-03  2:26           ` Jean-Christian de Rivaz
2005-11-03 19:32             ` john stultz
2005-11-03 19:51               ` Lennart Sorensen
2005-11-03 20:11                 ` john stultz
2005-11-03 20:48                   ` Lennart Sorensen
2005-11-03 21:00                     ` john stultz
2005-11-03 21:12                       ` Lennart Sorensen [this message]
2005-11-03 21:28                   ` Jean-Christian de Rivaz
2005-11-03 21:12               ` Jean-Christian de Rivaz
2005-11-03 21:41                 ` john stultz
2005-11-03 22:10                   ` Jean-Christian de Rivaz
2005-11-03 22:54                     ` john stultz
2005-11-04  0:15                       ` Jean-Christian de Rivaz
2005-11-04  0:40                         ` john stultz
2005-11-04  2:50                           ` Jean-Christian de Rivaz
2005-11-06 22:49                             ` Hans-Peter Jansen
2005-11-07 21:44                               ` Jean-Christian de Rivaz
2005-11-04 12:40                       ` Maciej W. Rozycki
2005-11-02 23:24 ` john stultz
2005-11-03  0:36 ` Roman Zippel
2005-11-03  1:13   ` Jean-Christian de Rivaz
2005-11-03  9:42     ` Roman Zippel
2005-11-04  3:44 Brown, Len
2005-11-04  4:07 ` john stultz
2005-11-04 13:51   ` Lennart Sorensen
2005-11-04 16:39   ` Jean-Christian de Rivaz
2005-11-04 17:41     ` Jean-Christian de Rivaz

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=20051103211243.GU9486@csclub.uwaterloo.ca \
    --to=lsorense@csclub.uwaterloo.ca \
    --cc=dean@arctic.org \
    --cc=jc@eclis.ch \
    --cc=johnstul@us.ibm.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

all inboxes | Powered by JetHome®