[Bug 256212] New: "sensors" output error
https://bugzilla.novell.com/show_bug.cgi?id=256212 Summary: "sensors" output error Product: openSUSE 10.2 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: Other AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: jimomura@pathcom.com QAContact: qa@suse.de I am using an MSI K9A Platinum motherboard with Crossfire 3200 chipset and a single core Sempron 2800+ CPU. I used the usual activiation of "sensors-detect". The following is the current result: Test: - Booted computer @ 23:00 - did research on Web for 40 min. to stabilize temp. etc. - @ 23:41 ran "sensors >outputfile.txt" - Then re-booted into BIOS and checked "Health" output to confirm: "sensors" output: -- w83627ehf-isa-0a10 Adapter: ISA adapter VCore: +1.38 V (min = +0.00 V, max = +1.74 V) in1: +12.30 V (min = +7.34 V, max = +6.60 V) ALARM AVCC: +3.33 V (min = +1.30 V, max = +4.08 V) 3VCC: +3.33 V (min = +1.33 V, max = +1.52 V) ALARM in4: +1.62 V (min = +0.81 V, max = +1.12 V) ALARM in5: +1.45 V (min = +0.76 V, max = +0.20 V) ALARM in6: +4.63 V (min = +4.84 V, max = +4.48 V) ALARM VSB: +3.31 V (min = +1.52 V, max = +2.29 V) ALARM VBAT: +3.31 V (min = +0.48 V, max = +2.64 V) ALARM in9: +1.64 V (min = +1.53 V, max = +1.24 V) ALARM Case Fan: 2083 RPM (min = 907 RPM, div = 8) CPU Fan: 2311 RPM (min = 883 RPM, div = 8) Aux Fan: 0 RPM (min = 703 RPM, div = 64) ALARM fan4: 0 RPM (min = 0 RPM, div = 64) Sys Temp: +40°C (high = -30°C, hyst = +127°C) CPU Temp: +34.5°C (high = +80.0°C, hyst = +75.0°C) AUX Temp: +34.0°C (high = +80.0°C, hyst = +75.0°C) * Note the bogus "alarms" -- The following is what the BIOS reported: (some numbers were changing constantly) CPU Temperature: 36 deg. C/96 deg. F System Temp: 40 deg. C/104 deg. F CPU Fan Speed: 2410 System Fan Speed: 2109 Vcore: 1.368 - 1.408V +3.3 V: 3.328 +5.0 V: 5.145 +12.0 V: 12.302 +3 Vsb: 3.328 -- The above confirms no real reason for "alarms". Normal operation. The following was the output of the activation: linux-h939:~ # sensors-detect # sensors-detect revision 4171 (2006-09-24 03:37:01 -0700) 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. We can start with probing for (PCI) I2C or SMBus adapters. Do you want to probe now? (YES/no): yes Probing for PCI bus adapters... Found unknown SMBus adapter 1002:4385 at 0000:00:14.0. Sorry, no known PCI bus adapters found. We will now try to load each adapter module in turn. If you have undetectable or unsupported adapters, you can have them scanned by manually loading the modules before running this script. To continue, we need module `i2c-dev' to be loaded. Do you want to load `i2c-dev' now? (YES/no): yes Module loaded successfully. We are now going to do the I2C/SMBus adapter probings. Some chips may be double detected; we choose the one with the highest confidence value in that case. If you found that the adapter hung after probing a certain address, you can specify that address to remain unprobed. Some chips are also 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): yest Probing for `National Semiconductor LM78' at 0x290... No Probing for `National Semiconductor LM78-J' at 0x290... No Probing for `National Semiconductor LM79' at 0x290... No Probing for `Winbond W83781D' at 0x290... No Probing for `Winbond W83782D' at 0x290... No Probing for `Winbond W83627HF' at 0x290... No Probing for `Silicon Integrated Systems SIS5595'... No Probing for `VIA VT82C686 Integrated Sensors'... No Probing for `VIA VT8231 Integrated Sensors'... No Probing for `AMD K8 thermal sensors'... Success! (confidence 9, driver `k8temp') Probing for `IPMI BMC KCS' at 0xca0... No Probing for `IPMI BMC SMIC' at 0xca8... No Some Super I/O chips may also contain 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): yes Probing for Super-I/O at 0x2e/0x2f Trying family `ITE'... No Trying family `National Semiconductor'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Fintek'... No Probing for Super-I/O at 0x4e/0x4f Trying family `ITE'... No Trying family `National Semiconductor'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Fintek'... Yes Found `Winbond W83627EHF/EHG Super IO Sensors' Success! (address 0xa10, driver `w83627ehf') Now follows a summary of the probes I have just done. Just press ENTER to continue: Driver `k8temp' (should be inserted): Detects correctly: * ISA bus, undetermined address (Busdriver `i2c-isa') Chip `AMD K8 thermal sensors' (confidence: 9) Driver `w83627ehf' (should be inserted): Detects correctly: * ISA bus address 0x0a10 (Busdriver `i2c-isa') Chip `Winbond W83627EHF/EHG Super IO Sensors' (confidence: 9) I will now generate the commands needed to load the required modules. Just press ENTER to continue: To make the sensors modules behave correctly, add these lines to /etc/modprobe.conf: #----cut here---- # I2C module options alias char-major-89 i2c-dev #----cut here---- To load everything that is needed, add this to some /etc/rc* file: #----cut here---- # I2C adapter drivers # Chip drivers # Warning: the required module k8temp is not currently installed # on your system. For status of 2.6 kernel ports check # http://www.lm-sensors.org/wiki/Devices. If driver is built # into the kernel, or unavailable, comment out the following line. modprobe k8temp modprobe w83627ehf # sleep 2 # optional /usr/bin/sensors -s # recommended #----cut here---- If you have some drivers built into your kernel, the list above will contain too many modules. Skip the appropriate ones! You really should try these commands right now to make sure everything is working properly. Monitoring programs won't work until the needed modules are loaded. Do you want to generate /etc/sysconfig/lm_sensors? (YES/no): yes -- The files I modified were: /etc/rc.status /etc/modprobe.conf /etc/sysconfig/lm_sensors -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=256212 ------- Comment #1 from jimomura@pathcom.com 2007-03-20 16:27 MST ------- Point 1: I did not realize that the ranges were not fully standardized. I have gone through them and re-defined them to get rid of most of the "Alarms". However, it looks like calculated ranges are giving incorrect results. There could be an error in data definitions or casts somewhere. Regardless of that, I think I can get rid of the last "alarm". However, I am doing so by simply setting ranges to get rid of the alarms. I have no specs to set them by yet. If I get real specs, I will post the setting changes later. Unfortunately, I do not expect that I will ever see real specs. So at most, there might be a problem with calculations of limits. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=256212 ------- Comment #2 from jimomura@pathcom.com 2007-03-20 19:22 MST ------- The following are the original settings in the "sensors.conf" file, which resulted in the output that I posted previously: # Start of Original Settings: # Winbond W83627EHF configuration originally contributed by Leon Moonen # This is for an Asus P5P800, voltages for A8V-E SE. chip "w83627ehf-*" label in0 "VCore" label in2 "AVCC" label in3 "3VCC" label in7 "VSB" label in8 "VBAT" # +12V is in1 and +5V is in6 as recommended by datasheet compute in1 @*(1+(56/10)), @/(1+(56/10)) compute in6 @*(1+(22/10)), @/(1+(22/10)) # set in1_min 12.0*0.9 # set in1_max 12.0*1.1 # set in6_min 5.0*0.95 # set in6_max 5.0*1.05 # Set the 3.3V # set in2_min 3.3*0.95 # set in2_max 3.3*1.05 # set in3_min 3.3*0.95 # set in3_max 3.3*1.05 # set in7_min 3.3*0.95 # set in7_max 3.3*1.05 # set in8_min 3.3*0.95 # set in8_max 3.3*1.05 # Fans label fan1 "Case Fan" label fan2 "CPU Fan" label fan3 "Aux Fan" # ignore fan3 # ignore fan4 # set fan1_min 1200 # set fan2_min 1700 # Temperatures label temp1 "Sys Temp" label temp2 "CPU Temp" label temp3 "AUX Temp" # ignore temp3 # set temp1_over 45 # set temp1_hyst 40 # set temp2_over 45 # set temp2_hyst 40 # End of Original Settings -- The following is the list of entries I am using now. The changes are just get rid of the "Alarms" and are NOT based on actual specifications for the hardware: # Winbond W83627EHF configuration originally contributed by Leon Moonen # This is for an Asus P5P800, voltages for A8V-E SE. # Edited for MSI-K9A Platinum Jim O. 2007-03-20 chip "w83627ehf-*" label in0 "VCore" label in1 "unknown" label in2 "AVCC" label in3 "3VCC" label in7 "VSB" label in8 "VBAT" # +12V is in1 and +5V is in6 as recommended by datasheet # compute in1 @*(1+(56/10)), @/(1+(56/10)) # compute in6 @*(1+(22/10)), @/(1+(22/10)) set in1_min 1.8*0.9 set in1_max 1.8*1.1 # set in6_min 5.0*0.95 # set in6_max 5.0*1.05 # Set the 3.3V # set in2_min 3.3*0.95 # set in2_max 3.3*1.05 set in3_min 3.3*0.95 set in3_max 3.3*1.05 # Jim O Inputs 4-6 & 9 are unknown. I am just setting them to ranges that kill the alarm set in4_min 1.6*0.95 set in4_max 1.6*1.05 set in5_min 1.45*0.95 set in5_max 1.45*1.05 set in6_min 1.45*0.95 set in6_max 1.45*1.05 set in9_min 1.64*0.95 set in9_max 1.64*1.05 # Following were commented out. Appear to be correct, so I re-instated them. set in7_min 3.3*0.95 set in7_max 3.3*1.05 set in8_min 3.3*0.95 set in8_max 3.3*1.05 # Fans label fan1 "Case Fan" label fan2 "CPU Fan" label fan3 "Aux Fan" # ignore fan3 # ignore fan4 # set fan1_min 1200 # set fan2_min 1700 set fan3_min 00 # Temperatures label temp1 "Sys Temp" label temp2 "CPU Temp" label temp3 "AUX Temp" # ignore temp3 set temp1_over 45 # I changed hyst from 40 to 75 -- JO set temp1_hyst 75 # set temp2_over 45 # set temp2_hyst 40 # End of MSI K9A Platinum -- The following is the output from "sensors": w83627ehf-isa-0a10 Adapter: ISA adapter VCore: +1.36 V (min = +0.00 V, max = +1.74 V) unknown: +1.86 V (min = +1.62 V, max = +1.98 V) AVCC: +3.33 V (min = +1.30 V, max = +4.08 V) 3VCC: +3.33 V (min = +3.14 V, max = +3.47 V) in4: +1.62 V (min = +1.52 V, max = +1.68 V) in5: +1.45 V (min = +1.38 V, max = +1.52 V) in6: +1.45 V (min = +1.38 V, max = +1.52 V) VSB: +3.33 V (min = +3.14 V, max = +3.47 V) VBAT: +3.30 V (min = +3.14 V, max = +3.47 V) in9: +1.65 V (min = +1.56 V, max = +1.72 V) Case Fan: 2083 RPM (min = 907 RPM, div = 8) CPU Fan: 2311 RPM (min = 883 RPM, div = 8) Aux Fan: 0 RPM (min = 0 RPM, div = 16) fan4: 0 RPM (min = 0 RPM, div = 16) Sys Temp: +40°C (high = +45°C, hyst = +75°C) CPU Temp: +39.0°C (high = +80.0°C, hyst = +75.0°C) AUX Temp: +39.0°C (high = +80.0°C, hyst = +75.0°C) Note that the readings from the sensors should not have been affected by the changes that I made to the parameters, but now there are no 12V or 5V readings. Again, I can only conclude that there is some kind of data "TYPE" or "CAST" error somewhere. I have not yet checked the "lm-sensors" website yet. I might not get a chance to do so for the next few days. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=256212 chrubis@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |werner@novell.com |screening@forge.provo.novell| |.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=256212 werner@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jdelvare@novell.com Status|NEW |RESOLVED Resolution| |INVALID ------- Comment #3 from werner@novell.com 2007-03-21 06:57 MST ------- This bug entry is invalid due to the fact that you have to change the /etc/sensors.conf to fit the needs of your hardware. Every entry in the provided may or may not fit your hardware. If you can provide a good configuration for your hardware please submit this to the lm-sensors website with the exact model name including the version If the developers will integrate this then the next update will provide such changes for all users. One remark: a line like VCore: +1.36 V (min = +0.00 V, max = +1.74 V) seems to be buggy (IMHO). The minimal voltage of an CPU core voltage is not zero on a running system. Currently the lm-sensors package does not provide an intelligent configuration of /etc/sensors.conf depending on the hardware found. Such a configuration does highly depend on the mainboard, CPU, chipset, BIOS, and the versions of all, which makes such a job very difficlut for an automatic setup without a human wizard. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=256212 ------- Comment #4 from jimomura@pathcom.com 2007-03-21 13:51 MST ------- (In reply to comment #3)
This bug entry is invalid due to the fact that you have to change the /etc/sensors.conf to fit the needs of your hardware. Every entry in the provided may or may not fit your hardware. If you can provide a good configuration for your hardware please submit this to the lm-sensors website with the exact model name including the version If the developers will integrate this then the next update will provide such changes for all users.
I have read a bit of the lm-sensors website, and I understand the situation better now. I also downloaded the documentation for the Winbond chip. As I see it, I should be able to get the VCore spec and temperature specs for the key chips, but the other voltage specs are pretty much out of my reach. MSI will have to tell me what they are supposed to be. It would be a good idea to make a small note in the HOWTO Wiki summarizing the situation for anyone interested. According to the lm-sensor site, the package is now being maintained as part of the Kernel, so a link to the Kernel website might be appropriate. (I would do this myself, but I have not added anything to a Wiki yet, so I do not know how.)
One remark: a line like
VCore: +1.36 V (min = +0.00 V, max = +1.74 V)
seems to be buggy (IMHO). The minimal voltage of an CPU core voltage is not zero on a running system.
. . It could be and infinitely efficient processor? :-) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=256212 ------- Comment #5 from jdelvare@novell.com 2007-03-21 14:23 MST ------- (In reply to comment #4)
It would be a good idea to make a small note in the HOWTO Wiki summarizing the situation for anyone interested. According to the lm-sensor site, the package is now being maintained as part of the Kernel, so a link to the Kernel website might be appropriate.
Only the driver development has moved to the kernel. The user-space part is still handled on lm-sensors.org.
(I would do this myself, but I have not added anything to a Wiki yet, so I do not know how.)
Unfortunately the wiki is read-only for visitors, as it was flooded with spam otherwise. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=256212 ------- Comment #6 from jimomura@pathcom.com 2007-03-22 14:38 MST ------- This is likely to be my last comment on this issue for the forseeable future: 1. I said previously that there seemed to be a Type or Cast error. As far as I can tell, I was wrong. On further investigation, I found that I had misunderstood some of the data calculations. As far as I know, the programs were running correctly. If I find out otherwise in the future, I will, of course post that information, but for now, I have no reason to believe the programs are incorrect. 2. The current version of "lm-sensors" in OpenSuSE 10.2 is "2.10.1-5". The data supporting the Winbond "w83627ehf" which connects the sensors on the my board was updated in lm-sensors 2.10.2, and the ATI SB600 (used in my board) chip support was defined in the very latest lm-sensors 2.10.3, which is just now in the process of being released. As such, I think my own next step is to wait for the release of lm-sensors 2.10.3 (which will be any-day-now) and then start over again at that point. In fact, I might just wait a while and see if you guys are going to update the "sensors" package for OpenSuSE 10.2. I expect that the "sensors.conf" file for 2.10.3 will be backwards compatible, and if it works with the current programs, I might just use that much as a new starting point for my adjustments -- unless you guys put out a new package. In that case I will start from whatever is in the updates. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=256212 ------- Comment #7 from jdelvare@novell.com 2007-03-22 15:27 MST ------- (In reply to comment #6)
2. The current version of "lm-sensors" in OpenSuSE 10.2 is "2.10.1-5". The data supporting the Winbond "w83627ehf" which connects the sensors on the my board was updated in lm-sensors 2.10.2, and the ATI SB600 (used in my board) chip support was defined in the very latest lm-sensors 2.10.3, which is just now in the process of being released.
The ATI SB600 support is something which happens in the kernel, not in the lm-sensors package. Upgrading to lm-sensors 2.10.3 will not help you, what you need is a 2.6.21 kernel. That being said, if your hardware monitoring device is handled by the w83627ehf driver, it means it is not connected to the SMBus, so you don't need the ATI SB600 support at all.
As such, I think my own next step is to wait for the release of lm-sensors 2.10.3 (which will be any-day-now) and then start over again at that point. In fact, I might just wait a while and see if you guys are going to update the "sensors" package for OpenSuSE 10.2.
No, we are not. We don't upgrade packages once a distribution is released. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
participants (1)
-
bugzilla_noreply@novell.com