From: Guenter Roeck <guenter.roeck@ericsson.com>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] FAULT status of sensors
Date: Tue, 17 May 2011 02:32:52 +0000 [thread overview]
Message-ID: <20110517023252.GC1925@ericsson.com> (raw)
In-Reply-To: <201105162023.54718.waja@cyconet.org>
On Mon, May 16, 2011 at 02:23:44PM -0400, Jan Wagner wrote:
> Hi there,
>
> we got a bugreport[1] against our nagios-plugins package. Unfortunately we are
> unsure about what "FAULT" means.
> In case this is a hardware problem of a sensor in form of it got damaged, we
> would report "CRITICAL", as a problem occured.
> If this means there is a problem detecting the sensor or something software
> like problem, we would report "UNKNOWN" as this not means a hardware problem
> happened.
>
It is supposed to indicate a HW problem. Here is the text describing the sysfs attribute:
"Each input channel may have an associated fault file. This can be used
to notify open diodes, unconnected fans etc. where the hardware
supports it. When this boolean has value 1, the measurement for that
channel should not be trusted."
Note that "critical" in the hwmon ABI means that a critical limit has been reached.
You would get a "critical" alarm in this case. You might have a terminology problem
if you use "critical" for a hardware failure.
An undetected sensor should not show up in the first place.
Guenter
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2011-05-17 2:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-16 18:23 [lm-sensors] FAULT status of sensors Jan Wagner
2011-05-17 2:32 ` Guenter Roeck [this message]
2011-05-17 7:36 ` Jean Delvare
2011-05-17 9:33 ` Jan Wagner
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=20110517023252.GC1925@ericsson.com \
--to=guenter.roeck@ericsson.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.