All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Walton <kj6eo@kj6eo.com>
To: Haines Brown <brownh@hartford-hwp.com>
Cc: linux-hams@vger.kernel.org
Subject: Re: Tracking down a Linux crash
Date: Thu, 17 Oct 2002 13:17:13 -0700	[thread overview]
Message-ID: <3DAF1AC9.91BA36B8@kj6eo.com> (raw)
In-Reply-To: 200210171202.g9HC2KD08295@hartford-hwp.com

Hi Haines -

I was using a temperature probe wrapped around the bottom of the CPU
cooling fan.  The probe plugs into a Digital Volt Meter that I bought down
at Sears.  I put the system into a "kernel compile" then slowed down the
speed of the CPU cooling fan via the adjustable power supply.  When the
CPU would reach 60C (plus or minus a degree sometimes), it would just
sieze up "freeze".  The CPU would not recover so I would have to cool it off
and do a cold boot on the entire system.  During this test I would spray some
"component cooler" (freeze spray) lightly on the motherboard to keep it
cool.  You can get the freeze spray at almost any electronics store.  You can
also turn those cans of "compressed air" into freeze spray by holding them
upside down while spraying them.  Be advised that some of the compressed
air (canned) stuff is flammable.  Should you spray it into say some high
voltage it will ignite (you may have known that already).

Since I determined the sieze up temperature of the CPU all I had to do was
to stop cooling down the motherboard with the freeze spray.  And sure
enough at around 50 to 51C the system hung up.  I went down to the local
computer store and exchanged the motherboard....problem resolved.

In my opinion nobody should intentionally overheat their CPU.  In my case
the CPU was "inexpensive".  Furthermore I asked my friends down at the
computer store what type of heat the "Duron" could take before it would
sieze.  I work in the electronics industry, I own a small business and we
service high resolution X-Ray equipment down to component level.  I can't
begin to tell you how many electronics problems I have isolated by
cooling suspected components down with freeze spray (>:  It's just a trick
of the trade.

Regards,

Bill KJ6EO

Haines Brown wrote:

> > I put a variable powersupply on the CPU fan and slowly starved it
> > for air to see if I could duplicate the problem that I was having.
> > The Duron 1300 locked up at 60 degrees C.  Even on the hottest days
> > I was not exceeding a CPU temperature of 50 degrees C max.  To make
> > a long story short, my problem was due to a motherboard failure.  I
> > traced it down by using some component cooler.  I replaced the MB
> > .... problem solved.
>
> Bill,
>
> Could I ask for a little more detail? How were you measuring CPU
> temperature? What do you mean by a "component cooler?" Did you select
> areas of the MB to cool and then await the result?
>
> Haines Brown KB1GRM


  reply	other threads:[~2002-10-17 20:17 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-16 13:08 Tracking down a Linux crash John Ackermann N8UR
2002-10-16 13:20 ` Kelly Black
2002-10-16 13:23   ` Kelly Black
2002-10-16 13:25   ` John Ackermann N8UR
2002-10-16 14:20     ` Tomi Manninen OH2BNS
2002-10-16 14:40     ` Haines Brown
2002-10-16 15:55       ` John Ackermann N8UR
2002-10-16 15:21     ` jjgpg
2002-10-16 14:11 ` jbennett
2002-10-16 16:38   ` Curt Mills, WE7U
2002-10-16 14:17 ` jbennett
2002-10-16 14:18 ` terry
2002-10-16 21:52   ` Nate Bargmann
2002-10-17  2:33   ` Bob Nielsen
2002-10-16 14:35 ` w9ya
2002-10-18 13:02   ` Tracking down a Linux crash (update) John Ackermann N8UR
2002-10-18 17:41     ` Ray Heasman
2002-10-18 17:55       ` John Ackermann N8UR
2002-10-16 20:49 ` Tracking down a Linux crash Ben Gelb
2002-10-17  6:38 ` Bill Walton
2002-10-17 12:02   ` Haines Brown
2002-10-17 20:17     ` Bill Walton [this message]
2002-10-17  7:59 ` Volker Schroer
  -- strict thread matches above, loose matches on Subject: below --
2002-10-16 13:52 Pär Flitt
2002-10-16 16:35 ` Curt Mills, WE7U
2002-10-16 21:02 Ben Gelb

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=3DAF1AC9.91BA36B8@kj6eo.com \
    --to=kj6eo@kj6eo.com \
    --cc=brownh@hartford-hwp.com \
    --cc=linux-hams@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.