Dear lm-sensors team,
I am experiencing fan reading/control problems with a Thinkstation D10
under Linux (Debian). A W83627EHG chip (visible on motherboard -
part number 816G9C28083030UB) gets recognized, but I have the
following problems:
1) RAM DIMMS get hot under heavy load, computer freezes
2) cannot read fan RPM with "sensors"
3) cannot set fan parameters (set fanX_div) with "sensors -s"
4) first loading of module w83627ehf yields message:
"Forcibly enabling Super-I/O.. Sensor is probably unusable."
The information on my system and output from my trials is included
below.
Thank you very much in advance for your help.
Linux User
System: Lenovo Thinkstation D10 (LENOVO 6427CTO)
motherboard: Lenovo (LENOVO LENOVO)
lm_sensors version: 3.1.0
kernel version: 2.6.29.1
SENSORS OUTPUT: ==================================================
w83627ehf-isa-0ca0
Adapter: ISA adapter
VCore: +1.11 V (min = +0.00 V, max = +1.74 V)
+12V: +7.92 V (min = +12.62 V, max = +13.46 V) ALARM
AVCC: +3.30 V (min = +4.08 V, max = +4.06 V) ALARM
3VCC: +3.30 V (min = +4.08 V, max = +3.06 V) ALARM
in4: +1.14 V (min = +1.98 V, max = +2.04 V) ALARM
in5: +1.60 V (min = +2.04 V, max = +1.45 V) ALARM
+5V: +4.92 V (min = +6.48 V, max = +6.53 V) ALARM
VSB: +3.30 V (min = +4.08 V, max = +4.06 V) ALARM
VBAT: +3.18 V (min = +4.08 V, max = +3.06 V) ALARM
in9: +1.12 V (min = +2.04 V, max = +2.03 V) ALARM
Case Fan: 0 RPM (min = 0 RPM, div = 128)
CPU Fan: 0 RPM (min = 0 RPM, div = 128)
Aux Fan: 0 RPM (min = 0 RPM, div = 128)
Fan 5: 0 RPM (min = 0 RPM, div = 128)
Sys Temp: +49.0?C (high = -2.0?C, hyst = -17.0?C) ALARM sensor = thermistor
CPU Temp: +46.0?C (high = +80.0?C, hyst = +75.0?C) sensor = thermistor
AUX Temp: +120.0?C (high = +80.0?C, hyst = +75.0?C) ALARM sensor = thermistor
cpu0_vid: +2.050 V
DMESG: ==================================================================
w83627ehf: Forcibly enabling Super-I/O. Sensor is probably unusable.
w83627ehf: Found W83627EHG chip at 0xca0
[later:]
w83627ehf w83627ehf.3232: Increasing fan1 clock divider from 8 to 16
w83627ehf w83627ehf.3232: Increasing fan2 clock divider from 8 to 16
w83627ehf w83627ehf.3232: Increasing fan3 clock divider from 8 to 16
w83627ehf w83627ehf.3232: Increasing fan5 clock divider from 2 to 4
w83627ehf w83627ehf.3232: Increasing fan1 clock divider from 16 to 32
w83627ehf w83627ehf.3232: Increasing fan2 clock divider from 16 to 32
w83627ehf w83627ehf.3232: Increasing fan3 clock divider from 16 to 32
w83627ehf w83627ehf.3232: Increasing fan5 clock divider from 4 to 8
w83627ehf w83627ehf.3232: Increasing fan1 clock divider from 32 to 64
w83627ehf w83627ehf.3232: Increasing fan2 clock divider from 32 to 64
w83627ehf w83627ehf.3232: Increasing fan3 clock divider from 32 to 64
w83627ehf w83627ehf.3232: Increasing fan5 clock divider from 8 to 16
w83627ehf w83627ehf.3232: Increasing fan1 clock divider from 64 to 128
w83627ehf w83627ehf.3232: Increasing fan2 clock divider from 64 to 128
w83627ehf w83627ehf.3232: Increasing fan3 clock divider from 64 to 128
w83627ehf w83627ehf.3232: Increasing fan5 clock divider from 16 to 32
w83627ehf w83627ehf.3232: Increasing fan5 clock divider from 32 to 64
w83627ehf w83627ehf.3232: Increasing fan5 clock divider from 64 to 128
SENSORS-DETECT OUTPUT: ==================================================
# sensors-detect revision 5666 (2009-02-26 17:15:04 +0100)
# System: LENOVO 6427CTO
# Board: LENOVO LENOVO
This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.
Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no):
Silicon Integrated Systems SIS5595... No
VIA VT82C686 Integrated Sensors... No
VIA VT8231 Integrated Sensors... No
AMD K8 thermal sensors... No
AMD K10 thermal sensors... No
Intel Core family thermal sensor... Success!
(driver `coretemp')
Intel AMB FB-DIMM thermal sensor... Success!
(driver `i5k_amb')
VIA C7 thermal and voltage sensors... No
Some Super I/O chips contain embedded sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no):
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Fintek'... Yes
Found `Winbond W83627EHF/EF/EHG/EG Super IO Sensors' Success!
(address 0xca0, driver `w83627ehf')
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Fintek'... No
Trying family `ITE'... No
Some systems (mainly servers) implement IPMI, a set of common interfaces
through which system health data may be retrieved, amongst other things.
We have to read from arbitrary I/O ports to probe for such interfaces.
This is normally safe. Do you want to scan for IPMI interfaces?
(YES/no):
Probing for `IPMI BMC KCS' at 0xca0... No
Probing for `IPMI BMC SMIC' at 0xca8... No
Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (yes/NO):
Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no):
Using driver `i2c-i801' for device 0000:00:1f..3: Intel Enterprise Southbridge - ESB2
Module i2c-dev loaded successfully.
Next adapter: SMBus I801 adapter at 1100 (i2c-0)
Do you want to scan it? (yes/NO/selectively):
Next adapter: NVIDIA i2c adapter (i2c-2)
Do you want to scan it? (YES/no/selectively):
Client found at address 0x50
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... No
Probing for `EDID EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)
Next adapter: NVIDIA i2c adapter (i2c-3)
Do you want to scan it? (YES/no/selectively):
Client found at address 0x2e
Probing for `Myson MTP008'... No
Probing for `National Semiconductor LM78'... No
Probing for `National Semiconductor LM79'... No
Probing for `National Semiconductor LM80'... No
Probing for `National Semiconductor LM85'... No
Probing for `National Semiconductor LM96000 or PC8374L'... No
Probing for `Analog Devices ADM1027'.... No
Probing for `Analog Devices ADT7460 or ADT7463'... No
Probing for `SMSC EMC6D100 or EMC6D101'... No
Probing for `SMSC EMC6D102'... No
Probing for `SMSC EMC6D103'... No
Probing for `Winbond WPCD377I'... No
Probing for `Analog Devices ADT7467 or ADT7468'... No
Probing for `Analog Devices ADT7470'... No
Probing for `Analog Devices ADT7473'... Success!
(confidence 5, driver `adt7473')
Probing for `Analog Devices ADT7475'... No
Probing for `Analog Devices ADT7476'... No
Probing for `Andigilog aSC7611'... No
Probing for `Andigilog aSC7621'... No
Probing for `National Semiconductor LM87'... No
Probing for `Analog Devices ADM1024'... No
Probing for `National Semiconductor LM93'... No
Probing for `Winbond W83781D'... No
Probing for `Winbond W83782D'... No
Probing for `Winbond W83791D'... No
Probing for `Winbond W83792D'... No
Probing for `Winbond W83793R/G'... No
Probing for `Winbond W83627HF'... No
Probing for `Winbond W83627EHF'... No
Probing for `Winbond W83627DHG'... No
Probing for `Asus AS99127F (rev.1)'... No
Probing for `Asus AS99127F (rev.2)'... No
Probing for `Asus ASB100 Bach'... No
Probing for `Winbond W83L786NR/NG/R/G'... No
Probing for `Winbond W83L785TS-S'... No
Probing for `Analog Devices ADM9240'... No
Probing for `Dallas Semiconductor DS1780'... No
Probing for `National Semiconductor LM81'.... No
Probing for `Analog Devices ADM1026'... No
Probing for `Analog Devices ADM1025'... No
Probing for `Analog Devices ADM1029'... No
Probing for `Analog Devices ADM1030'... No
Probing for `Analog Devices ADM1031'... No
Probing for `Analog Devices ADM1022'... No
Probing for `Texas Instruments THMC50'... No
Probing for `Analog Devices ADM1028'... No
Probing for `Texas Instruments THMC51'... No
Probing for `ITE IT8712F'... No
Probing for `SMSC DME1737'... No
Probing for `SMSC SCH5027D-NW'... No
Probing for `Fintek F75373S/SG'... No
Probing for `Fintek F75375S/SP'... No
Probing for `Fintek F75387SG/RG'... No
Probing for `Winbond W83791SD'... No
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `w83627ehf':
* ISA bus, address 0xca0
Chip `Winbond W83627EHF/EF/EHG/EG Super IO Sensors' (confidence: 9)
Driver `adt7473':
* Bus `NVIDIA i2c adapter '
Busdriver `nvidia', I2C address 0x2e
Chip `Analog Devices ADT7473' (confidence: 5)
Driver `coretemp':
* Chip `Intel Core family thermal sensor' (confidence: 9)
Driver `i5k_amb':
* Chip `Intel AMB FB-DIMM thermal sensor' (confidence: 9)
To load everything that is needed, add this to /etc/modules:
#----cut here----
# Adapter drivers
nvidia
# Chip drivers
adt7473
coretemp
i5k_amb
w83627ehf
#----cut here----
If you have some drivers built into your kernel, the list above will
contain too many modules. Skip the appropriate ones!
Do you want to add these lines automatically to /etc/modules? (yes/NO)
Unloading i2c-dev... OK
LSMOD OUTPUT: ==================================================
Module Size Used by
w83627ehf 24328 0
ppp_async 10072 1
crc_ccitt 1944 1 ppp_async
ppp_generic 21720 5 ppp_async
slhc 5752 1 ppp_generic
hwmon_vid 3480 1 w83627ehf
coretemp 6360 0
adt7473 20232 0
nvidia 8113496 26
loop 17252 0
sg 32640 0
sr_mod 15940 0
snd_hda_codec_realtek 253884 1
cdrom 37704 1 sr_mod
usb_storage 56416 0
ata_piix 26396 0
snd_hda_intel 26952 3
ahci 35876 0
uhci_hcd 34680 0
ehci_hcd 52816 0
ohci1394 32276 0
e1000e 125960 0
snd_hda_codec 58712 2 snd_hda_codec_realtek,snd_hda_intel
libata 174380 2 ata_piix,ahci
i5k_amb 6720 0
hwmon 2888 4 w83627ehf,coretemp,adt7473,i5k_amb
i2c_i801 10612 0
OUTPUT OF LSPCI -NN: ==================================================
00:00.0 Host bridge [0600]: Intel Corporation 5400 Chipset Memory Controller Hub [8086:4001] (rev 20)
00:01.0 PCI bridge [0604]: Intel Corporation 5400 Chipset PCI Express Port 1 [8086:4021] (rev 20)
00:05.0 PCI bridge [0604]: Intel Corporation 5400 Chipset PCI Express Port 5 [8086:4025] (rev 20)
00:09.0 PCI bridge [0604]: Intel Corporation 5400 Chipset PCI Express Port 9 [8086:4029] (rev 20)
00:10.0 Host bridge [0600]: Intel Corporation 5400 Chipset FSB Registers [8086:4030] (rev 20)
00:10.1 Host bridge [0600]: Intel Corporation 5400 Chipset FSB Registers [8086:4030] (rev 20)
00:10.2 Host bridge [0600]: Intel Corporation 5400 Chipset FSB Registers [8086:4030] (rev 20)
00:10.3 Host bridge [0600]: Intel Corporation 5400 Chipset FSB Registers [8086:4030] (rev 20)
00:10.4 Host bridge [0600]: Intel Corporation 5400 Chipset FSB Registers [8086:4030] (rev 20)
00:11.0 Host bridge [0600]: Intel Corporation 5400 Chipset CE/SF Registers [8086:4031] (rev 20)
00:15.0 Host bridge [0600]: Intel Corporation 5400 Chipset FBD Registers [8086:4035] (rev 20)
00:15.1 Host bridge [0600]: Intel Corporation 5400 Chipset FBD Registers [8086:4035] (rev 20)
00:16.0 Host bridge [0600]: Intel Corporation 5400 Chipset FBD Registers [8086:4036] (rev 20)
00:16.1 Host bridge [0600]: Intel Corporation 5400 Chipset FBD Registers [8086:4036] (rev 20)
00:1b.0 Audio device [0403]: Intel Corporation 631xESB/632xESB High Definition Audio Controller [8086:269a] (rev 09)
00:1c.0 PCI bridge [0604]: Intel Corporation 631xESB/632xESB/3100 Chipset PCI Express Root Port 1 [8086:2690] (rev 09)
00:1d.0 USB Controller [0c03]: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #1 [8086:2688] (rev 09)
00:1d.1 USB Controller [0c03]: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #2 [8086:2689] (rev 09)
00:1d.2 USB Controller [0c03]: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #3 [8086:268a] (rev 09)
00:1d.3 USB Controller [0c03]: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #4 [8086:268b] (rev 09)
00:1d.7 USB Controller [0c03]: Intel Corporation 631xESB/632xESB/3100 Chipset EHCI USB2 Controller [8086:268c] (rev 09)
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev d9)
00:1f.0 ISA bridge [0601]: Intel Corporation 631xESB/632xESB/3100 Chipset LPC Interface Controller [8086:2670] (rev 09)
00:1f.1 IDE interface [0101]: Intel Corporation 631xESB/632xESB IDE Controller [8086:269e] (rev 09)
00:1f.2 SATA controller [0106]: Intel Corporation 631xESB/632xESB SATA AHCI Controller [8086:2681] (rev 09)
00:1f.3 SMBus [0c05]: Intel Corporation 631xESB/632xESB/3100 Chipset SMBus Controller [8086:269b] (rev 09)
05:00.0 VGA compatible controller [0300]: nVidia Corporation Quadro FX 1700 [10de:040f] (rev a1)
09:00.0 PCI bridge [0604]: Intel Corporation 6311ESB/6321ESB PCI Express Upstream Port [8086:3500] (rev 01)
09:00.3 PCI bridge [0604]: Intel Corporation 6311ESB/6321ESB PCI Express to PCI-X Bridge [8086:350c] (rev 01)
0a:00.0 PCI bridge [0604]: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E1 [8086:3510] (rev 01)
0a:01.0 PCI bridge [0604]: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E2 [8086:3514] (rev 01)
0a:02.0 PCI bridge [0604]: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E3 [8086:3518] (rev 01)
0f:00.0 Ethernet controller [0200]: Intel Corporation 80003ES2LAN Gigabit Ethernet Controller (Copper) [8086:1096] (rev 01)
0f:00.1 Ethernet controller [0200]: Intel Corporation 80003ES2LAN Gigabit Ethernet Controller (Copper) [8086:1096] (rev 01)
1f:00.0 SCSI storage controller [0100]: LSI Logic / Symbios Logic SAS1068E PCI-Express Fusion-MPT SAS [1000:0058] (rev 04)
20:04.0 Audio device [0403]: Creative Labs SB X-Fi [1102:0005]
20:05.0 FireWire (IEEE 1394) [0c00]: Texas Instruments TSB43AB22/A IEEE-1394a-2000 Controller (PHY/Link) [104c:8023]
CHIP PART NUMBER: ==================================================
816G9C28083030UB
"SENSORS -S ERRORS": ==================================================
ioctl(3, SNDCTL_TMR_TIMEBASE or TCGETS, 0x7fff86877cd0) = -1 ENOTTY (Inappropriate ioctl for device)
ioctl(3, SNDCTL_TMR_TIMEBASE or TCGETS, 0x7fff86876570) = -1 ENOTTY (Inappropriate ioctl for device)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20090411/615fb138/attachment-0001.html
