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:13:05 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590701905610@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905591@msgid-missing>
>>>>> "Peter" = Peter Chubb <peter@chubb.wattle.id.au> writes:
>>>>> "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> One interesting `feature' is that on the one that keeps running
Peter> away, the CPU clock is detected as 718.793988 MHz not the
Peter> supposedly correct 733MHz.
Guess what. After the reboot that I did to find out what the BIOS
said, the kernel now reports the correct cpu clock frequency, and NTP
works.
Peter C
next prev parent reply other threads:[~2002-05-29 5:13 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
2002-05-29 5:13 ` Peter Chubb [this message]
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-105590701905610@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox