Date: Tue, 18 May 1999 08:44:44 -0700 (PDT) From: John Polstra <jdp@polstra.com> To: Doug Rabson <dfr@nlsystems.com> Cc: alpha@freebsd.org Subject: Re: Clock drift on the alpha Message-ID: <XFMail.990518084444.jdp@polstra.com> In-Reply-To: <Pine.BSF.4.05.9905181007370.509-100000@herring.nlsystems.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I'm trying Doug's clock calibration patch. Though the system hasn't
been up very long yet, it's already doing _much_ better. xntpd is
actually able to sync up now, instead of giving up in despair every 7
minutes like it did before. I'll report again later in the day after
it's had time to settle in.
The calibration found a much different clock frequency than had been
found before:
before: Timecounter "alpha" frequency 531914893 Hz
after: Timecounter "alpha" frequency 533180986 Hz
I'd say the "before" number was just plain wrong. I noticed that on
beast, there's no disagreement between the nominal CPU speed and the
nominal clock frequency:
Digital AlphaPC 164 500 MHz, 500MHz
Maybe on the 533 MHz version they transcribed bit 2**20 incorrectly
... :-)
John
--
John Polstra jdp@polstra.com
John D. Polstra & Co., Inc. Seattle, Washington USA
"Self-interest is the aphrodisiac of belief." -- James V. DeLong
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.990518084444.jdp>