[lm-sensors] ridicolous sensors output?

[lm-sensors] ridicolous sensors output?

[Roy Sigurd Karlsbakk]

hi all

running 'sensors' on this new 1U asus server, gives me quite  
interesting data. this is on a server that's been running three weeks  
or so without problems. attached is lspci -vvv output and  
sensors.conf (standard from debian sarge).

can someone please help me figure out what's happening here?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: sensors.conf.gz
Type: application/x-gzip
Size: 18675 bytes
Desc: not available
Url : http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20060416/e36e63b5/sensors.conf-0001.gz
-------------- next part --------------
A non-text attachment was scrubbed...
Name: lspci-vvv.txt.gz
Type: application/x-gzip
Size: 1854 bytes
Desc: not available
Url : http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20060416/e36e63b5/lspci-vvv.txt-0001.gz
-------------- next part --------------

thanks

roy

# sensors
w83627thf-isa-0290
Adapter: ISA adapter
VCore:     +1.94 V  (min =  +0.70 V, max =  +1.87 V)       ALARM
+12V:      +7.36 V  (min =  +0.30 V, max =  +7.78 V)
+3.3V:     +1.44 V  (min =  +0.21 V, max =  +0.77 V)       ALARM
+5V:       +5.01 V  (min =  +0.00 V, max =  +0.77 V)       ALARM
-12V:      +6.06 V  (min = -10.96 V, max = -12.28 V)       ALARM
V5SB:      +5.03 V  (min =  +1.51 V, max =  +0.38 V)       ALARM
VBat:      +0.11 V  (min =  +0.00 V, max =  +2.82 V)
fan1:        0 RPM  (min = 5232 RPM, div = 2)              ALARM
CPU Fan:     0 RPM  (min = 675000 RPM, div = 2)              ALARM
fan3:        0 RPM  (min = 9926 RPM, div = 2)              ALARM
M/B Temp:    -48 C  (high =    +4 C, hyst =    +0 C)   sensor =  
thermistor
CPU Temp:  -48.0 C  (high =   +80 C, hyst =   +75 C)   sensor =  
thermistor
temp3:     -48.0 C  (high =   +80 C, hyst =   +75 C)   sensor =  
thermistor
alarms:   Chassis intrusion detection                      ALARM
beep_enable:
           Sound alarm enabled

--
Roy Sigurd Karlsbakk
roy at karlsbakk.net
---
In space, loud sounds, like explosions, are even louder because there  
is no air to get in the way.

[lm-sensors] ridicolous sensors output?

[Jean Delvare]

Hi Roy,

> running 'sensors' on this new 1U asus server, gives me quite  
> interesting data. this is on a server that's been running three weeks  
> or so without problems. attached is lspci -vvv output and  
> sensors.conf (standard from debian sarge).

Please:
* Don't compress files you send on the list. You shouldn't expect
people to take the time to save and gunzip the file to look at the
data. People are always busy.
* Don't send sensors.conf in its entirety when only a small part of it
is relevant for your configuration.

> can someone please help me figure out what's happening here?

My first guess is that this W83627THF chip is not used for hardware
monitoring on your board. You probably have another chip for that.

Please provide the following information:
* Kernel version.
* Version of lm_sensors.
* Server model.
* Full output of sensors-detect.

-- 
Jean Delvare

[lm-sensors] ridicolous sensors output?

[Roy Sigurd Karlsbakk]

> Please:
> * Don't compress files you send on the list. You shouldn't expect
> people to take the time to save and gunzip the file to look at the
> data. People are always busy.
>
> * Don't send sensors.conf in its entirety when only a small part of it
> is relevant for your configuration.

ok. sorry.

>> can someone please help me figure out what's happening here?
>
> My first guess is that this W83627THF chip is not used for hardware
> monitoring on your board. You probably have another chip for that.
>
> Please provide the following information:
> * Kernel version.

2.6.16.2 custom built

> * Version of lm_sensors.

sensors version 2.9.1 with libsensors version 2.9.1

> * Server model.

Asus AP140R

> * Full output of sensors-detect.

attached below


thanks

roy
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: sensorslogstuff.txt
Url: http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20060416/247204ae/sensorslogstuff.txt
-------------- next part --------------

--
Roy Sigurd Karlsbakk
roy at karlsbakk.net
---
In space, loud sounds, like explosions, are even louder because there  
is no air to get in the way.

[lm-sensors] ridicolous sensors output?

[Jean Delvare]

Roy,

> > My first guess is that this W83627THF chip is not used for hardware
> > monitoring on your board. You probably have another chip for that.
> >
> > Please provide the following information:
> > * Kernel version.
> 
> 2.6.16.2 custom built
> 
> > * Version of lm_sensors.
> 
> sensors version 2.9.1 with libsensors version 2.9.1

That's a bit old, see below.

> Next adapter: SMBus I801 adapter at 0500
> (...)
> Client found at address 0x2f
> (...)
> Probing for `Winbond W83792D'... Success!
>     (confidence 7, driver `to-be-written'), other addresses: 0x4b 0x4f

OK, that's your hardware monitoring chip. sensors-detect thinks there
is no driver for it, but by now, there is. Try:
  rmmod w83627hf
  modprobe i2c-i801
  modprobe w83792d
And sensors output should be better.

However, user-space support for that chip was just added in lm_sensors
2.9.1 and many bugs have been fixed since, so you are invited to update
lm_sensors to a later version for better results.

-- 
Jean Delvare

[lm-sensors] ridicolous sensors output?

[Roy Sigurd Karlsbakk]

>> Next adapter: SMBus I801 adapter at 0500
>> (...)
>> Client found at address 0x2f
>> (...)
>> Probing for `Winbond W83792D'... Success!
>>     (confidence 7, driver `to-be-written'), other addresses: 0x4b  
>> 0x4f
>
> OK, that's your hardware monitoring chip. sensors-detect thinks there
> is no driver for it, but by now, there is. Try:
>   rmmod w83627hf
>   modprobe i2c-i801
>   modprobe w83792d
> And sensors output should be better.
>
> However, user-space support for that chip was just added in lm_sensors
> 2.9.1 and many bugs have been fixed since, so you are invited to  
> update
> lm_sensors to a later version for better results.

works like a dream :)

only, see below, I can't get fan6 data. can this be due to some other  
error? Also, temp2 shows ALARM where the data looks ok, and temp3 is  
still -48.5 degrees, and, beleive me, it's not that cold :)

# sensors
w83792d-i2c-0-2f
Adapter: SMBus I801 adapter at 0500
VCoreA:    +1.34 V  (min =  +0.00 V, max =  +2.04 V)
VCoreB:    +1.37 V  (min =  +0.00 V, max =  +2.04 V)
VIN0:      +3.38 V  (min =  +0.00 V, max =  +4.08 V)
VIN1:      +3.11 V  (min =  +0.00 V, max =  +4.08 V)
VIN2:      +1.53 V  (min =  +0.00 V, max =  +4.08 V)
VIN3:      +2.60 V  (min =  +0.00 V, max =  +4.08 V)
5VCC:      +5.07 V  (min =  +0.00 V, max =  +6.12 V)
5VSB:      +5.03 V  (min =  +0.00 V, max =  +6.12 V)
VBAT:      +3.20 V  (min =  +0.00 V, max =  +4.08 V)
Fan1:     9507 RPM  (min =    0 RPM, div = 2)
Fan2:     9642 RPM  (min =    0 RPM, div = 2)
Fan3:     6553 RPM  (min =    0 RPM, div = 2)
Fan4:     6887 RPM  (min =    0 RPM, div = 2)
Fan5:     9000 RPM  (min =    0 RPM, div = 2)
ERROR: Can't get FAN6 data!
Fan7:     9246 RPM  (min =    0 RPM, div = 2)
Temp1:     +40.0 C  (high = +127.0 C, hyst =  +0.0 C)
Temp2:     +36.5 C  (high = +80.0 C, hyst = +75.0 C)   ALARM
Temp3:     -48.5 C  (high = +80.0 C, hyst = +75.0 C)   ALARM
chassis:  Chassis intrusion detection                  ALARM

again thanks a lot

roy
--
Roy Sigurd Karlsbakk
roy at karlsbakk.net
---
In space, loud sounds, like explosions, are even louder because there  
is no air to get in the way.

[lm-sensors] ridicolous sensors output?

[Jean Delvare]

> works like a dream :)
> 
> only, see below, I can't get fan6 data. can this be due to some other  
> error? Also, temp2 shows ALARM where the data looks ok, and temp3 is  
> still -48.5 degrees, and, beleive me, it's not that cold :)
> 
> # sensors
> w83792d-i2c-0-2f
> Adapter: SMBus I801 adapter at 0500
> VCoreA:    +1.34 V  (min =  +0.00 V, max =  +2.04 V)
> VCoreB:    +1.37 V  (min =  +0.00 V, max =  +2.04 V)
> VIN0:      +3.38 V  (min =  +0.00 V, max =  +4.08 V)
> VIN1:      +3.11 V  (min =  +0.00 V, max =  +4.08 V)
> VIN2:      +1.53 V  (min =  +0.00 V, max =  +4.08 V)
> VIN3:      +2.60 V  (min =  +0.00 V, max =  +4.08 V)
> 5VCC:      +5.07 V  (min =  +0.00 V, max =  +6.12 V)
> 5VSB:      +5.03 V  (min =  +0.00 V, max =  +6.12 V)
> VBAT:      +3.20 V  (min =  +0.00 V, max =  +4.08 V)
> Fan1:     9507 RPM  (min =    0 RPM, div = 2)
> Fan2:     9642 RPM  (min =    0 RPM, div = 2)
> Fan3:     6553 RPM  (min =    0 RPM, div = 2)
> Fan4:     6887 RPM  (min =    0 RPM, div = 2)
> Fan5:     9000 RPM  (min =    0 RPM, div = 2)
> ERROR: Can't get FAN6 data!

Some pins of the W83792D chip can be used for different purposes. In
your case, the fan6 pin is indeed used for something different so the
w83792d kernel driver did not create an interface for that fan.
"sensors" should ignore missing interface files in this case, but the
version you have did not. This was fixed in CVS recently.

You may try to add an "ignore fan6" statement in your configuration
file.

> Fan7:     9246 RPM  (min =    0 RPM, div = 2)
> Temp1:     +40.0 C  (high = +127.0 C, hyst =  +0.0 C)
> Temp2:     +36.5 C  (high = +80.0 C, hyst = +75.0 C)   ALARM

Looks like a known bug, fixed in lm_sensors 2.9.2.

> Temp3:     -48.5 C  (high = +80.0 C, hyst = +75.0 C)   ALARM

-48 degrees C is a typical value for unconnected thermal sensors. You
can probably just ignore that input ("ignore temp3").

> chassis:  Chassis intrusion detection                  ALARM

-- 
Jean Delvare

[lm-sensors] ridicolous sensors output?

[Roy Sigurd Karlsbakk]

>> ERROR: Can't get FAN6 data!
>
> Some pins of the W83792D chip can be used for different purposes. In
> your case, the fan6 pin is indeed used for something different so the
> w83792d kernel driver did not create an interface for that fan.
> "sensors" should ignore missing interface files in this case, but the
> version you have did not. This was fixed in CVS recently.
>
> You may try to add an "ignore fan6" statement in your configuration
> file.

didn't help. it still seems to probe it.

>> Fan7:     9246 RPM  (min =    0 RPM, div = 2)
>> Temp1:     +40.0 C  (high = +127.0 C, hyst =  +0.0 C)
>> Temp2:     +36.5 C  (high = +80.0 C, hyst = +75.0 C)   ALARM
>
> Looks like a known bug, fixed in lm_sensors 2.9.2.

indeed. cvs version works well here.

>> Temp3:     -48.5 C  (high = +80.0 C, hyst = +75.0 C)   ALARM
>
> -48 degrees C is a typical value for unconnected thermal sensors. You
> can probably just ignore that input ("ignore temp3").

just did that, so that's ok as well.

thanks

roy

--
Roy Sigurd Karlsbakk
roy at karlsbakk.net
---
In space, loud sounds, like explosions, are even louder because there  
is no air to get in the way.

[lm-sensors] ridicolous sensors output?

[Yuan Mu]

Roy Sigurd Karlsbakk wrote:
>>> ERROR: Can't get FAN6 data!
>> Some pins of the W83792D chip can be used for different purposes. In
>> your case, the fan6 pin is indeed used for something different so the
>> w83792d kernel driver did not create an interface for that fan.
>> "sensors" should ignore missing interface files in this case, but the
>> version you have did not. This was fixed in CVS recently.
>>
>> You may try to add an "ignore fan6" statement in your configuration
>> file.
> 
> didn't help. it still seems to probe it.
> 
Are you sure...
Are you find " chip "w83792d-*" " and add ignore fan6 below it?

Or you may try download the lm_sensors2 nightly cvs snapshots and install the userspace tools,
http://secure.netroedge.com/~lm78/archive/lm_sensors-daily.tar.gz
I think this warning has been removed in the cvs.


Best Regards
Yuan Mu


=============================================The privileged confidential information contained in this email is intended for use only by the addressees as indicated by the original sender of this email. If you are not the addressee indicated in this email or are not responsible for delivery of the email to such  a person, please kindly reply to the sender indicating this fact and delete all copies of it from your computer and network server immediately. Your cooperation is highly appreciated. It is advised that any unauthorized use of confidential information of Winbond is strictly prohibited; and any information in this email irrelevant to the official business of Winbond shall be deemed as neither given nor endorsed by Winbond.