From: Hans de Goede <hdegoede@redhat.com>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] f71889ed temp alarm polarity reversed.
Date: Sun, 24 Apr 2011 14:57:12 +0000 [thread overview]
Message-ID: <4DB43A48.1050802@redhat.com> (raw)
In-Reply-To: <m3wrikmw1g.fsf@jhcloos.com>
Hi,
On 04/24/2011 12:39 AM, James Cloos wrote:
> As of Linus' v2.6.39-rc4-89-g2f666bc I still get:
>
> fan1: 871 RPM
> fan2: 0 RPM ALARM
> fan3: 0 RPM ALARM
> temp1: +35.0°C (high = +255.0°C, hyst = +251.0°C) ALARM (CRIT)
> (crit = +255.0°C, hyst = +251.0°C) sensor = transistor
> temp2: FAULT (high = +255.0°C, hyst = +251.0°C)
> (crit = +255.0°C, hyst = +251.0°C) sensor = transistor
> temp3: +38.0°C (high = +255.0°C, hyst = +253.0°C) ALARM (CRIT)
> (crit = +255.0°C, hyst = +253.0°C) sensor = transistor
>
> The polarity for the fan alarms is correct, but it is reversed for the
> temp alarms.
I just checked the data sheet and it disagrees with your observation. It is
possible that the temp has been outside alarm boundaries before they
were set to their current settings, and the alarm register has never
been read before. Try running the sensors command again (after waiting
a couple of seconds otherwise you will get cached readings).
Or maybe the problem is that 255 gets seen as -1 ? The F71889ED does
have signed values in certain temp registers (but not the alarm thresholds
according to the datasheet). Try writing 100 to the temp#_max and
temp#_crit sysfs attributes, you can find these files under
/sys/class/hwmon#, or /sys/class/hwmon#/device.
Regards,
Hans
_______________________________________________
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-04-24 14:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-23 22:39 [lm-sensors] f71889ed temp alarm polarity reversed James Cloos
2011-04-24 14:57 ` Hans de Goede [this message]
2011-04-24 15:14 ` Jean Delvare
2011-04-27 17:31 ` James Cloos
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=4DB43A48.1050802@redhat.com \
--to=hdegoede@redhat.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.