From: Ben Greear <greearb@candelatech.com>
To: jamal <hadi@cyberus.ca>
Cc: Andre Hedrick <andre@pyxtechnologies.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
"'netdev@oss.sgi.com'" <netdev@oss.sgi.com>
Subject: Re: Update on e1000 troubles (over-heating!)
Date: Sun, 06 Oct 2002 20:46:42 -0700 [thread overview]
Message-ID: <3DA103A2.1060901@candelatech.com> (raw)
In-Reply-To: Pine.GSO.4.30.0210061835350.1861-100000@shell.cyberus.ca
jamal wrote:
> It seems like the prerequisite to reproduce it is you beat the NIC heavily
> with a lot of packets/sec and then run it at that sustained rate for at
> least 30 minutes. isci would tend to use MTU sized packets which will
> not be that effective.
I can reproduce my crash using mtu sized pkts running only 50Mbps send + receive
on 2 nics. It took over-night to do it though. Running as hard as I can with
MTU packets will crash it as well, and much quicker.
Interestingly enough, the tg3 NIC (netgear 302t), registered 57 deg C between
the fins of it's heat sink in the 32-bit slots. Makes me wonder if my PCI bus
is running too hot :P
Dave says I'm wierd and no one else sees these bizarre problems, btw :)
More trouble-shooting to follow this next week.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com> <Ben_Greear AT 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:[~2002-10-07 3:41 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-06 3:38 Update on e1000 troubles (over-heating!) Ben Greear
2002-10-06 3:47 ` Andre Hedrick
2002-10-06 22:38 ` jamal
2002-10-07 0:14 ` Andre Hedrick
2002-10-07 11:56 ` jamal
2002-10-09 1:10 ` Update on e1000 troubles (over-heating!) (problem solved) Ben Greear
2002-10-07 3:46 ` Ben Greear [this message]
2002-10-07 5:26 ` Update on e1000 troubles (over-heating!) David S. Miller
2002-10-07 11:53 ` jamal
2002-10-07 11:58 ` David S. Miller
2002-10-07 16:40 ` Ben Greear
2002-10-07 18:11 ` How can we bound one CPU to one Gigabit NIC? Xiaoliang (David) Wei
2002-10-07 18:24 ` Ben Greear
2002-10-07 19:12 ` Xiaoliang (David) Wei
2002-10-08 7:27 ` Xiaoliang (David) Wei
2002-10-08 8:57 ` jamal
2002-10-08 17:41 ` Jason Lunz
2002-10-10 2:22 ` jamal
2002-10-10 2:24 ` jamal
-- strict thread matches above, loose matches on Subject: below --
2002-10-06 7:33 Update on e1000 troubles (over-heating!) Feldman, Scott
2002-10-08 18:44 ` Ben Greear
2002-10-15 2:20 Feldman, Scott
2002-10-15 2:37 ` Andi Kleen
2002-10-15 2:54 ` Jonathan Lundell
2002-10-15 5:42 ` Dave Hansen
2002-10-15 7:07 ` Ben Greear
2002-10-15 7:01 ` 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=3DA103A2.1060901@candelatech.com \
--to=greearb@candelatech.com \
--cc=andre@pyxtechnologies.com \
--cc=hadi@cyberus.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.