From: Bruce Harada <bruce@ask.ne.jp>
To: Ben Greear <greearb@candelatech.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Locked up 2.4.10-pre11 on Tyan 815t motherboard.
Date: Thu, 20 Sep 2001 03:38:41 +0900 [thread overview]
Message-ID: <20010920033841.2079e414.bruce@ask.ne.jp> (raw)
In-Reply-To: <3BA8DF59.B9F536B4@candelatech.com>
In-Reply-To: <3BA84088.27698798@candelatech.com> <3BA8CCF1.CA2933B3@zip.com.au> <3BA8D351.F57BE70D@candelatech.com> <3BA8D619.9A607219@zip.com.au> <3BA8DF59.B9F536B4@candelatech.com>
On Wed, 19 Sep 2001 11:09:29 -0700
Ben Greear <greearb@candelatech.com> wrote:
>
> When I opened the machine the first time (before I powered it up),
> I noticed that the CPU fan's wires were tangled in the fan such that
> it couldn't move.. I fixed that, but it could have been run before
> I received the machine... Could that cause this problem you think??
Doubtful. Since it's an 815, I presume you're running a PIII (correct me if
I'm wrong) - newish PIIIs have reasonable overheating cutout features, and
if overheating had damaged the CPU, I'd be very surprised if it worked at
all, rather than just locking up on certain sizes of network packets.
next prev parent reply other threads:[~2001-09-19 18:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-19 6:51 Ben Greear
2001-09-19 7:10 ` Ben Greear
[not found] ` <3BA8CCF1.CA2933B3@zip.com.au>
[not found] ` <3BA8D351.F57BE70D@candelatech.com>
[not found] ` <3BA8D619.9A607219@zip.com.au>
2001-09-19 18:09 ` Ben Greear
2001-09-24 15:14 ` bill davidsen
2001-09-24 18:18 ` Ben Greear
2001-09-19 18:38 ` Bruce Harada [this message]
2001-09-19 19:15 ` Alan Cox
2001-09-19 19:53 ` Ben Greear
2001-09-19 20:03 ` Jeff Garzik
2001-09-19 20:05 ` Alan Cox
2001-09-19 20:40 ` Locked up 2.4.10-pre11 on Tyan 815t motherboard. [EEPRO-100 bugs] Ben Greear
2001-09-19 21:57 ` Alan Cox
2001-09-20 19:28 ` Locked up 2.4.10-pre11 on Tyan 815t motherboard Martin Josefsson
2001-09-19 19:46 ` Ben Greear
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=20010920033841.2079e414.bruce@ask.ne.jp \
--to=bruce@ask.ne.jp \
--cc=greearb@candelatech.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
Powered by JetHome