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@xxxxxxxxxxxxxx
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
