From: Austin Gonyou <austin@digitalroadkill.net>
To: Steve Cole <coles@vip.kos.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Dual Athlon 2000 XP MP nightmare
Date: 15 Jun 2002 19:37:20 -0500 [thread overview]
Message-ID: <1024187840.19232.3.camel@UberGeek> (raw)
In-Reply-To: <003101c214bb$0275a720$0a00000a@kos.net>
On Sat, 2002-06-15 at 17:21, Steve Cole wrote:
> I'm not sure that what I'm experiencing is a kernel problem, but I thought
> I would stick my foot in the door nonetheless, since I have no real
> indication of what is going on.
One thing which could remedy this is using the KDB. (kernel debugger) If
you get the -aa series kernels/patches you can get this functionality.
(Dunno if -ac has it built it). Once the machine crashes, as long as
it's not a black screen, then you can get a back-trace on the process
and even possibly find the section of code that's actually causing the
problem right off the bat,(not usual and YMMV), though probably not, but
it's an enormous amount of info that you can't get ATM.
> If it's hardware for sure, please just indicate that and I'll move on. I'm
> getting semi-desperate. :(
--
Austin Gonyou <austin@digitalroadkill.net>
next prev parent reply other threads:[~2002-06-16 0:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-15 22:21 Dual Athlon 2000 XP MP nightmare Steve Cole
2002-06-15 22:58 ` Dr. David Alan Gilbert
2002-06-17 2:30 ` Shawn
2002-06-17 2:35 ` Shawn
2002-06-16 0:37 ` Austin Gonyou [this message]
2002-06-16 8:30 ` Mark Hounschell
2002-06-16 12:29 ` Allan Sandfeld Jensen
2002-06-19 12:00 ` Bill Davidsen
2002-06-16 21:06 ` Austin Gonyou
-- strict thread matches above, loose matches on Subject: below --
2002-06-16 0:54 Hugh
2002-06-16 6:35 ` Austin Gonyou
2002-06-18 9:19 Hugh
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=1024187840.19232.3.camel@UberGeek \
--to=austin@digitalroadkill.net \
--cc=coles@vip.kos.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