From: Bill Walton <kj6eo@kj6eo.com>
To: John Ackermann N8UR <jra@febo.com>
Cc: linux@lists.tapr.org, linux-hams@vger.kernel.org
Subject: Re: Tracking down a Linux crash
Date: Wed, 16 Oct 2002 23:38:14 -0700 [thread overview]
Message-ID: <3DAE5AD6.5CE83E7F@kj6eo.com> (raw)
In-Reply-To: 3031448.1034759336@WUSJA129861-8HP
Hi John -
The others are much more qualified than me to comment on your problem but I do
have some information that I would like to contribute. Recently I have built a
prototype system (RH7.2)(2.4.19)(Duron 1300)(MSI KT3 Ultra2)(250MB DDR
SDRAM)(30gig Maxtor 7200 HD)(TNT2 PCI Video Card)(D-Link Lan cards).
I had the same type of failure that your having and it was driving me nuts. My
servers are in a 19" rack cabinet out in the garage. As you can imagine during the
hot summer months the servers take a beating out there. However I do run every
type of cooler gadget I can get my hands on...even HD coolers. Believe it or not
they work great out there inspite of the heat.
In my case I had to determine if the CPU was locking up, or if the MB, or something
else was overheating. I ran a heat test on the DURON 1300. 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.
I don't know about the Athlon processor but the Duron runs extremely hot. The
run of the mill CPU cooler down at the computer store just will not cut it. I am
running a copper heatsink CPU cooler now with a high speed fan, heat pipes, silver
grease, etc. Even on the hottest days I don't exceed around 42 degrees C.
It would be interesting to know what temperature your CPU is running at! I bet that
the Athlon would lock up at 60 degrees C. If you have a good CPU cooler that
would be almost impossible to accomplish inside your house with the AC on.
Good Luck,
Bill KJ6EO
next prev parent reply other threads:[~2002-10-17 6:38 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 [this message]
2002-10-17 12:02 ` Haines Brown
2002-10-17 20:17 ` Bill Walton
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=3DAE5AD6.5CE83E7F@kj6eo.com \
--to=kj6eo@kj6eo.com \
--cc=jra@febo.com \
--cc=linux-hams@vger.kernel.org \
--cc=linux@lists.tapr.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