RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1318002 - lm_sensors sensors-detect command causes kernel panic on APM X-gene1 machines (Gigabyte MP30-AR0 and Mustang)
Summary: lm_sensors sensors-detect command causes kernel panic on APM X-gene1 machines...
Keywords:
Status: CLOSED DUPLICATE of bug 1261659
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: kernel-aarch64
Version: 7.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Linda Wang
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-15 18:03 UTC by Richard W.M. Jones
Modified: 2016-03-16 19:21 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-16 19:21:20 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Richard W.M. Jones 2016-03-15 18:03:54 UTC 
Description of problem:

Running the 'sensors-detect' command causes a kernel panic.

Version-Release number of selected component (if applicable):

  lm_sensors-3.3.4-11.el7.aarch64
  kernel-4.5.0-0.rc7.31.el7.aarch64

How reproducible:

  100%

Steps to Reproduce:
1. Install lm_sensors.
2. Run sensors-detect command as root.
3.

Actual results:

# sensors-detect 
# sensors-detect revision 6170 (2013-05-20 21:25:22 +0200)
# System: AppliedMicro Mustang [1.0]

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 15h power sensors...                             No
AMD Family 16h power sensors...                             No
Intel digital thermal sensor...                             No
Intel AMB FB-DIMM 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

Message from syslogd@harm at Mar 15 17:55:09 ...
 kernel:Internal error: Oops: 96000047 [#1] SMP

Message from syslogd@harm at Mar 15 17:55:09 ...
 kernel:Process sensors-detect (pid: 1753, stack limit = 0xfffffe7fe46a0020)

Message from syslogd@harm at Mar 15 17:55:09 ...
 kernel:Stack: (0xfffffe7fe46a3d70 to 0xfffffe7fe46a4000)

Message from syslogd@harm at Mar 15 17:55:09 ...
 kernel:3d60:                                   fffffe7fe46a3da0 fffffe0000223588

Message from syslogd@harm at Mar 15 17:55:09 ...
 kernel:3d80: fffffe7fe46a3dc0 fffffe7fe46a3ec8 0000000000000001 000000001080f0f0


In the serial console:

[  475.707212] Unable to handle kernel paging request at virtual address fffffdf
ffae0002e
[  475.715150] pgd = fffffe7ffa8b0000
[  475.718544] [fffffdfffae0002e] *pgd=0000000000000000, *pud=0000000000000000, *pmd=0000000000000000
[  475.727503] Internal error: Oops: 96000047 [#1] SMP
[  475.732355] Modules linked in: xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 tun rpcsec_gss_krb5 ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 ipt_REJECT nf_reject_ipv4 xt_conntrack ebtable_nat ebtable_broute ebtable_filter ebtables ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_security ip6table_raw ip6table_filter ip6_tables iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_security iptable_raw iptable_filter vfat fat sg i2c_xgene_slimpro xgene_rng gpio_xgene_sb gpio_generic br_netfilter bridge stp llc nfsd ip_tables xfs libcrc32c ast i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops ttm drm i2c_core sdhci_acpi sdhci mmc_core ahci_xgene libahci_platform dm_mirror dm_region_hash dm_log dm_mod
[  475.803608] CPU: 0 PID: 1753 Comm: sensors-detect Not tainted 4.5.0-0.rc7.31.el7.aarch64 #1
[  475.811915] Hardware name: AppliedMicro Mustang/Mustang, BIOS 1.1.0 Jan 26 2016
[  475.819186] task: fffffe7fe4aaf680 ti: fffffe7fe46a0000 task.ti: fffffe7fe46a0000
[  475.826633] PC is at write_port+0x88/0xf0
[  475.830622] LR is at __vfs_write+0x48/0x104
[  475.834782] pc : [<fffffe00004a68dc>] lr : [<fffffe0000223588>] pstate: 80000145
[  475.842138] sp : fffffe7fe46a3d70
[  475.845434] x29: fffffe7fe46a3d70 x28: fffffe7fe46a0000
[  475.850737] x27: fffffe0000772000 x26: 0000000000000040
[  475.856038] x25: 000000000000011e x24: 0000000000000015
[  475.861341] x23: 0000000060000000 x22: 000000001080f0f0
[  475.866643] x21: fffffe7fe46a3ec8 x20: 0000000000000001
[  475.871944] x19: fffffe7fe1218700 x18: 000003ffd2fda3f0
[  475.877247] x17: 000003ff862df050 x16: fffffe0000224e00
[  475.882548] x15: 0000000000000002 x14: 0000000000000000
[  475.887849] x13: ffffffffffffffff x12: 0000000000000000
[  475.893151] x11: 0000000000000000 x10: 0000000000000001
[  475.898452] x9 : 000003ff8668f000 x8 : fffffdfffae0002e
[  475.903753] x7 : 0000000000000000 x6 : 000000000000002e
[  475.909057] x5 : fffffdfffae0002e x4 : 0000000000000000
[  475.914361] x3 : fffffe7fe46a3ec8 x2 : 00000000000000aa
[  475.919666] x1 : 000000001080f0f0 x0 : 000000001080f0f0
[  475.924971]
[  475.926452] Process sensors-detect (pid: 1753, stack limit = 0xfffffe7fe46a0020)
[  475.933809] Stack: (0xfffffe7fe46a3d70 to 0xfffffe7fe46a4000)
[  475.939524] 3d60:                                   fffffe7fe46a3da0 fffffe0000223588
[  475.947313] 3d80: fffffe7fe46a3dc0 fffffe7fe46a3ec8 0000000000000001 000000001080f0f0
[  475.955102] 3da0: fffffe7fe46a3e30 fffffe000022430c fffffe7fe1218700 0000000000000001
[  475.962890] 3dc0: fffffe7fe46a3ec8 000000001080f0f0 0000000000000001 fffffe7fe1218700
[  475.970679] 3de0: 0000000000000001 000000001080f0f0 fffffe7fe46a3e30 fffffe00002242dc
[  475.978468] 3e00: fffffe7fe1218700 0000000000000001 fffffe7fe46a3ec8 fffffe000014dd7c
[  475.986256] 3e20: fffffe7fe46a3e50 fffffe7fe46a3ec8 fffffe7fe46a3e80 fffffe0000224e54
[  475.994045] 3e40: fffffe7fe1218700 fffffe7fe1218700 ffffffffffffffff 000003ff862df028
[  476.001834] 3e60: 0000000060000000 fffffe0000224e2c 0000000000000003 fffffe7fe46a0000
[  476.009623] 3e80: 0000000000000000 fffffe0000083a8c 0000000000000200 000000001043ec98
[  476.017411] 3ea0: ffffffffffffffff fffffe0000083a5c 0000000000000001 000000001080f0f0
[  476.025200] 3ec0: ffffffffffffffff 000000000000002e 0000000000000003 000000001080f0f0
[  476.032989] 3ee0: 0000000000000001 000003ff8662c750 0000000010400010 0000000000000000
[  476.040778] 3f00: 1bad5e281129b200 0000000000000000 0000000000000040 000003ff8668f000
[  476.048566] 3f20: 0000000000000001 0000000000000000 0000000000000000 ffffffffffffffff
[  476.056355] 3f40: 0000000000000000 0000000000000002 0000000000000000 000003ff862df050
[  476.064144] 3f60: 000003ffd2fda3f0 0000000010400010 000000001043ec98 0000000000000000
[  476.071933] 3f80: 000003ff8668f000 00000000105e8bb8 000000001043ecb0 00000000105e8e40
[  476.079722] 3fa0: 0000000000000001 0000000000000001 000000001080f0f0 000003ffd2fda5e0
[  476.087510] 3fc0: 000003ff86601ac8 000003ffd2fda5e0 000003ff862df028 0000000060000000
[  476.095299] 3fe0: 0000000000000003 0000000000000040 0000000000000000 0000000000000000
[  476.103087] Call trace:
[  476.105520] Exception stack(0xfffffe7fe46a3bb0 to 0xfffffe7fe46a3cd0)
[  476.111926] 3ba0:                                   fffffe7fe1218700 0000000000000001
[  476.119715] 3bc0: fffffe7fe46a3d70 fffffe00004a68dc 0000000000000002 fffffc00546722b0
[  476.127503] 3be0: fffffe7fe46a3c00 fffffe000047e9dc fffffe7ff9e93600 fffffe00007cecb8
[  476.135292] 3c00: fffffe7fe46a3c20 fffffe00004808d0 0000000000000000 000000000000000a
[  476.143080] 3c20: fffffe7fe46a3c60 fffffe0000478b10 fffffe7fe46a3c60 fffffe00000f79a0
[  476.150869] 3c40: fffffe7fe44cd230 fffffe00000f7994 000000001080f0f0 000000001080f0f0
[  476.158658] 3c60: 00000000000000aa fffffe7fe46a3ec8 0000000000000000 fffffdfffae0002e
[  476.166446] 3c80: 000000000000002e 0000000000000000 fffffdfffae0002e 000003ff8668f000
[  476.174235] 3ca0: 0000000000000001 0000000000000000 0000000000000000 ffffffffffffffff
[  476.182023] 3cc0: 0000000000000000 0000000000000002
[  476.186875] [<fffffe00004a68dc>] write_port+0x88/0xf0
[  476.191898] [<fffffe0000223588>] __vfs_write+0x48/0x104
[  476.197095] [<fffffe000022430c>] vfs_write+0x98/0x198
[  476.202121] [<fffffe0000224e54>] SyS_write+0x54/0xb0
[  476.207060] [<fffffe0000083a8c>] __sys_trace_return+0x0/0x4
[  476.212603] Code: aa0103e0 52800007 1400000a d5033e9f (390000a2)
[  476.218686] ---[ end trace b81b23d96fb04919 ]---
[  476.223295] Kernel panic - not syncing: Fatal exception

(There are several pages more of exceptions but that is the
first one)

Additional info:

This was originally reported by Gordon Bobic
https://lists.centos.org/pipermail/arm-dev/2016-March/001843.html
I reproduced it on RHELSA
Comment 2 Marcin Juszkiewicz 2016-03-15 18:27:11 UTC 
[root@pinkiepie ~]# sensors-detect 
# sensors-detect revision 6170 (2013-05-20 21:25:22 +0200)
# System: AppliedMicro Mustang [1.0]

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 15h power sensors...                             No
AMD Family 16h power sensors...                             No
Intel digital thermal sensor...                             No
Intel AMB FB-DIMM 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
[   71.580770] Unable to handle kernel paging request at virtual address fffffdfffae0002e
[   71.591814] pgd = fffffe035bc00000
[   71.595231] [fffffdfffae0002e] *pgd=0000000000000000, *pud=0000000000000000, *pmd=0000000000000000
[   71.604265] Internal error: Oops: 96000047 [#1] SMP
[   71.609151] Modules linked in: ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 ipt_REJECT nf_reject_ipv4 xt_conntrack ebtable_nat ebtable_brout
e bridge stp llc ebtable_filter ebtables ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_security ip6tab
le_raw ip6table_filter ip6_tables iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_secur
ity iptable_raw iptable_filter dm_mirror dm_region_hash dm_log dm_mod vfat fat snd_hda_codec_hdmi snd_hda_intel snd_hda_codec snd_hda_core 
snd_hwdep snd_seq snd_seq_device snd_pcm snd_timer snd soundcore sdhci_acpi sdhci mmc_core sg xgene_rng gpio_xgene_sb gpio_generic ip_table
s ext4 mbcache jbd2 uas usb_storage radeon i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops ttm drm i2c_core ahci_
xgene libahci_platform realtek(E)
[   71.685757] CPU: 4 PID: 2481 Comm: sensors-detect Tainted: G            E   4.5.0-0.rc7.31.el7.aarch64 #1
[   71.695338] Hardware name: AppliedMicro Mustang/Mustang, BIOS 1.1.0 Oct 20 2015
[   71.702658] task: fffffe0358620000 ti: fffffe035d500000 task.ti: fffffe035d500000
[   71.710157] PC is at write_port+0x88/0xf0
[   71.714175] LR is at __vfs_write+0x48/0x104
[   71.718364] pc : [<fffffe00004a68dc>] lr : [<fffffe0000223588>] pstate: 80000145
[   71.725771] sp : fffffe035d503d70
[   71.729089] x29: fffffe035d503d70 x28: fffffe035d500000 
[   71.734434] x27: fffffe0000772000 x26: 0000000000000040 
[   71.739779] x25: 000000000000011e x24: 0000000000000015 
[   71.745123] x23: 0000000060000000 x22: 0000000031fea5d0 
[   71.750466] x21: fffffe035d503ec8 x20: 0000000000000001 
[   71.755810] x19: fffffe035d686900 x18: 000003fffc7b8430 
[   71.761155] x17: 000003ff8b78f050 x16: fffffe0000224e00 
[   71.766499] x15: 0000000000000002 x14: 0000000000000000 
[   71.771842] x13: ffffffffffffffff x12: 0000000000000000 
[   71.777185] x11: 0000000000000000 x10: 0000000000000001 
[   71.782529] x9 : 000003ff8bb3f000 x8 : fffffdfffae0002e 
[   71.787874] x7 : 0000000000000000 x6 : 000000000000002e 
[   71.793219] x5 : fffffdfffae0002e x4 : 0000000000000000 
[   71.798562] x3 : fffffe035d503ec8 x2 : 00000000000000aa 
[   71.803906] x1 : 0000000031fea5d0 x0 : 0000000031fea5d0 
[   71.809250] 
[   71.810742] Process sensors-detect (pid: 2481, stack limit = 0xfffffe035d500020)
[   71.818149] Stack: (0xfffffe035d503d70 to 0xfffffe035d504000)
[   71.823904] 3d60:                                   fffffe035d503da0 fffffe0000223588
[   71.833424] 3d80: fffffe035d503dc0 fffffe035d503ec8 0000000000000001 0000000031fea5d0
[   71.842960] 3da0: fffffe035d503e30 fffffe000022430c fffffe035d686900 0000000000000001
[   71.852493] 3dc0: fffffe035d503ec8 0000000031fea5d0 0000000000000001 fffffe035d686900
[   71.862033] 3de0: 0000000000000001 0000000031fea5d0 fffffe035d503e30 fffffe00002242dc
[   71.871555] 3e00: fffffe035d686900 0000000000000001 fffffe035d503ec8 fffffe000014dd7c
[   71.881057] 3e20: fffffe035d503e50 fffffe035d503ec8 fffffe035d503e80 fffffe0000224e54
[   71.890571] 3e40: fffffe035d686900 fffffe035d686900 ffffffffffffffff 000003ff8b78f028
[   71.900109] 3e60: 0000000060000000 fffffe0000224e2c 0000000000000003 fffffe035d500000
[   71.909677] 3e80: 0000000000000000 fffffe0000083a8c 0000000000000200 0000000031c1e2c8
[   71.919235] 3ea0: ffffffffffffffff fffffe0000083a5c 0000000000000001 0000000031fea5d0
[   71.928770] 3ec0: ffffffffffffffff 000000000000002e 0000000000000003 0000000031fea5d0
[   71.938272] 3ee0: 0000000000000001 000003ff8badc750 0000000031be0010 0000000000000000
[   71.947758] 3f00: b40da5a5da382000 0000000000000000 0000000000000040 000003ff8bb3f000
[   71.957222] 3f20: 0000000000000001 0000000000000000 0000000000000000 ffffffffffffffff
[   71.966659] 3f40: 0000000000000000 0000000000000002 0000000000000000 000003ff8b78f050
[   71.976046] 3f60: 000003fffc7b8430 0000000031be0010 0000000031c1e2c8 0000000000000000
[   71.985386] 3f80: 000003ff8bb3f000 0000000031dc7978 0000000031c1e2e0 0000000031dc7c00
[   71.994671] 3fa0: 0000000000000001 0000000000000001 0000000031fea5d0 000003fffc7b8620
[   72.003910] 3fc0: 000003ff8bab1ac8 000003fffc7b8620 000003ff8b78f028 0000000060000000
[   72.013110] 3fe0: 0000000000000003 0000000000000040 0000000000000000 000000000000ca70
[   72.022263] Call trace:
[   72.026001] Exception stack(0xfffffe035d503bb0 to 0xfffffe035d503cd0)
[   72.033713] 3ba0:                                   fffffe035d686900 0000000000000001
[   72.042801] 3bc0: fffffe035d503d70 fffffe00004a68dc fffffe035d503c00 fffffe0000495664
[   72.051880] 3be0: 0000000000000000 fffffe0000495658 0000000000000000 0000000000000140
[   72.060950] 3c00: fffffe035d503c20 fffffe0000495508 fffffe035d503c40 fffffe0000495558
[   72.070034] 3c20: fffffe000135bae8 fffffe000049554c fffffe035d503c60 fffffe00000f79a0
[   72.079091] 3c40: fffffe0356636a30 fffffe00000f7994 0000000031fea5d0 0000000031fea5d0
[   72.088141] 3c60: 00000000000000aa fffffe035d503ec8 0000000000000000 fffffdfffae0002e
[   72.097206] 3c80: 000000000000002e 0000000000000000 fffffdfffae0002e 000003ff8bb3f000
[   72.106284] 3ca0: 0000000000000001 0000000000000000 0000000000000000 ffffffffffffffff
[   72.115371] 3cc0: 0000000000000000 0000000000000002
[   72.121515] [<fffffe00004a68dc>] write_port+0x88/0xf0
[   72.127837] [<fffffe0000223588>] __vfs_write+0x48/0x104
[   72.134335] [<fffffe000022430c>] vfs_write+0x98/0x198
[   72.140656] [<fffffe0000224e54>] SyS_write+0x54/0xb0
[   72.146885] [<fffffe0000083a8c>] __sys_trace_return+0x0/0x4
[   72.153728] Code: aa0103e0 52800007 1400000a d5033e9f (390000a2) 
[   72.161189] Starting crashdump kernel...
[   72.167639] Bye!
[    0.000000] Booting Linux on physical CPU 0x200
[    0.000000] Linux version 4.5.0-0.rc7.31.el7.aarch64 (mockbuild.eng.bos.redhat.com) (gcc version 4.8.5 20150623 (Red Hat
 4.8.5-4) (GCC) ) #1 SMP Tue Mar 8 13:10:54 EST 2016
[    0.000000] Boot CPU: AArch64 Processor [500f0000]
[    0.000000] Memory limited to 2048MB
Comment 3 Marcin Juszkiewicz 2016-03-15 18:30:22 UTC 
Rawhide on Mustang (device tree mode) works:

# sensors-detect revision 6284 (2015-05-31 14:00:33 +0200)
# System: AppliedMicro Mustang [1.0]
# Kernel: 4.5.0-0.rc7.git0.2.fc24.aarch64 aarch64
# Processor:  (//)

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): 
modprobe: FATAL: Module cpuid not found in directory /lib/modules/4.5.0-0.rc7.git0.2.fc24.aarch64
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): 
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): 
Sorry, no supported PCI bus adapters found.

Next adapter: Radeon i2c bit bus 0x90 (i2c-0)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: Radeon i2c bit bus 0x91 (i2c-1)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: Radeon i2c bit bus 0x92 (i2c-2)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: Radeon i2c bit bus 0x93 (i2c-3)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: Radeon i2c bit bus 0x94 (i2c-4)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: Radeon i2c bit bus 0x95 (i2c-5)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: Radeon i2c bit bus 0x96 (i2c-6)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: Radeon i2c bit bus 0x97 (i2c-7)
Do you want to scan it? (yes/NO/selectively): 

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
http://www.lm-sensors.org/wiki/Devices for driver status.
Comment 4 Marcin Juszkiewicz 2016-03-15 18:40:13 UTC 
Works on mustang/rawhide/acpi as well.
Comment 5 Richard W.M. Jones 2016-03-15 19:22:15 UTC 
FWIW I'm using ACPI on the Gigabyte board.  Do we expect lm_sensors to
work?  It's a RHEL(SA) package.
Comment 8 Richard W.M. Jones 2016-03-15 21:56:56 UTC 
Original reporter says this affects the following CentOS packages:

Kernels I tried are:
CentOS supplied:
 4.2.0-0.21.el7.1
 4.2.0-0.26.el7.1
Self-built:
 4.4.5
 4.5.0

lm_sensors:
CentOS supplied:
3.3.4-11.el7
Comment 10 Richard W.M. Jones 2016-03-16 17:53:53 UTC 
FWIW the same thing happens with kernel-4.2.0-0.21.el7.aarch64.
Comment 12 Jeff Bastian 2016-03-16 19:21:20 UTC 
This was reported earlier in bug 1261659, although it was marked private so it may not have appeared if searching for this issue.  I've opened that bug up and I'll close this one as a duplicate.

*** This bug has been marked as a duplicate of bug 1261659 ***
Note You need to log in before you can comment on or make changes to this bug.