From: Ben Hutchings <bhutchings@solarflare.com>
To: Jesper Dangaard Brouer <hawk@comx.dk>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: Driver SFC: Possible bug in LM87 temperature XFP detection code
Date: Tue, 28 Apr 2009 18:04:18 +0100 [thread overview]
Message-ID: <1240938258.3200.28.camel@achroite> (raw)
In-Reply-To: <1240925799.3200.16.camel@achroite>
I wrote:
> However, I
> think your time might be better spent in fixing the air flow in the
> computer before the board is permanently damaged.
It may also be worth checking that the sensors are actually reading
correctly. You can read them using the "sensors" command from the
lm_sensors package or by running:
grep . /sys/class/net/eth88/device/i2c-adapter:*/*-002e/temp*_input
Divide the numbers by 1000 to get temperatures in degrees celsius.
The "internal" temperature sensor (temp1_input) is in the LM87, which is
placed at the corner of the board away from the bracket and the edge
connector.
The "external" temperature sensor (temp2_input) is in the SFC4000.
Ben.
--
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
next prev parent reply other threads:[~2009-04-28 17:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-28 9:36 Driver SFC: Possible bug in LM87 temperature XFP detection code Jesper Dangaard Brouer
2009-04-28 13:36 ` Ben Hutchings
2009-04-28 14:44 ` Jesper Dangaard Brouer
2009-04-28 14:48 ` [PATCH] sfc: Make temperature warnings/alarms more explicit Jesper Dangaard Brouer
2009-04-30 0:50 ` David Miller
2009-04-30 1:25 ` Ben Hutchings
2009-04-30 8:44 ` Jesper Dangaard Brouer
2009-04-28 17:04 ` Ben Hutchings [this message]
2009-04-29 8:52 ` Driver SFC: Possible bug in LM87 temperature XFP detection code Jesper Dangaard Brouer
2009-04-29 12:11 ` Jesper Dangaard Brouer
2009-04-29 12:47 ` Ben Hutchings
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=1240938258.3200.28.camel@achroite \
--to=bhutchings@solarflare.com \
--cc=hawk@comx.dk \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).