From: Nico Schottelius <nicos-mutt@pcsystems.de>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: cpu speed is 165mhz instead of real 650mhz
Date: Wed, 24 Jul 2002 13:01:21 +0200 [thread overview]
Message-ID: <20020724110121.GA1925@schottelius.org> (raw)
Hello guys!
This periodicly appears in my system. The Kernel seems to misdetect the
right cpu speed and then it's running only at 165mhz.
I don't really understand why this happens, there's no acpi enabled, which
caused this failure the last time.
I attached .config of 2.5.24 [which still runs fine with devfs :) ]
and /proc/cpuinfo.
Please cc me when answering.
Nico
--
Please send your messages pgp-signed and/or pgp-encrypted (don't encrypt mails
to mailing list!). If you don't know what pgp is visit www.gnupg.org.
(public pgp key: ftp.schottelius.org/pub/familiy/nico/pgp-key)
next reply other threads:[~2002-07-24 8:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-24 11:01 Nico Schottelius [this message]
2002-07-24 10:27 ` cpu speed is 165mhz instead of real 650mhz Joshua Uziel
2002-07-24 13:16 ` Nico Schottelius
2002-07-24 20:13 ` george anzinger
2002-08-02 3:57 ` Nico Schottelius
-- strict thread matches above, loose matches on Subject: below --
2002-07-24 11:39 Nico Schottelius
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=20020724110121.GA1925@schottelius.org \
--to=nicos-mutt@pcsystems.de \
--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