All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Hansen <haveblue@us.ibm.com>
To: "Feldman, Scott" <scott.feldman@intel.com>
Cc: "'Ben Greear'" <greearb@candelatech.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, 14 Oct 2002 22:42:38 -0700	[thread overview]
Message-ID: <3DABAACE.9040706@us.ibm.com> (raw)
In-Reply-To: 288F9BF66CD9D5118DF400508B68C44604758B78@orsmsx113.jf.intel.com

Feldman, Scott wrote:
>>Here is the lspci information, both -x and -vv.  This is with 
>>two of the e1000 single-port NICS side-by-side.  I have also 
>>strapped a P-IV CPU fan on top of the two cards to blow some 
>>air over them....running tests now to see if that actually 
>>helps anything.  If it does, I'll be sure to send you a picture :)
> 
> Ben, I checked the datasheet for the part shown in the lspci dump, and it
> shows an operating temperature of 0-55 degrees C.  You said you measured 50
> degrees C, so you're within the safe range.  Did the fans help?
> 
> Here's the datasheet:
> http://www.intel.com/network/connectivity/resources/doc_library/data_sheets/
> pro1000mt_sa.pdf

I get some strange e1000 failures too.  It usually involves the 
watchdog kicking them back into order, but sometimes they'll stay 
offline for a while.  Heat would explain it, though, because it only 
happens when I'm actually using the cards for a benchmark.  I figured 
that it was either my cables, or a shoddy switch.

The new dual-port e1000 that I have doesn't seem to have this problem, 
even though I'm running 4 times more traffic than the singles that I 
had.
-- 
Dave Hansen
haveblue@us.ibm.com


  parent reply	other threads:[~2002-10-15  5:37 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-15  2:20 Update on e1000 troubles (over-heating!) Feldman, Scott
2002-10-15  2:37 ` Andi Kleen
2002-10-15  2:54   ` Jonathan Lundell
2002-10-15  5:42 ` Dave Hansen [this message]
2002-10-15  7:07   ` Ben Greear
2002-10-15  7:01 ` Ben Greear
  -- strict thread matches above, loose matches on Subject: below --
2002-10-06  7:33 Feldman, Scott
2002-10-08 18:44 ` Ben Greear
2002-10-06  3:38 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

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=3DABAACE.9040706@us.ibm.com \
    --to=haveblue@us.ibm.com \
    --cc=greearb@candelatech.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@oss.sgi.com \
    --cc=scott.feldman@intel.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.