mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jonathan A. Davis" <davis@jdhouse.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.19-pre4-ac2
Date: 26 Mar 2002 19:47:05 -0600	[thread overview]
Message-ID: <1017193625.1435.18.camel@bacchus.jdhouse.org> (raw)
In-Reply-To: <E16q29I-0004Qr-00@the-village.bc.nu>

On Tue, 2002-03-26 at 19:22, Alan Cox wrote:
> Linux 2.4.19pre4-ac2

Alan and Co,

By chance I was culling through my boot log and noticed the following:

Initializing CPU#0
Detected 8132.282 MHz processor.

Now, I'd *love* to have a processor that could do that for real, but
don't think my Athlon XP quite makes the grade.  :-)

Looking through my boot logs, this problem seems to start somewhere
between 2.4.19-pre2-ac4 and 2.4.19-pre4-ac1 (I didn't run any of the
intervening releases).

It's also sporadic -- out of 5 reboots, the proper speed (1466.559 MHz)
was detected 2 of the 5 times.  Dropping back to 2.4.19-pre2-ac4 gives
me correct detection 5 of 5.  No config changes were made between these
kernels (except =n for any new options).

System:

Athlon XP 1700+
Soyo SY-K7VX MB (VIA KT266A)
1GB ECC PC2100 Memory
Redhat 7.2 (stock+updates with the exception of the kernel and XFree 4.2
(to support my ATI 7500 card)
Everything from the P/S to the cpu fan is AMD spec'd and environment
sensors show normal.

Please let me know if more info is needed...

-- 

-Jonathan <davis@jdhouse.org>

          * "The mind is like a parachute. It works best when open." *

  reply	other threads:[~2002-03-27  1:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-27  1:22 Alan Cox
2002-03-27  1:47 ` Jonathan A. Davis [this message]
2002-03-27  2:10   ` Alan Cox

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=1017193625.1435.18.camel@bacchus.jdhouse.org \
    --to=davis@jdhouse.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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®