Bug 1899896
| Summary: | "sensors: No sensors found!" running Fedora as a HVM virtual machine (domU) | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Marcin CIEŚLAK <redhat> |
| Component: | lm_sensors | Assignee: | Hans de Goede <hdegoede> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 33 | CC: | aegorenk, awilliam, hdegoede, jaromir.capik, olysonek-foss, pknirsch |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | openqa | ||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-11-30 18:07:10 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Right. This actually affects Fedora Server disk image deployments (commonly used on ARM especially) out of the box, because the disk images include the 'server-hardware-support' group which includes lm_sensors. If you deploy one on a VM, you get a failed lm_sensors service out of the box on first boot. This should be fixed with: https://src.fedoraproject.org/rpms/lm_sensors/c/a2bee3abb72af537635fcb94b51f652ca7684f5c?branch=rawhide Build: https://koji.fedoraproject.org/koji/taskinfo?taskID=62681374 Behavior: - on physical: - if sensors found, return 0 - if sensors not found, return 1 + error message - on virtual: - if sensors found, return 0 - if sensors not fount, return 0 + error message This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '33'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 33 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '33'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 33 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |
Description of problem: lm_sensors fails at startup, well, maybe because there may be no sensors? Version-Release number of selected component (if applicable): lm_sensors-3.6.0-5.fc33.x86_64 kernel-5.9.8-200.fc33.x86_64 How reproducible: Always, seen with Fedora 30 and after upgrade to 33, maybe earlier (the original installation was 25). Steps to Reproduce: 1. Install Fedora 30 as a HVM guest under Xen 2. Upgrade Fedora 30 to Fedora 32 via dnf system-upgrade 3. Upgrade Fedora 32 to Fedora 33 via dnf system-upgrade Actual results: # journalctl -u lm_sensors -- Logs begin at Tue 2020-11-17 20:08:14 CET, end at Fri 2020-11-20 11:30:32 CET. -- Nov 17 20:14:15 fedora0.6speed.de systemd[1]: Starting Hardware Monitoring Sensors... Nov 17 20:14:15 fedora0.6speed.de lm_sensors-modprobe-wrapper[849]: No sensors with loadable kernel modules configured. Nov 17 20:14:15 fedora0.6speed.de lm_sensors-modprobe-wrapper[849]: Please, run 'sensors-detect' as root in order to searc> Nov 17 20:14:17 fedora0.6speed.de sensors[861]: No sensors found! Nov 17 20:14:17 fedora0.6speed.de sensors[861]: Make sure you loaded all the kernel drivers you need. Nov 17 20:14:17 fedora0.6speed.de sensors[861]: Try sensors-detect to find out which these are. Nov 17 20:14:17 fedora0.6speed.de systemd[1]: lm_sensors.service: Main process exited, code=exited, status=1/FAILURE Nov 17 20:14:17 fedora0.6speed.de systemd[1]: lm_sensors.service: Failed with result 'exit-code'. Nov 17 20:14:17 fedora0.6speed.de systemd[1]: Failed to start Hardware Monitoring Sensors. -- Reboot -- Nov 18 00:55:13 fedora0.6speed.de systemd[1]: Starting Hardware Monitoring Sensors... Nov 18 00:55:13 fedora0.6speed.de lm_sensors-modprobe-wrapper[706]: No sensors with loadable kernel modules configured. Nov 18 00:55:13 fedora0.6speed.de lm_sensors-modprobe-wrapper[706]: Please, run 'sensors-detect' as root in order to searc> Nov 18 00:55:17 fedora0.6speed.de sensors[728]: No sensors found! Nov 18 00:55:17 fedora0.6speed.de sensors[728]: Make sure you loaded all the kernel drivers you need. Nov 18 00:55:17 fedora0.6speed.de sensors[728]: Try sensors-detect to find out which these are. Nov 18 00:55:17 fedora0.6speed.de systemd[1]: lm_sensors.service: Main process exited, code=exited, status=1/FAILURE Nov 18 00:55:17 fedora0.6speed.de systemd[1]: lm_sensors.service: Failed with result 'exit-code'. Nov 18 00:55:17 fedora0.6speed.de systemd[1]: Failed to start Hardware Monitoring Sensors. -- Reboot -- Nov 20 05:03:58 fedora0.6speed.de systemd[1]: Starting Hardware Monitoring Sensors... Nov 20 05:03:59 fedora0.6speed.de lm_sensors-modprobe-wrapper[708]: No sensors with loadable kernel modules configured. Nov 20 05:03:59 fedora0.6speed.de lm_sensors-modprobe-wrapper[708]: Please, run 'sensors-detect' as root in order to searc> Nov 20 05:04:07 fedora0.6speed.de sensors[721]: No sensors found! Nov 20 05:04:07 fedora0.6speed.de sensors[721]: Make sure you loaded all the kernel drivers you need. Nov 20 05:04:07 fedora0.6speed.de sensors[721]: Try sensors-detect to find out which these are. Nov 20 05:04:07 fedora0.6speed.de systemd[1]: lm_sensors.service: Main process exited, code=exited, status=1/FAILURE Nov 20 05:04:07 fedora0.6speed.de systemd[1]: lm_sensors.service: Failed with result 'exit-code'. Nov 20 05:04:07 fedora0.6speed.de systemd[1]: Failed to start Hardware Monitoring Sensors. -- Reboot -- Nov 20 07:08:11 fedora0.6speed.de systemd[1]: Starting Hardware Monitoring Sensors... Nov 20 07:08:11 fedora0.6speed.de lm_sensors-modprobe-wrapper[750]: No sensors with loadable kernel modules configured. Nov 20 07:08:11 fedora0.6speed.de lm_sensors-modprobe-wrapper[750]: Please, run 'sensors-detect' as root in order to searc> Nov 20 07:08:13 fedora0.6speed.de sensors[766]: No sensors found! Nov 20 07:08:13 fedora0.6speed.de sensors[766]: Make sure you loaded all the kernel drivers you need. Nov 20 07:08:13 fedora0.6speed.de sensors[766]: Try sensors-detect to find out which these are. Nov 20 07:08:13 fedora0.6speed.de systemd[1]: lm_sensors.service: Main process exited, code=exited, status=1/FAILURE Nov 20 07:08:13 fedora0.6speed.de systemd[1]: lm_sensors.service: Failed with result 'exit-code'. Nov 20 07:08:13 fedora0.6speed.de systemd[1]: Failed to start Hardware Monitoring Sensors. -- Reboot -- Nov 20 10:59:27 fedora0.6speed.de systemd[1]: Starting Hardware Monitoring Sensors... Nov 20 10:59:27 fedora0.6speed.de lm_sensors-modprobe-wrapper[707]: No sensors with loadable kernel modules configured. Nov 20 10:59:27 fedora0.6speed.de lm_sensors-modprobe-wrapper[707]: Please, run 'sensors-detect' as root in order to searc> Nov 20 10:59:31 fedora0.6speed.de sensors[726]: No sensors found! Expected results: The service should realize there are no sensors and this is not an error condition. "systemctl" output should be clean without errors. Additional info: Xen domain configuration file: builder = "hvm" name = "fedora" disk = [ '/dev/zvol/zroot/fedora0,raw,xvda,w', '/dev/zvol/zroot/fedorab2g,raw,xvdb,w', '/dev/zvol/zroot/verity,raw,xvdc,w' # '/root/xen/Fedora-Server-netinst-x86_64-25-1.3.iso,raw,hdc:cdrom,r' ] boot = "c" bios = "ovmf" usbdevice = 'tablet' vnc = 1 vif = ['bridge=bridge1,mac=00:02:04:08:99:f0'] memory=2048 vcpus=2 vga = "stdvga" videoram = 16 xen_platform_pci=0 lm_sensors config: # /etc/sysconfig/lm_sensors - Defines modules loaded by the lm_sensors service # Run 'sensors-detect' to generate this config file # sensors-detect --auto # sensors-detect version 3.6.0 # System: Xen HVM domU [4.7.2] # Kernel: 5.9.8-200.fc33.x86_64 x86_64 # Processor: Intel(R) Xeon(R) CPU E31245 @ 3.30GHz (6/42/7) Running in automatic mode, default answers to all questions are assumed. 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 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 17h thermal sensors... No AMD Family 15h power sensors... No AMD Family 16h power sensors... No Hygon Family 18h thermal 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): Probing for Super-I/O at 0x2e/0x2f Trying family `National Semiconductor/ITE'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Nuvoton/Fintek'... No Trying family `ITE'... No Probing for Super-I/O at 0x4e/0x4f Trying family `National Semiconductor/ITE'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Nuvoton/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 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): 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): 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 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-piix4' for device 0000:00:01.3: Intel 82371AB PIIX4 ACPI Sorry, no sensors were detected. Either your system has no sensors, or they are not supported, or they are connected to an I2C or SMBus adapter that is not supported. If you find out what chips are on your board, check https://hwmon.wiki.kernel.org/device_support_status for driver status.