Error getting sensor data: w83627ehf/#34

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello Jean,

thank you for your detailed explanation. The problem seemed to be fan4
indeed. I updated lm-sensors to 3.0.2 though it is still marked as
unstable (and hard-masked because barely any applications can deal with
it) in Gentoo. But now sensord starts without complaints and the fan4 is
automatically non-existent. But still the values reported by lm-sensors
seem bogus. Especially +5V and temperatures values:

w83627ehf-isa-0290
Adapter: ISA adapter
VCore:       +1.59 V  (min =  +0.00 V, max =  +1.85 V)
+12V:       +12.04 V  (min = +10.82 V, max = +13.20 V)
AVCC:        +3.38 V  (min =  +3.14 V, max =  +3.47 V)
3VCC:        +3.36 V  (min =  +3.14 V, max =  +3.47 V)
+5V:         +4.30 V  (min =  +4.76 V, max =  +5.25 V)   ALARM
VSB:         +3.38 V  (min =  +3.14 V, max =  +3.47 V)
VBAT:        +3.28 V  (min =  +3.14 V, max =  +3.47 V)
CPU Fan:    2481 RPM  (min = 1704 RPM, div = 8)
Sys Temp:    +27.0?C  (high =  +0.0?C, hyst =  +0.0?C)  ALARM  sensor =
thermistor
CPU Temp:     +9.0?C  (high = +80.0?C, hyst = +75.0?C)  sensor = diode
AUX Temp:    +77.5?C  (high = +80.0?C, hyst = +75.0?C)  ALARM  sensor =
thermistor

How should I go about tweaking the temperature and voltage computations?
Should I measure the 5V lines or just fiddle about the resistor values
and pretend the raw voltage value is 5V?

What about the temperature values? The CPU temperature seems to be too
low (though the room is admittedly cooled). Unfortunately the
/proc/acpi/thermal_zone directory remains empty on this machine and I
cannot easily doublecheck the temperature. Maybe I should check the
values reported in the system BIOS...

What about the sys and aux temperatures? I seriously doubt that anything
is 77.5?C hot in that machine while idling. I guess the sys temp is a
dead input because the rrdcgi charts show a perfectly constant value of
27.0?C. Is that reasonable? Which temperature sensors do "sys temp" and
"aux temp" correspond to anyway?

Lot's of questions...
Thanks again,
Tobias



Jean Delvare wrote:
> Hallo Tobias,
> 
> On Mon, 29 Dec 2008 13:26:27 +0100, Tobias Preclik wrote:
>> Hello,
>>
>> i encountered a problem running sensord. I am running version 2.10.7 and
>> have a w83627ehf sensor chip on my P4V800D-X Asus mainboard. The kernel
>> is a Gentoo Linux kernel version 2.6.27. The syslog states the following:
>>
>> sensord started
>> Chip: w83627ehf-isa-0290
>> Adapter: ISA adapter
>>   Case Fan: 0 RPM (min = 0 RPM, div = 128)
>>   CPU Fan: 2481 RPM (min = 0 RPM, div = 4)
>>   Aux Fan: 0 RPM (min = 0 RPM, div = 128)
>> Error getting sensor data: w83627ehf/#34: Can't access procfs/sysfs file
>> sensord failed (23)
>>
>> As I understand it I am supposed to add "#34" to the ignore list in the
>> corresponding chip section in /etc/sensors.conf. However this does not
>> fix the problem. The sensors tool does not complain btw:
> 
> This #34 is the libsensors feature number for the feature which is
> causing trouble. You can't use it in sensors.conf, as sensors.conf
> wants feature names, not numbers. From lib/chips.h:
> 
> #define SENSORS_W83627EHF_FAN4		34 /* R  */
> 
> So the problem is with fan4. If you want to ignore something, that
> would be fan4. I am not certain whether this is enough to make sensord
> happy though. Try adding:
> 
>    ignore fan4
> 
> to the w83627ehf configuration section and see if it helps.
> 
> The cause of the problem is that the w83627ehf driver in Linux 2.6
> hides some inputs when the chip is configured to use the pins in
> question for other functions. The idea is to make the configuration
> easier. sensord in lm-sensors 2 isn't smart enough to cope with
> possibly missing inputs though, thus the error.
> 
>> w83627ehf-isa-0290
>> Adapter: ISA adapter
>> VCore:     +1.59 V  (min =  +0.00 V, max =  +1.85 V)
>> in1:      +12.04 V  (min =  +1.80 V, max =  +0.00 V) ALARM
>> AVCC:      +3.38 V  (min =  +0.00 V, max =  +0.00 V) ALARM
>> 3VCC:      +3.36 V  (min =  +0.00 V, max =  +0.00 V) ALARM
>> in4:       +1.32 V  (min =  +0.01 V, max =  +0.00 V) ALARM
>> in5:       +1.71 V  (min =  +0.26 V, max =  +0.06 V) ALARM
>> in6:       +4.28 V  (min =  +0.00 V, max =  +0.00 V) ALARM
>> VSB:       +3.38 V  (min =  +0.00 V, max =  +0.00 V) ALARM
>> VBAT:      +3.28 V  (min =  +0.00 V, max =  +0.00 V) ALARM
>> in9:       +1.26 V  (min =  +0.00 V, max =  +0.00 V) ALARM
>> Case Fan:    0 RPM  (min =    0 RPM, div = 128) ALARM
>> CPU Fan:  2463 RPM  (min =    0 RPM, div = 4) ALARM
>> Aux Fan:     0 RPM  (min =    0 RPM, div = 128) ALARM
>> fan5:        0 RPM  (min =    0 RPM, div = 128)
>> Sys Temp:    +27?C  (high =    +0?C, hyst =    +0?C)  [thermistor] ALARM
>> CPU Temp:   +9.0?C  (high = +80.0?C, hyst = +75.0?C)  [CPU diode ]
>> AUX Temp:  +77.5?C  (high = +80.0?C, hyst = +75.0?C)  [thermistor]
>>
>>
>> How can I fix this?
> 
> This is all solved in lm-sensors 3, if you can upgrade. The changes
> required are too intrusive to be ported back to lm-sensors 2.
> 


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 260 bytes
Desc: OpenPGP digital signature
Url : http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20090113/51a80e3b/attachment.bin 


[Index of Archives]     [Linux Kernel]     [Linux Hardware Monitoring]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]

  Powered by Linux