linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Mon, 07 Oct 2002 09:40:13 -0700	[thread overview]
Message-ID: <3DA1B8ED.2000309@candelatech.com> (raw)
In-Reply-To: Pine.GSO.4.30.0210070749430.1861-100000@shell.cyberus.ca

jamal wrote:
> 
> On Sun, 6 Oct 2002, Ben Greear wrote:
> 
> 
>>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.
>>
> 
> 
> So is there a correlation with packet count then?

No, running at slower speeds (50Mbps), the packet count was well over
4 billion (ie it successfully wrapped 32-bits).  At higher speeds, it
crashes before the 32-bit wrap, generally.  It also does not coorelate
to bytes-sent/received, or anything else that I could think of to look at.

> 
> 
> 
>>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
> 
> 
> Does the problem happen with the tg3?

As Dave mentioned, tg3 locks up almost immediately (like within 30 seconds),
and in the meantime, it's spitting out errors that are 'impossible'.  The
messages I sent a day or two ago.

I may have cooked my cards, or something like that, because one of
the tg3's do not work in my other machine now.  Still trouble-shooting that one.

Ben


> 
> cheers,
> jamal
> 
> 


-- 
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



  parent reply	other threads:[~2002-10-07 16:35 UTC|newest]

Thread overview: 18+ 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-07  3:46     ` Ben Greear
2002-10-07  5:26       ` David S. Miller
2002-10-07 11:53       ` jamal
2002-10-07 11:58         ` David S. Miller
2002-10-07 16:40         ` Ben Greear [this message]
2002-10-06  7:33 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=3DA1B8ED.2000309@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).