From: mds@mds.gotdns.com (Mark Studebaker)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] lm87 alarm threshold changed mysteriously
Date: Fri, 01 Jul 2005 04:59:20 +0000 [thread overview]
Message-ID: <42C4B15A.7080306@mds.gotdns.com> (raw)
In-Reply-To: <84ab3f2e05063006542885c7e6@mail.gmail.com>
I don't see anything in CHANGES or the CVS log that sounds like it would fix this.
Strange since I assume there are no writes happening to any registers in normal operation, just reads for monitoring.
Could be noise on the I2C bus or even cosmic rays that flipped a bit in the LM87.
The server wasn't in Denver, was it (high altitude)?
Sorry no great ideas on how to answer 2-4.
Hope it doesn't happen again...
mds
David Knierim wrote:
> We have a product based on the Intel E7501 chipset which uses two LM87
> sensor chips and the i2c-i801 bus driver. We have fielded several
> hundred of these boxes over the past two years. They are all running
> Red Hat 9 with the version of sensors that came with it (the rpm
> version is 2.6.5-5). Yes, I know this an ancient release...
>
> I got a call yesterday that one of the boxes had started getting
> voltage alarms. After some investigation, I determined the problem
> was that the low voltage alarm threshold for the +V2.5 power plane had
> changed to 3.32V (from the normal value of 2.37V. The high voltage
> threshold had not changed for the normal setting of 2.61V. The
> measured voltage of 2.48V looked fine, too.
>
> After running sensors -s, the problem went away (as I expected it to).
>
> So I have a bunch of questions:
> 1 - is it likely that this problem would be fixed in a newer release
> of lm_sensors?
> 2 - if it's not fixed, how would one track down the problem so we could fix it?
> 3 - is it possible this is a hardware problem?
> 4 - Any thoughs on recovering from problem in a more automated fashion
> until a fix is found?
>
> Any thoughts are welcome.
>
> David
>
> _______________________________________________
> lm-sensors mailing list
> lm-sensors@lm-sensors.org
> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2005-07-01 4:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-30 15:55 [lm-sensors] lm87 alarm threshold changed mysteriously David Knierim
2005-07-01 4:59 ` Mark Studebaker [this message]
2005-07-01 20:46 ` Jean Delvare
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=42C4B15A.7080306@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.