From: Ben Greear <greearb@candelatech.com>
To: Bruce Harada <bruce@ask.ne.jp>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Locked up 2.4.10-pre11 on Tyan 815t motherboard.
Date: Wed, 19 Sep 2001 12:46:04 -0700 [thread overview]
Message-ID: <3BA8F5FC.BFDF5126@candelatech.com> (raw)
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> <20010920033841.2079e414.bruce@ask.ne.jp>
Bruce Harada wrote:
>
> 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.
Yes, it's a PIII 1Ghz. I'm not sure how important the packet sizes
are: I can lock it with 64 byte and 128 byte packets, with the commonality
being that the CPU is maxed out and there are a massive number of little
packets all over the place.
Also, the traffic I'm running is raw packets sent straight to the
driver, not IP....
I took out the 4-port Tulip NIC and I haven't locked it up yet, though
I'm getting really sorry performance out of the sketchy machine for
some reason or another. Still, the problem definately seems related
to the DLINK 4-port NIC at this point...
Ben
--
Ben Greear <greearb@candelatech.com> <Ben_Greear@excite.com>
President of Candela Technologies Inc http://www.candelatech.com
ScryMUD: http://scry.wanfear.com http://scry.wanfear.com/~greear
next prev parent reply other threads:[~2001-09-19 19:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-19 6:51 Locked up 2.4.10-pre11 on Tyan 815t motherboard 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-19 18:38 ` Bruce Harada
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 [this message]
2001-09-24 15:14 ` bill davidsen
2001-09-24 18:18 ` 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=3BA8F5FC.BFDF5126@candelatech.com \
--to=greearb@candelatech.com \
--cc=bruce@ask.ne.jp \
--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