From: Austin Gonyou <austin@digitalroadkill.net>
To: Hugh <hugh@nospam.com>
Cc: linux-kernel@vger.kernel.org, coles@vip.kos.netDear
Subject: Re: Dual Athlon 2000 XP MP nightmare
Date: 16 Jun 2002 01:35:02 -0500 [thread overview]
Message-ID: <1024209302.26299.4.camel@UberGeek> (raw)
In-Reply-To: <3D0BE1AC.3080202@nospam.com>
It does most sound like some mis-behaving kernel code. No hard locks it
sounds like...but kernel panics and no joy. I'd for sure recommend KDB
for this chore, it will at least shed light on the misbehaving piece.
On Sat, 2002-06-15 at 19:54, Hugh wrote:
> Dear Steve, Richard, and others,
>
> >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.
> >
....
>
> That was when I returned the motherboard the second time.
> The first time, the board gave me a CMOS error. The third time, the
> board even did not give me the first beep. I now think that I should
> have bought the Tyan board instead of the ASUS.
>
> Regards,
>
> G. Hugh Song
>
>
>
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Austin Gonyou <austin@digitalroadkill.net>
next prev parent reply other threads:[~2002-06-16 6:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-16 0:54 Dual Athlon 2000 XP MP nightmare Hugh
2002-06-16 6:35 ` Austin Gonyou [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-18 9:19 Hugh
2002-06-15 22:21 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
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
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=1024209302.26299.4.camel@UberGeek \
--to=austin@digitalroadkill.net \
--cc=coles@vip.kos.netDear \
--cc=hugh@nospam.com \
--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