public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] NTP broken?
Date: Sat, 25 May 2002 02:33:11 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590701905600@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905591@msgid-missing>

>>>>> On Wed, 22 May 2002 13:08:08 +1000, Peter Chubb <peter@chubb.wattle.id.au> said:

  Peter> NTP on Linux 2.4.17/IA64 appears broken.  ntpd never seems to
  Peter> be able to pull the PLL into sync, even after using ntpdate
  Peter> to set the clock to the correct server time.

  Peter> What are other peoples' experiences with NTP on IA64?

I'm not aware of any problems with NTP keeping in sync with realtime.
However, I do think the drift on the kernel's time-of-day (without NTP
synchronization) may be bigger than it could be.  This could be due to
rounding errors, due to the CPU clock not being accurate enough, or
something else entirely.  Some time ago, I did look over the code and
didn't find any obvious rounding errors, but that doesn't mean they
don't exist.  Actually, one experiment that might be worth doing is to
set HZ to 100.  This will make maintaining the time-of-day slightly
easier and since it also happens to be the freq used by x86, makes it
almost certain that there are no other subtle issues.

	--david


  parent reply	other threads:[~2002-05-25  2:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-22  3:08 [Linux-ia64] NTP broken? Peter Chubb
2002-05-22  8:09 ` Andreas Schwab
2002-05-25  2:33 ` David Mosberger [this message]
2002-05-28 22:48 ` Luck, Tony
2002-05-28 23:05 ` David Mosberger
2002-05-29  5:04 ` Peter Chubb
2002-05-29  5:13 ` Peter Chubb
2002-05-29 15:01 ` David Mosberger
2002-05-29 17:18 ` Rich Altmaier
2002-05-30  3:55 ` David Mosberger

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=marc-linux-ia64-105590701905600@msgid-missing \
    --to=davidm@napali.hpl.hp.com \
    --cc=linux-ia64@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