linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: "Feldman, Scott" <scott.feldman@intel.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	"'netdev@oss.sgi.com'" <netdev@oss.sgi.com>
Subject: Re: Update on e1000 troubles (over-heating!)
Date: Tue, 15 Oct 2002 00:01:14 -0700	[thread overview]
Message-ID: <3DABBD3A.2000901@candelatech.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?

The fan did help, and Andi is right, the chip was much hotter than what
my probe read (I was gently pushing it against the top of the chip, cause it
was too hot to really press my finger against it to get good contact :))

With the fan blowing on the chips, it has been perfect.  This implies to me
that if you are going to run the e1000, you need significant air-flow over
the chipset, and the generic 2U chassis that I have is definately inadequate,
partially because the MB is so big that the fans are too far away from the
PCI slots...  This is all doubly true if you are running two NICs side-by-side,
which is what I was doing.

I am also considering glueing heat-sinks onto the main chip, which may make it
work in more marginal environments.

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



  parent reply	other threads:[~2002-10-15  6:56 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
2002-10-15  7:07   ` Ben Greear
2002-10-15  7:01 ` Ben Greear [this message]
  -- 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=3DABBD3A.2000901@candelatech.com \
    --to=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 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).