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 1327759 - Kernel panic on ARM64 when running sensors-detect
Summary: Kernel panic on ARM64 when running sensors-detect
Keywords:
Status: CLOSED DUPLICATE of bug 1261659
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: kernel-aarch64
Version: 7.3
Hardware: aarch64
OS: Linux
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-04-15 21:12 UTC by Jiri Hladky
Modified: 2016-04-18 12:09 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-04-18 12:09:32 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
vmcore-dmesg.txt (41.46 KB, text/plain)
2016-04-15 21:12 UTC, Jiri Hladky
no flags Details
4.5.0-0.33.el7.aarch64_vmcore-dmesg.txt (30.89 KB, text/plain)
2016-04-15 21:54 UTC, Jiri Hladky
no flags Details

Description Jiri Hladky 2016-04-15 21:12:25 UTC
Created attachment 1147778 [details]
vmcore-dmesg.txt

Description of problem:

Kernel panic on ARM64 when running sensors-detect

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

uname -a
Linux amd-seattle-05.lab.eng.rdu.redhat.com 4.2.0-0.21.el7.aarch64 #1 SMP Tue Oct 6 15:59:59 EDT 2015 aarch64 aarch64 aarch64 GNU/Linux

How reproducible:

Use one of amd-seattle systems in lab.eng.rdu.redhat.com

Steps to Reproduce:
1. yum -y install lm_sensors
2. sensors-detect

Actual results:

Kernel panic

[  514.560078] Unable to handle kernel paging request at virtual address fffffdfffae0002e
[  514.568005] pgd = fffffe00175a0000
[  514.571397] [fffffdfffae0002e] *pgd=0000000000000000, *pud=0000000000000000, *pmd=0000000000000000
[  514.580366] Internal error: Oops: 96000047 [#1] SMP
[  514.585234] Modules linked in: vfat fat aes_ce_blk ablk_helper cryptd aes_ce_cipher ipmi_ssif ghash_ce i2c_core sha2_ce sha1_ce ipmi_si ipmi_msghandler sg ccp hed nfsd ip_tables xfs libcrc32c dm_mirror dm_region_hash dm_log dm_mod
[  514.605708] CPU: 2 PID: 17989 Comm: sensors-detect Not tainted 4.2.0-0.21.el7.aarch64 #1
[  514.613789] Hardware name: Default string Default string/Default string, BIOS ROD0083B 07/17/2015
[  514.622651] task: fffffe0354959c80 ti: fffffe0359030000 task.ti: fffffe0359030000
[  514.630128] PC is at write_port+0xac/0xf4
[  514.634130] LR is at __vfs_write+0x48/0x130
[  514.638302] pc : [<fffffe0000486804>] lr : [<fffffe000021cabc>] pstate: 80000145
[  514.645687] sp : fffffe0359033d70
[  514.648990] x29: fffffe0359033d70 x28: fffffe0359030000 
[  514.654300] x27: fffffe0000772000 x26: 0000000000000040 
[  514.659608] x25: 000000000000011a x24: 0000000000000015 
[  514.664915] x23: 0000000060000000 x22: 000000002d6dd6d0 
[  514.670223] x21: fffffe0359033ec8 x20: 0000000000000001 
[  514.675530] x19: fffffe0358dc9200 x18: 000003ffcc64bf10 
[  514.680837] x17: 000003ffa88cf030 x16: fffffe000021dbd0 
[  514.686144] x15: 0000000000000002 x14: 0000000000000000 
[  514.691451] x13: ffffffffffffffff x12: 0000000000000000 
[  514.696757] x11: 0000000000000000 x10: 0000000000000001 
[  514.702064] x9 : 0000000000000000 x8 : 000000002d6dd6a2 
[  514.707371] x7 : 0000000000000000 x6 : 00000000000000aa 
[  514.712679] x5 : fffffdfffae0002e x4 : 000000000000002f 
[  514.717985] x3 : fffffe0359033ec8 x2 : 000000000000002f 
[  514.723293] x1 : 000000002d6dd6d0 x0 : 000000000000ffff 
[  514.728599] 
[  514.730083] Process sensors-detect (pid: 17989, stack limit = 0xfffffe0359030020)
[  514.737561] Stack: (0xfffffe0359033d70 to 0xfffffe0359034000)
[  514.743300] 3d60:                                     59033da0 fffffe03 0021cabc fffffe00
[  514.751474] 3d80: 59033d90 fffffe03 59033ec8 fffffe03 00000001 00000000 2d6dd6d0 00000000
[  514.759646] 3da0: 59033e30 fffffe03 0021d328 fffffe00 58dc9200 fffffe03 00000001 00000000
[  514.767819] 3dc0: 59033ec8 fffffe03 2d6dd6d0 00000000 00000001 00000000 58dc9200 fffffe03
[  514.775992] 3de0: 00000001 00000000 2d6dd6d0 00000000 59033e30 fffffe03 0021d2f8 fffffe00
[  514.784165] 3e00: 58dc9200 fffffe03 00000001 00000000 59033ec8 fffffe03 00154bbc fffffe00
[  514.792337] 3e20: 59033e50 fffffe03 59033ec8 fffffe03 59033e80 fffffe03 0021dc24 fffffe00
[  514.800509] 3e40: 58dc9200 fffffe03 58dc9200 fffffe03 ffffffff ffffffff a88cf008 000003ff
[  514.808682] 3e60: 60000000 00000000 0021dbfc fffffe00 00000003 00000000 2d301dd8 00000000
[  514.816854] 3e80: cc64c100 000003ff 00091a0c fffffe00 00000200 00000000 2d301dd8 00000000
[  514.825027] 3ea0: ffffffff ffffffff 000919dc fffffe00 00000001 00000000 2d6dd6d0 00000000
[  514.833199] 3ec0: ffffffff ffffffff 0000002e 00000000 00000003 00000000 2d6dd6d0 00000000
[  514.841371] 3ee0: 00000001 00000000 a8c1c750 000003ff 2d2c0010 00000000 00000000 00000000
[  514.849544] 3f00: 9a7ab900 c939d869 00000000 00000000 00000040 00000000 a8c7f000 000003ff
[  514.857716] 3f20: 00000001 00000000 00000000 00000000 00000000 00000000 ffffffff ffffffff
[  514.865888] 3f40: 00000000 00000000 00000002 00000000 00000000 00000000 a88cf030 000003ff
[  514.874061] 3f60: cc64bf10 000003ff 2d2c0010 00000000 2d301dd8 00000000 00000000 00000000
[  514.882233] 3f80: a8c7f000 000003ff 2d4abd50 00000000 2d301df0 00000000 2d4abfd8 00000000
[  514.890405] 3fa0: 00000001 00000000 00000001 00000000 2d6dd6d0 00000000 cc64c100 000003ff
[  514.898578] 3fc0: a8bf1ac8 000003ff cc64c100 000003ff a88cf008 000003ff 60000000 00000000
[  514.906750] 3fe0: 00000003 00000000 00000040 00000000 00000000 00000000 00000000 00000000
[  514.914920] Call Trace:
[  514.917361] [<fffffe0000486804>] write_port+0xac/0xf4
[  514.922405] [<fffffe000021cab8>] __vfs_write+0x44/0x130
[  514.927623] [<fffffe000021d324>] vfs_write+0x98/0x1a8
[  514.932667] [<fffffe000021dc20>] SyS_write+0x50/0xb0
[  514.937624] Code: d5033e9f 92c04005 f2bf5be5 8b050085 (390000a6) 
[  514.943719] CPU4: stopping
[  514.946425] CPU: 4 PID: 17988 Comm: runtest.sh Not tainted 4.2.0-0.21.el7.aarch64 #1
[  514.954164] Hardware name: Default string Default string/Default string, BIOS ROD0083B 07/17/2015
[  514.963030] Call Trace:
[  514.965476] [<fffffe000009739c>] dump_backtrace+0x0/0x170
[  514.970869] [<fffffe000009752c>] show_stack+0x20/0x2c
[  514.975916] [<fffffe00007436f8>] dump_stack+0x78/0x9c
[  514.980961] [<fffffe000009d0c0>] handle_IPI+0x1ac/0x244
[  514.986180] [<fffffe00000904b4>] gic_handle_irq+0x7c/0x84

Comment 2 Jiri Hladky 2016-04-15 21:52:51 UTC
I have reproduced the panic also on latest kernel 4.5.0-0.33.el7.aarch64 :

[root@amd-seattle-05 ~]# uname -a
Linux amd-seattle-05.lab.eng.rdu.redhat.com 4.5.0-0.33.el7.aarch64 #1 SMP Tue Apr 5 12:55:39 EDT 2016 aarch64 aarch64 aarch64 GNU/Linux
    
[root@amd-seattle-05 ~]# (while :; do echo ""; done ) | sensors-detect
# sensors-detect revision 6170 (2013-05-20 21:25:22 +0200)
# System: Default string Default string [Default string]

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

Comment 3 Jiri Hladky 2016-04-15 21:54:44 UTC
Created attachment 1147781 [details]
4.5.0-0.33.el7.aarch64_vmcore-dmesg.txt

Comment 4 Jeff Bastian 2016-04-18 12:09:32 UTC

*** 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.