From: mds@mds.gotdns.com (Mark Studebaker)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] W83792D & Overtemperature LED on Supermicro
Date: Fri, 01 Jul 2005 02:33:55 +0000 [thread overview]
Message-ID: <42C48F47.5030503@mds.gotdns.com> (raw)
In-Reply-To: <1120167411.32695.31.camel@wiz.dev.aspsys.com>
you want hyst (hysteresis) to be high, like 68.
The alarm isn't cleared until the temperature goes below the hysteresis value.
Eric J. Bowersox wrote:
> (Sorry about the blank message, let's try it again...)
>
> Greetings to all.
>
> We've got some compute nodes here that are using Supermicro X6DHR
> motherboards (for the Intel Nocona processors), which use the Winbond
> W83792D hardware monitor chip. Since the OS installed on these is SuSE
> Linux Enterprise Server 9 (kernel 2.6.5), I had to upgrade lm_sensors to
> 2.9.1 and apply a kernel patch (the one recently posted to this list) to
> get the right chip driver into the system. I'm able to get temperature,
> fan, and voltage readings out of the chip, so it's all good there.
>
> However, another strange issue has cropped up: during the system boot
> process, as soon as the "sensors" service loads, the "overtemperature"
> LED on the front panel begins flashing. I've tried mucking around with
> the "set tempN_over" and "set tempN_hyst" lines in sensors.conf, but to
> no avail; the last settings I tried were 70 for over and 30 for hyst,
> and the light still blinks. Naturally, if we ship the nodes like this,
> the customer might get worried, seeing all those blinking red lights.
>
> So, anybody have any ideas, short of taking a pair of diagonal cutters
> to the leads for the temperature light? Is that light somehow connected
> to one of the outputs of the W83792D, and if so, is there some kind of
> "magic poke" I can make to the chip registers to get it to quit
> flashing? (Maybe this is a driver issue?) Or have I just not been
> aggressive enough in how I changed the temperature bounds in
> sensors.conf?
>
> Thanks in advance.
>
next prev parent reply other threads:[~2005-07-01 2:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-30 23:37 [lm-sensors] W83792D & Overtemperature LED on Supermicro Eric J. Bowersox
2005-06-30 23:51 ` Eric J. Bowersox
2005-07-01 2:33 ` Mark Studebaker [this message]
2005-07-01 17:44 ` Eric J. Bowersox
2005-07-02 18:37 ` Rudolf Marek
2005-07-06 17:41 ` Eric J. Bowersox
2005-07-07 21:19 ` Jean Delvare
2005-07-07 21:26 ` Jean Delvare
2005-07-07 22:11 ` Rudolf Marek
2005-07-08 0:22 ` Eric J. Bowersox
2005-07-08 9:42 ` Rudolf Marek
2005-07-08 12:28 ` Rudolf Marek
2005-07-08 18:19 ` Eric J. Bowersox
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=42C48F47.5030503@mds.gotdns.com \
--to=mds@mds.gotdns.com \
--cc=lm-sensors@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 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.