From: Nathan Walp <faceprint@faceprint.com>
To: linux-kernel@vger.kernel.org
Subject: Re: OOPSes and BUGs everywhere (2.4.0)
Date: Tue, 06 Feb 2001 09:05:19 -0500 [thread overview]
Message-ID: <3A80049F.A63907B@faceprint.com> (raw)
In-Reply-To: <3A7ECD8C.B847B770@faceprint.com>
Nathan Walp wrote:
> I'm gonna type fast and send this as soon as possible, cuz I'm not sure
> how long i'll be able to stay up. I'm OOPSing and BUGging (is that a
> word?) like crazy, and I can't figure it out. I thought it was the BIOS
> upgrade I did, but downgrading didn't do anything. System is 1.1GHz
> Tbird on Asus A7V, mixed SCSI and IDE. I hope to post a follow-up w/
> more info shortly, but here's the bulk of the info.
>
> Nathan
Don't worry about these oopses and bugs...MAJOR hardware issues, I think i have a faulty chip. segfaults on clean deb potato system. windows WAS stable, till I started actually using the CPU, then
BSOD all over the place. I guess it's time to see how good that warranty really is ;-) Sorry for all the trouble.
Nathan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2001-02-06 14:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-05 15:58 OOPSes and BUGs everywhere (2.4.0) Nathan Walp
2001-02-06 14:05 ` Nathan Walp [this message]
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=3A80049F.A63907B@faceprint.com \
--to=faceprint@faceprint.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