linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: watermodem <aquamodem@ameritech.net>
To: Horst von Brand <brand@jupiter.cs.uni-dortmund.de>
Cc: Greg Boyce <gboyce@rakis.net>, linux-kernel@vger.kernel.org
Subject: Re: Machines misreporting Bogomips
Date: Sun, 03 Feb 2002 01:39:37 -0600	[thread overview]
Message-ID: <3C5CE939.6030609@ameritech.net> (raw)
In-Reply-To: <200202010959.g119xXH3008047@tigger.cs.uni-dortmund.de>

Horst von Brand wrote:

> Greg Boyce <gboyce@rakis.net> said:
> 
> [...]
> 
> 
>>Every once in a while we come across single machines which are running a
>>lot slower than they should be, and are misreporting their speed in
>>bogomips under /proc/cpuinfo.  Reinstalling the OS and changing versions
>>of the kernel don't appear to affect the machines themselves at all.
>>
> 
> Just misrepresented bogomips or is the machine really slower? Perhaps the
> CPU is being underclocked?
> 

If they are Intel CPU's and the heatsink <-> CPU connection is poor
(no heatsink compound, heatsink loose) or the fan is dead/dying or
due to dust poor airflow this is reasonable.   Intel CPUs slow down
when they get hot as as safety measure.

Clean the machine,  remove the heatsink/fan. Replace fan if needed.
(they are cheap so replace).  Clean or replace heatsink.  Apply a
good heatsink compound such as ArticSilver. [just a small dab]
Make sure you have proper contact and preasure.   Re-run the speed test.

If the video card, case or motherboard have fans check them too.
Note that some of these heatsinks are epoxied on with a conductive
epoxy so it is unlikely that you could safely remove those. Replacing
the fans is ok though.  If you are unsure of the proceses go to
one of the hardware or overclocking web pages.







  parent reply	other threads:[~2002-02-03  7:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-31 22:55 Machines misreporting Bogomips Greg Boyce
2002-01-31 23:21 ` Matthew Dharm
2002-01-31 23:30   ` Roger Larsson
2002-02-01  0:11     ` Greg Boyce
2002-02-01  9:59 ` Horst von Brand
2002-02-01 17:11   ` Greg Boyce
2002-02-01 12:59     ` gmack
2002-02-01 20:53       ` Greg Boyce
2002-02-01 23:41         ` Alan Cox
2002-02-01 23:34           ` Greg Boyce
2002-02-01 23:59             ` Alan Cox
2002-02-03 22:05             ` Juhan Ernits
2002-02-03  7:39   ` watermodem [this message]
2002-02-08 17:13 ` Andrew Scott
     [not found] <no.id>
2002-02-03 21:40 ` Barry K. Nathan

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=3C5CE939.6030609@ameritech.net \
    --to=aquamodem@ameritech.net \
    --cc=brand@jupiter.cs.uni-dortmund.de \
    --cc=gboyce@rakis.net \
    --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;
as well as URLs for NNTP newsgroup(s).