sensor has a short memory

[ticket]

sensor command seems to forget my settings for the max and hyst temperature settings

[root@desk ~]# sensors
w83697hf-isa-0290
Adapter: ISA adapter
VCore:       +1.86 V  (min =  +1.71 V, max =  +1.89 V)
+3.3V:       +3.31 V  (min =  +3.14 V, max =  +3.47 V)
+5V:         +5.05 V  (min =  +4.76 V, max =  +5.24 V)
+12V:       +11.98 V  (min = +10.82 V, max = +13.19 V)
V5SB:        +5.43 V  (min =  +4.76 V, max =  +5.24 V)
VBat:        +3.25 V  (min =  +2.40 V, max =  +3.60 V)
fan1:       4821 RPM  (min = 2500 RPM, div = 4)
M/B Temp:    +30.0°C  (high = +40.0°C, hyst = +37.0°C)  sensor = thermistor
CPU Temp:    +46.0°C  (high =  -1.0°C, hyst =  -1.0°C)  sensor = thermistor
beep_enable:enabled

[root@desk ~]# sensors -s
[root@desk ~]# sensors
w83697hf-isa-0290
Adapter: ISA adapter
VCore:       +1.89 V  (min =  +1.71 V, max =  +1.89 V)
+3.3V:       +3.31 V  (min =  +3.14 V, max =  +3.47 V)
+5V:         +5.08 V  (min =  +4.76 V, max =  +5.24 V)
+12V:       +11.92 V  (min = +10.82 V, max = +13.19 V)
V5SB:        +5.43 V  (min =  +4.76 V, max =  +5.24 V)
VBat:        +3.25 V  (min =  +2.40 V, max =  +3.60 V)
fan1:       4821 RPM  (min = 2500 RPM, div = 4)
M/B Temp:    +30.0°C  (high = +40.0°C, hyst = +37.0°C)  sensor = thermistor
CPU Temp:    +46.0°C  (high = +65.0°C, hyst = +60.0°C)  sensor = thermistor
beep_enable:enabled

[root@desk ~]# sleep 60 && sensors
w83697hf-isa-0290
Adapter: ISA adapter
VCore:       +1.86 V  (min =  +1.71 V, max =  +1.89 V)
+3.3V:       +3.33 V  (min =  +3.14 V, max =  +3.47 V)
+5V:         +5.08 V  (min =  +4.76 V, max =  +5.24 V)
+12V:       +11.92 V  (min = +10.82 V, max = +13.19 V)
V5SB:        +5.43 V  (min =  +4.76 V, max =  +5.24 V)
VBat:        +3.25 V  (min =  +2.40 V, max =  +3.60 V)
fan1:       4821 RPM  (min = 2500 RPM, div = 4)
M/B Temp:    +30.0°C  (high = +40.0°C, hyst = +37.0°C)  sensor = thermistor
CPU Temp:    +46.0°C  (high =  -1.0°C, hyst =  -1.0°C)  sensor = thermistor
beep_enable:enabled

[root@desk ~]#   

sri to keep pestering you.

v

[ticket]

oops, component is not fancontrol v

[khali]

What kernel version is this? This is most probably a driver or hardware issue, not a user-space bug.

To prove this, please try writing to the sysfs interface directly:

# cd /sys/class/hwmon/hwmon0/device # cat temp2_max # echo 50000 > temp2_max # cat temp2_max # sleep 3 # cat temp2_max

If the last cat returns -1000 instead of the expected 50000 then this is a kernel or hardware issue.

[ticket]

1. would it help you if I migrate to the SVN version? Since you have been so helpful and responsive, I would be glad to.

Here is what i got from your test...

[root@desk device]# cat temp2_max
-1000
[root@desk device]# echo 5000 > temp2_max
[root@desk device]# sleep 60
cat temp2_max
[root@desk device]# cat temp2_max
-1000
[root@desk device]# echo 5000 > temp2_max
[root@desk device]# sleep 6
[root@desk device]# cat temp2_max
5000
[root@desk device]# sleep 6
[root@desk device]# cat temp2_max
5000
[root@desk device]# sleep 6
[root@desk device]# cat temp2_max
-1000
[root@desk device]#     

If this is a kernel problem, I'm in trouble, since fedora core 6 is at end of life. Putting in a new kernel can be exceedingly tedious.

v

[khali]

Upgrading to SVN wouldn't help as this is definitely not a user-space issue. For your previous comment, it is either a driver issue or a hardware issue. Or a conflict with ACPI or your BIOS.

The w83627hf driver caches its data for 1.5 second. If the problem was that the register values were not written successfully then you'd get -1.0°C again after 1.5 second, while it seems to take about 15 seconds in your case. I suspect that something else is accessing the chip and this is causing trouble.

What motherboard is this? Is it advertised to do any kind of automatic fan speed control or thermal regulation?

You still did not tell me your kernel version.

If you load the "thermal" driver so you see anything under /proc/acpi/thermal_zone?

[khali]

No answer for 3 months -> closing. Please reopen if you can answer my questions.

Note that this could still be a user-space issue, if some 3rd party monitoring application insists on writing arbitrary limits to the chip every 15 seconds. That would be pretty stupid though and thus very unlikely.