Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionOndrej Mosnacek
2023-05-11 07:57:28 UTC
Description of problem:
Somewhere between RHEL-9.1 and RHEL-9.2 perf became unable to print function names in kernel stack traces from events on aarch64 unless kernel-debuginfo is installed. On RHEL-9.1 and also on all other arches on RHEL-9.2/9.3 it is able to infer the function names without it (presumably using /proc/kallsyms).
The issue also appears when I boot a RHEL-9.2 kernel on RHEL-9.1 userspace, so it seems to be a regression in the kernel rather than the userspace tools/libraries.
Version-Release number of selected component (if applicable):
Last known good: kernel-5.14.0-162.23.1.el9_1.aarch64
First known bad: kernel-5.14.0-284.14.1.el9_2.aarch64
How reproducible:
Always.
Steps to Reproduce:
1. perf record -g sleep 1
2. perf script
Actual results:
perf-exec 21437 257.001297: 1 cycles:
ffffa2362e8ce7d0 [unknown] ([unknown])
ffffa2362e9f90e0 [unknown] ([unknown])
ffffa2362ea6a728 [unknown] ([unknown])
ffffa2362e9f6714 [unknown] ([unknown])
ffffa2362e9f785c [unknown] ([unknown])
ffffa2362e9f7fc4 [unknown] ([unknown])
ffffa2362e9f80b0 [unknown] ([unknown])
ffffa2362e9f84e8 [unknown] ([unknown])
ffffa2362e9f85bc [unknown] ([unknown])
ffffa2362e67636c [unknown] ([unknown])
ffffa2362e676514 [unknown] ([unknown])
ffffa2362e67654c [unknown] ([unknown])
ffffa2362f279348 [unknown] ([unknown])
ffffa2362f279cb4 [unknown] ([unknown])
ffffa2362e6615c0 [unknown] ([unknown])
ffff8147c9cc [unknown] ([unknown])
[...]
Expected results:
perf-exec 21046 143.835852: 1 cycles:
ffffb7d2558f43a0 perf_event_remove_on_exec+0x0 ([kernel.kallsyms])
ffffb7d255a02614 begin_new_exec+0x2e4 ([kernel.kallsyms])
ffffb7d255a73ae0 load_elf_binary+0x65c ([kernel.kallsyms])
ffffb7d2559ffb34 search_binary_handler+0xd4 ([kernel.kallsyms])
ffffb7d255a0191c exec_binprm+0x5c ([kernel.kallsyms])
ffffb7d255a01c24 bprm_execve.part.0+0x184 ([kernel.kallsyms])
ffffb7d255a01d10 bprm_execve+0x60 ([kernel.kallsyms])
ffffb7d255a01ec4 do_execveat_common+0x184 ([kernel.kallsyms])
ffffb7d255a01f90 __arm64_sys_execve+0x3c ([kernel.kallsyms])
ffffb7d2556a65cc invoke_syscall.constprop.0+0x7c ([kernel.kallsyms])
ffffb7d2556a6774 el0_svc_common.constprop.0+0x154 ([kernel.kallsyms])
ffffb7d2556a67ac do_el0_svc+0x2c ([kernel.kallsyms])
ffffb7d25625c648 el0_svc+0x38 ([kernel.kallsyms])
ffffb7d25625cf9c el0t_64_sync_handler+0x9c ([kernel.kallsyms])
ffffb7d2556915c0 el0t_64_sync+0x174 ([kernel.kallsyms])
ffffaf9cc9cc [unknown] ([unknown])
[...]
perf-5.14.0-340.el9.aarch64 works OK, so RHEL-9.3 solves this problem
Comment 3RHEL Program Management
2023-09-25 16:44:59 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 4RHEL Program Management
2023-09-25 16:46:02 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Description of problem: Somewhere between RHEL-9.1 and RHEL-9.2 perf became unable to print function names in kernel stack traces from events on aarch64 unless kernel-debuginfo is installed. On RHEL-9.1 and also on all other arches on RHEL-9.2/9.3 it is able to infer the function names without it (presumably using /proc/kallsyms). The issue also appears when I boot a RHEL-9.2 kernel on RHEL-9.1 userspace, so it seems to be a regression in the kernel rather than the userspace tools/libraries. Version-Release number of selected component (if applicable): Last known good: kernel-5.14.0-162.23.1.el9_1.aarch64 First known bad: kernel-5.14.0-284.14.1.el9_2.aarch64 How reproducible: Always. Steps to Reproduce: 1. perf record -g sleep 1 2. perf script Actual results: perf-exec 21437 257.001297: 1 cycles: ffffa2362e8ce7d0 [unknown] ([unknown]) ffffa2362e9f90e0 [unknown] ([unknown]) ffffa2362ea6a728 [unknown] ([unknown]) ffffa2362e9f6714 [unknown] ([unknown]) ffffa2362e9f785c [unknown] ([unknown]) ffffa2362e9f7fc4 [unknown] ([unknown]) ffffa2362e9f80b0 [unknown] ([unknown]) ffffa2362e9f84e8 [unknown] ([unknown]) ffffa2362e9f85bc [unknown] ([unknown]) ffffa2362e67636c [unknown] ([unknown]) ffffa2362e676514 [unknown] ([unknown]) ffffa2362e67654c [unknown] ([unknown]) ffffa2362f279348 [unknown] ([unknown]) ffffa2362f279cb4 [unknown] ([unknown]) ffffa2362e6615c0 [unknown] ([unknown]) ffff8147c9cc [unknown] ([unknown]) [...] Expected results: perf-exec 21046 143.835852: 1 cycles: ffffb7d2558f43a0 perf_event_remove_on_exec+0x0 ([kernel.kallsyms]) ffffb7d255a02614 begin_new_exec+0x2e4 ([kernel.kallsyms]) ffffb7d255a73ae0 load_elf_binary+0x65c ([kernel.kallsyms]) ffffb7d2559ffb34 search_binary_handler+0xd4 ([kernel.kallsyms]) ffffb7d255a0191c exec_binprm+0x5c ([kernel.kallsyms]) ffffb7d255a01c24 bprm_execve.part.0+0x184 ([kernel.kallsyms]) ffffb7d255a01d10 bprm_execve+0x60 ([kernel.kallsyms]) ffffb7d255a01ec4 do_execveat_common+0x184 ([kernel.kallsyms]) ffffb7d255a01f90 __arm64_sys_execve+0x3c ([kernel.kallsyms]) ffffb7d2556a65cc invoke_syscall.constprop.0+0x7c ([kernel.kallsyms]) ffffb7d2556a6774 el0_svc_common.constprop.0+0x154 ([kernel.kallsyms]) ffffb7d2556a67ac do_el0_svc+0x2c ([kernel.kallsyms]) ffffb7d25625c648 el0_svc+0x38 ([kernel.kallsyms]) ffffb7d25625cf9c el0t_64_sync_handler+0x9c ([kernel.kallsyms]) ffffb7d2556915c0 el0t_64_sync+0x174 ([kernel.kallsyms]) ffffaf9cc9cc [unknown] ([unknown]) [...]