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.
Comment 13fj-lsoft-rh-dump
2022-05-17 08:20:52 UTC
I tried to check this issue on RHEL9.0 RC system using the following packages but it looks everything works fine.
# rpm -q kernel crash crash-trace-command
kernel-5.14.0-70.13.1.el9_0.x86_64
crash-8.0.0-6.el9.x86_64
crash-trace-command-3.0-6.el9.x86_64
Could you give us more information about the issue?
Thanks.
HATAYAMA, Daisuke
Hi FJ,
FYI, This issue was reported against below versions:
RHEL-9.0.0-20211201.0
- crash-8.0.0-1(gdb-10.2)
- trace-cmd-2.9.2-8.el9
- libtraceevent-1.1.1-7.el9 (manually install)
- libtracecmd-0-8.el9
Steps to Reproduce:
1. generate a normal vmcore
2. install the mentioned crash plugins
3. # crash -i crash.cmd vmlinux vmcore
# cat crash.cmd
extend trace.so
help trace
trace dump
ls dump_tracing_dir/*
trace dump -m /mnt/testarea/DUMP_M
ls /mnt/testarea/DUMP_M/*
trace show | head
trace show -f nocontext_info | head
trace show -f context_info | head
trace show -f sym_offset | head
trace show -f nosym_offset | head
trace show -f sym_addr | head
trace show -f nosym_addr | head
trace show -f nograph_print_duration | head
trace show -f graph_print_duration | head
trace show -f nograph_print_overhead | head
trace show -f graph_print_overhead | head
trace show -f graph_print_abstime | head
trace show -f nograph_print_abstime | head
trace show -f nograph_print_cpu | head
trace show -f graph_print_cpu | head
trace show -f graph_print_proc | head
trace show -f nograph_print_proc | head
trace show -f graph_print_overrun | head
trace show -f nograph_print_overrun | head
trace show -c 0 | head
extend -u trace.so
exit
Comment 15fj-lsoft-rh-dump
2022-05-17 12:55:53 UTC
Probably, the issue was already fixed at crash 8.0.0-3:
# LANG=C rpm -q --changelog crash
...snip...
* Mon Dec 13 2021 Lianbo Jiang <lijiang> - 8.0.0-3
- Fix segmentation fault caused by crash extension modules
- Support the overflow stack exception handling on aarch64
The corresponding commit at the upstream is:
defs.h: fix breakage of compatibility of struct symbol_table_data for extension modules
https://github.com/crash-utility/crash/commit/6968345893178d2750b8872055498d2a6010a861
Please try the latest version of crash utility.
Thanks.
HATAYAMA, Daisuke
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (new packages: crash), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2022:2479
> Could you give us more information about the issue?
>
Sorry for the late reply, HATAYAMA.
I worked on other issues and just saw your message. Seem that you have discussed with Jie and got the answer.
I tried to check this issue on RHEL9.0 RC system using the following packages but it looks everything works fine. # rpm -q kernel crash crash-trace-command kernel-5.14.0-70.13.1.el9_0.x86_64 crash-8.0.0-6.el9.x86_64 crash-trace-command-3.0-6.el9.x86_64 Could you give us more information about the issue? Thanks. HATAYAMA, Daisuke