| Summary: | sensors-detect reports 'mmap: Invalid argument' error for supported architectures | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Rachel Sibley <rasibley> |
| Component: | lm_sensors | Assignee: | Martin Sehnoutka <msehnout> |
| Status: | CLOSED DUPLICATE | QA Contact: | Rachel Sibley <rasibley> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.3 | Keywords: | Regression |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-09-07 19:01:45 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: | |
Looks like this is related to the selinux-policy bug, marking as a dup of 1372200 *** This bug has been marked as a duplicate of bug 1372200 *** |
Description of problem: sensors-detect reports 'mmap: Invalid argument' error for supported architectures, I am not seeing this error on an unsupported arch such as aarch64. This error can be seen when installing the lm_sensors pkg as well as running sensors-detect. Version-Release number of selected component (if applicable): # rpm -q lm_sensors lm_sensors-3.4.0-4.20160601gitf9185e5.el7.x86_64 How reproducible: Always Steps to Reproduce: 1. yum install -y lm_sensors 2. sensors-detect 3. Actual results: # yum install -y lm_sensors <snip> --> Running transaction check ---> Package lm_sensors.x86_64 0:3.4.0-4.20160601gitf9185e5.el7 will be installed --> Processing Dependency: lm_sensors-libs = 3.4.0-4.20160601gitf9185e5.el7 for package: lm_sensors-3.4.0-4.20160601gitf9185e5.el7.x86_64 --> Processing Dependency: libsensors.so.4()(64bit) for package: lm_sensors-3.4.0-4.20160601gitf9185e5.el7.x86_64 --> Running transaction check ---> Package lm_sensors-libs.x86_64 0:3.4.0-4.20160601gitf9185e5.el7 will be installed --> Finished Dependency Resolution Dependencies Resolved ============================================================================================================================================================================= Package Arch Version Repository Size ============================================================================================================================================================================= Installing: lm_sensors x86_64 3.4.0-4.20160601gitf9185e5.el7 beaker-Server 139 k Installing for dependencies: lm_sensors-libs x86_64 3.4.0-4.20160601gitf9185e5.el7 beaker-Server 40 k Transaction Summary ============================================================================================================================================================================= Install 1 Package (+1 Dependent package) <snip> Transaction test succeeded Running transaction mmap: Invalid argument <---------------------------------- Installing : lm_sensors-libs-3.4.0-4.20160601gitf9185e5.el7.x86_64 1/2 Installing : lm_sensors-3.4.0-4.20160601gitf9185e5.el7.x86_64 2/2 Verifying : lm_sensors-3.4.0-4.20160601gitf9185e5.el7.x86_64 1/2 Verifying : lm_sensors-libs-3.4.0-4.20160601gitf9185e5.el7.x86_64 2/2 Installed: lm_sensors.x86_64 0:3.4.0-4.20160601gitf9185e5.el7 Dependency Installed: lm_sensors-libs.x86_64 0:3.4.0-4.20160601gitf9185e5.el7 Complete! [root@dell-per815-02 ~]# sensors-detect # sensors-detect revision 3.4.0-4 (2016-06-01) # System: Dell Inc. PowerEdge R815 # Board: Dell Inc. 06JC9T # Kernel: 3.10.0-501.el7.x86_64 x86_64 # Processor: AMD Opteron(tm) Processor 6168 (16/9/1) 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 Family 10h thermal sensors... Success! (driver `k10temp') 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): Probing for Super-I/O at 0x2e/0x2f Trying family `National Semiconductor/ITE'... No Trying family `SMSC'... Yes Found `SMSC EMC2700LPC Super IO' (no information available) 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): Found `IPMI BMC KCS' at 0xca8... 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): 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:14.0: ATI Technologies Inc SB600/SB700/SB800 SMBus Module i2c-dev loaded successfully. mmap: Invalid argument <------------------------------------ Next adapter: mga i2c (i2c-0) Do you want to scan it? (yes/NO/selectively): Next adapter: SMBus PIIX4 adapter at 0900 (i2c-1) Do you want to scan it? (YES/no/selectively): Next adapter: SMBus PIIX4 adapter at 0920 (i2c-2) Do you want to scan it? (YES/no/selectively): Now follows a summary of the probes I have just done. Just press ENTER to continue: Driver `to-be-written': * ISA bus, address 0xca8 Chip `IPMI BMC KCS' (confidence: 8) Driver `k10temp' (autoloaded): * Chip `AMD Family 10h thermal sensors' (confidence: 9) 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 'mmap: Invalid argument' errors generated Additional info: Seen on systems with both coretemp and k10temp drivers