From: Kelly Black <krblack@penguinpackets.com>
To: linux-hams@vger.kernel.org
Subject: Re: Tracking down a Linux crash
Date: 16 Oct 2002 08:23:50 -0500 [thread overview]
Message-ID: <1034774630.5516.6.camel@edith> (raw)
In-Reply-To: <1034774433.5514.2.camel@edith>
> On Wed, 2002-10-16 at 08:08, John Ackermann N8UR wrote:
> > Hi all --
> >
> > I realize this may be a bit off-topic, but my rationale is that (a) I'm
> > among knowledgeable friends, and (b) this machine is destined to be my
> > hamshack system, displacing a Windows box.
> >
> ---Snip long description---
>
Could the problem be heat related? What is the CPU temp when the
lockups occur (or just after a reboot). Does anything show up in the
logs (kernel panics or anything suspicious?).
Kelly Black
KB0GBJ
next prev parent reply other threads:[~2002-10-16 13:23 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 [this message]
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
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=1034774630.5516.6.camel@edith \
--to=krblack@penguinpackets.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox