Red Hat Bugzilla – Bug 1362664
sensors-detect triggers multiple errors if unsupported
Last modified: 2016-11-04 02:39:11 EDT
Description of problem: After running sensors-detect, I'm seeing the following errors printed on aarch64 HP Moonshot system: - Use of uninitialized value in concatenation (.) or string at /usr/sbin/sensors-detect line 2880. - modprobe: FATAL: Module cpuid not found. Failed to load module cpuid. - /dev/port: No such file or directory - Processor: (//) Version-Release number of selected component (if applicable): ~]# rpm -q lm_sensors lm_sensors-3.4.0-2.20160601gitf9185e5.el7.aarch64 How reproducible: Always Steps to Reproduce: 1. sensors-detect 2. 3. Actual results: ~]# sensors-detect # sensors-detect revision $Revision$ # System: HP ProLiant m400 Server # Kernel: 4.5.0-0.48.el7.aarch64 aarch64 Use of uninitialized value in concatenation (.) or string at /usr/sbin/sensors-detect line 2880. Use of uninitialized value in concatenation (.) or string at /usr/sbin/sensors-detect line 2880. Use of uninitialized value in concatenation (.) or string at /usr/sbin/sensors-detect line 2880. Use of uninitialized value in concatenation (.) or string at /usr/sbin/sensors-detect line 2880. # Processor: (//) 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): modprobe: FATAL: Module cpuid not found. Failed to load module cpuid. Silicon Integrated Systems SIS5595... No VIA VT82C686 Integrated Sensors... No VIA VT8231 Integrated Sensors... No AMD K8 thermal sensors... No AMD Family 10h thermal sensors... No AMD Family 11h thermal sensors... No AMD Family 12h and 14h thermal sensors... No AMD Family 15h thermal sensors... No AMD Family 16h thermal sensors... No AMD Family 15h power sensors... No AMD Family 16h power sensors... No Intel digital thermal sensor... No Intel AMB FB-DIMM thermal sensor... No Intel 5500/5520/X58 thermal sensor... No VIA C7 thermal sensor... No VIA Nano thermal sensor... 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): /dev/port: No such file or directory Some systems (mainly servers) implement IPMI, a set of common interfaces through which system health data may be retrieved, amongst other things. We first try to get the information from SMBIOS. If we don't find it there, 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): Found `IPMI BMC KCS' at 0xca2... Success! (confidence 8, driver `to-be-written') 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): /dev/port: No such file or directory 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): Sorry, no supported PCI bus adapters found. Module i2c-dev loaded successfully. Now follows a summary of the probes I have just done. Just press ENTER to continue: Driver `to-be-written': * ISA bus, address 0xca2 Chip `IPMI BMC KCS' (confidence: 8) Note: there is no driver for IPMI BMC KCS yet. Check http://www.lm-sensors.org/wiki/Devices for updates. No modules to load, skipping modules configuration. Unloading i2c-dev... OK Expected results: NO errors Additional info:
If sensors-detect is not supported maybe a usage message could be displayed ?
This is really just an FYI... Since I was the one that added the patch to remove /dev/port from aarch64, I thought I would take a look at this bug. It appears some porting is needed; I'm afraid perl is not a strong point for me, but the initial reported message is due to there being no CPU info to print out in the function print_cpu_info() in sensors-detect (i.e., that $cpu is undefined at line 2880). The cpuid module is not found because it is specific to x86. And /dev/port is not present because it makes little sense on aarch64 and has been removed. Out of curiosity, I tried the Debian sid version of sensors-detect (also a 3.4.0 version, but claiming support for multiple architectures) and it was much more polite -- none of the above messages appeared, but no CPU info was printed either. It does, however, use quite a few patches, at least three changing sensors-detect. It looks like aarch64 ended up working better because of sone of the patches made to support ppc64; not knowing enough about this package or perl, though, I hesitate to suggest which patches if any may help.
Much better ! The version details looks good and the 'Use of uninitialized value in concatenation (.) or string at /usr/sbin/sensors-detect line 2880' error is no longer displayed, it would be nice to also suppress the 'modprobe: FATAL: Module cpuid not found.Failed to load module cpuid.' and '/dev/port: No such file or directory' on the aarch64 arch, but at least now we are warned about the unsupported architecture. [root@hp-moonshot-02-c10 ~]# rpm -q lm_sensors lm_sensors-3.4.0-4.20160601gitf9185e5.el7.aarch64 [root@hp-moonshot-02-c10 ~]# sensors-detect # sensors-detect revision 3.4.0-4 (2016-06-01) # System: HPE ProLiant m400 Server # Kernel: 4.5.0-3.el7.aarch64 aarch64 ********** Your processor's architecture is not yet supported. Beware that sensors-detect might not work properly! ********** 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): modprobe: FATAL: Module cpuid not found. Failed to load module cpuid. Silicon Integrated Systems SIS5595... No VIA VT82C686 Integrated Sensors... No VIA VT8231 Integrated Sensors... No AMD K8 thermal sensors... No AMD Family 10h thermal sensors... No AMD Family 11h thermal sensors... No AMD Family 12h and 14h thermal sensors... No AMD Family 15h thermal sensors... No AMD Family 16h thermal sensors... No AMD Family 15h power sensors... No AMD Family 16h power sensors... No Intel digital thermal sensor... No Intel AMB FB-DIMM thermal sensor... No Intel 5500/5520/X58 thermal sensor... No VIA C7 thermal sensor... No VIA Nano thermal sensor... 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): /dev/port: No such file or directory Some systems (mainly servers) implement IPMI, a set of common interfaces through which system health data may be retrieved, amongst other things. We first try to get the information from SMBIOS. If we don't find it there, 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): Found `IPMI BMC KCS' at 0xca2... Success! (confidence 8, driver `to-be-written') 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): /dev/port: No such file or directory 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): Sorry, no supported PCI bus adapters found. Module i2c-dev loaded successfully. Now follows a summary of the probes I have just done. Just press ENTER to continue: Driver `to-be-written': * ISA bus, address 0xca2 Chip `IPMI BMC KCS' (confidence: 8) Note: there is no driver for IPMI BMC KCS yet. Check http://www.lm-sensors.org/wiki/Devices for updates. No modules to load, skipping modules configuration. Unloading i2c-dev... OK
*** Bug 1371791 has been marked as a duplicate of this bug. ***
Verified as fixed, using an unsupported arch, a warning message is now displayed, no longer seeing 'Use of uninitialized value in concatenation (.) or string at /usr/sbin/sensors-detect line 2880.' However I am seeing a regression on supported systems, I will file a new bug to track. [root@hp-moonshot-03-c12 ~]# sensors-detect # sensors-detect revision 3.4.0-4 (2016-06-01) # System: HPE ProLiant m400 Server # Kernel: 4.5.0-8.el7.aarch64 aarch64 ********** Your processor's architecture is not yet supported. Beware that sensors-detect might not work properly! ********** 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): modprobe: FATAL: Module cpuid not found. Failed to load module cpuid. Silicon Integrated Systems SIS5595... No VIA VT82C686 Integrated Sensors... No VIA VT8231 Integrated Sensors... No AMD K8 thermal sensors... No AMD Family 10h thermal sensors... No AMD Family 11h thermal sensors... No AMD Family 12h and 14h thermal sensors... No AMD Family 15h thermal sensors... No AMD Family 16h thermal sensors... No AMD Family 15h power sensors... No AMD Family 16h power sensors... No Intel digital thermal sensor... No Intel AMB FB-DIMM thermal sensor... No Intel 5500/5520/X58 thermal sensor... No VIA C7 thermal sensor... No VIA Nano thermal sensor... 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): /dev/port: No such file or directory Some systems (mainly servers) implement IPMI, a set of common interfaces through which system health data may be retrieved, amongst other things. We first try to get the information from SMBIOS. If we don't find it there, 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): Found `IPMI BMC KCS' at 0xca2... Success! (confidence 8, driver `to-be-written') 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): /dev/port: No such file or directory 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): Sorry, no supported PCI bus adapters found. Module i2c-dev loaded successfully. Now follows a summary of the probes I have just done. Just press ENTER to continue: Driver `to-be-written': * ISA bus, address 0xca2 Chip `IPMI BMC KCS' (confidence: 8) Note: there is no driver for IPMI BMC KCS yet. Check http://www.lm-sensors.org/wiki/Devices for updates. No modules to load, skipping modules configuration. Unloading i2c-dev... OK
------- Comment From pavsubra@in.ibm.com 2016-09-19 07:04 EDT------- I have installed RHEL 7.3 LE Snapshot3 build and again executed the test. [root@ltc-garri5 ~]# uname -a Linux ltc-garri5.aus.stglabs.ibm.com 3.10.0-505.el7.ppc64le #1 SMP Tue Sep 6 11:09:32 EDT 2016 ppc64le ppc64le ppc64le GNU/Linux [root@ltc-garri5 ~]# cat /etc/os-release NAME="Red Hat Enterprise Linux Server" VERSION="7.3 (Maipo)" ID="rhel" ID_LIKE="fedora" VERSION_ID="7.3" PRETTY_NAME="Red Hat Enterprise Linux Server 7.3 Beta (Maipo)" ANSI_COLOR="0;31" CPE_NAME="cpe:/o:redhat:enterprise_linux:7.3:beta:server" HOME_URL="https://www.redhat.com/" BUG_REPORT_URL="https://bugzilla.redhat.com/" REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 7" REDHAT_BUGZILLA_PRODUCT_VERSION=7.3 REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux" REDHAT_SUPPORT_PRODUCT_VERSION="7.3 Beta" [root@ltc-garri5 ~]# update_flash -d Firmware version: Product Name : OpenPOWER Firmware Product Version : IBM-garrison-ibm-OP8_v1.10_2.17 Product Extra : op-build-b4e013a Product Extra : buildroot-81b8d98 Product Extra : skiboot-5.3.3 Product Extra : hostboot-1f6784d-113d2bd Product Extra : linux-4.4.16-openpower1-a515412 Product Extra : petitboot-v1.2.4-7e6637c Product Extra : garrison-xml-3db7b6e Product Extra : occ-69fb587 Product Extra : hostboot-bina [root@ltc-garri5 ~]# cat /proc/cpuinfo | tail processor : 159 cpu : POWER8NVL (raw), altivec supported clock : 4023.000000MHz revision : 1.0 (pvr 004c 0100) timebase : 512000000 platform : PowerNV model : 8335-GTB machine : PowerNV 8335-GTB firmware : OPAL v3 [root@ltc-garri5 ~]# which sensors-detect /usr/sbin/sensors-detect [root@ltc-garri5 ~]# rpm -qf /usr/sbin/sensors-detect lm_sensors-3.4.0-4.20160601gitf9185e5.el7.ppc64le ------- Comment From pavsubra@in.ibm.com 2016-09-19 07:06 EDT------- [root@ltc-garri5 ~]# sensors-detect # DMI data unavailable, please consider installing dmidecode 2.7 # or later for better results. # Kernel: 3.10.0-505.el7.ppc64le ppc64le Do you want to scan for them? This is totally safe. (YES/no): YES mmap: Invalid argument Do you want to scan for Super I/O sensors? (YES/no): YES Probing for Super-I/O at 0x2e/0x2f Trying family `National Semiconductor/ITE'... Yes Found unknown chip with ID 0x6060 Probing for Super-I/O at 0x4e/0x4f Trying family `National Semiconductor/ITE'... Yes Found unknown chip with ID 0x6060 interfaces? (YES/no): YES Probing for `IPMI BMC KCS' at 0xca0... Success! (confidence 4, driver `to-be-written') Probing for `IPMI BMC SMIC' at 0xca8... Success! (confidence 4, driver `to-be-written') ISA slots! Do you want to scan the ISA I/O ports? (YES/no): YES Probing for `National Semiconductor LM78' 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 Do you want to probe the I2C/SMBus adapters now? (YES/no): YES As can be seen the above command execution doesn't show the original uninitialized messages. So, the issue is fixed and the bug is resolved and verified.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-2450.html