All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Chubb <peter@chubb.wattle.id.au>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] NTP broken?
Date: Wed, 29 May 2002 05:04:54 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590701905609@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905591@msgid-missing>

>>>>> "David" = David Mosberger <davidm@napali.hpl.hp.com> writes:

>>>>> 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 to
Peter> set the clock to the correct server time.

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

David> I'm not aware of any problems with NTP keeping in sync with
David> realtime.  

OK, I now have two i2000s both running the same kernel, both
configured identically.  On one of them, NTP pulls into sync within a
few minutes.  The other just drifts further and further away.

One interesting `feature' is that on the one that keeps running away,
the CPU clock is detected as 718.793988 MHz not the supposedly correct
733MHz.  The boot message says:
	 CPU 0: base freq\x130.684MHz, ITC ratio\x11/2, ITC
		freqq8.764MHz
My suspicion is that this is incorrect on this machine, and it is
*really* at 733MHz --- which would explain the lack of sync (NTP just
can't slow the clock down enough) and the runaway time (733/718 is
around 1.02; which corresponds to a second a minute) 

The BIOS reports 733MHz, though.

Peter C


  parent reply	other threads:[~2002-05-29  5:04 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
2002-05-28 22:48 ` Luck, Tony
2002-05-28 23:05 ` David Mosberger
2002-05-29  5:04 ` Peter Chubb [this message]
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-105590701905609@msgid-missing \
    --to=peter@chubb.wattle.id.au \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.