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.
I have a shot, but it seems that crash works as expected:
.........
Type "show copying" and "show warranty" for details.
This GDB was configured as "aarch64-unknown-linux-gnu".
Type "show configuration" for configuration details.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
KERNEL: /usr/lib/debug/lib/modules/5.14.0-35.el9.aarch64/vmlinux
DUMPFILE: vmcore.strip [PARTIAL DUMP]
CPUS: 224
DATE: Fri Dec 24 01:50:35 EST 2021
UPTIME: 02:11:59
LOAD AVERAGE: 0.00, 0.15, 0.13
TASKS: 2014
NODENAME: hpe-apache-cn99xx-05.khw4.lab.eng.bos.redhat.com
RELEASE: 5.14.0-35.el9.aarch64
VERSION: #1 SMP Tue Dec 21 08:37:30 EST 2021
MACHINE: aarch64 (unknown Mhz)
MEMORY: 15.9 GB
PANIC: "Kernel panic - not syncing: sysrq triggered crash"
PID: 23319
COMMAND: "bash"
TASK: ffff0009ef61c600 [THREAD_INFO: ffff0009ef61c600]
CPU: 204
STATE: TASK_RUNNING (PANIC)
crash> foreach bt
PID: 0 TASK: ffff8000119e1700 CPU: 0 COMMAND: "swapper/0"
#0 [ffff800010003d60] crash_save_cpu at ffff8000101b4384
#1 [ffff800010003f10] do_handle_IPI at ffff800010054af4
#2 [ffff800010003f60] ipi_handler at ffff800010054c84
#3 [ffff800010003f70] handle_percpu_devid_irq at ffff800010161980
#4 [ffff800010003fa0] handle_domain_irq at ffff80001015962c
#5 [ffff800010003fd0] gic_handle_irq at ffff800010040190
--- <IRQ stack> ---
#6 [ffff8000119c3bc0] call_on_irq_stack at ffff800010044db4
#7 [ffff8000119c3bd0] do_interrupt_handler at ffff800010046b68
#8 [ffff8000119c3be0] el1_interrupt at ffff800010c2f8ac
#9 [ffff8000119c3c00] el1h_64_irq_handler at ffff800010c2fc94
#10 [ffff8000119c3d40] el1h_64_irq at ffff800010041348
#11 [ffff8000119c3d60] arch_cpu_idle at ffff800010c30b08
#12 [ffff8000119c3d70] default_idle_call at ffff800010c3d138
#13 [ffff8000119c3d90] cpuidle_idle_call at ffff800010115cf8
#14 [ffff8000119c3dd0] do_idle at ffff800010115e28
#15 [ffff8000119c3e00] cpu_startup_entry at ffff800010116080
#16 [ffff8000119c3e20] rest_init at ffff800010c3147c
#17 [ffff8000119c3e40] arch_call_rest_init at ffff80001155151c
#18 [ffff8000119c3e50] start_kernel at ffff800011551a54
PID: 0 TASK: ffff000803170000 CPU: 1 COMMAND: "swapper/1"
.......
As the message shows, kernel version is "5.14.0-35.el9.aarch64",
machine is hpe-apache-cn99xx-05.khw4.lab.eng.bos.redhat.com
And crash 8.0.0-3.el9.
One thing worth to mention is about the vmcore.strip. It is generated with " makedumpfile -l --message-level 7 -d 31 vmcore vmcore.strip", where vmcore is got by "collector cp"
So could you re-test whether the latest kernel has this issue?
Thanks,
Pingfan
Check on hpe-apache-cn99xx-09.khw4.lab.eng.bos.redhat.com. I can observe the issue now.
With "cp vmcore", this issue can not be observed, so it is a makedumpfile bug.
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
I have a shot, but it seems that crash works as expected: ......... Type "show copying" and "show warranty" for details. This GDB was configured as "aarch64-unknown-linux-gnu". Type "show configuration" for configuration details. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... KERNEL: /usr/lib/debug/lib/modules/5.14.0-35.el9.aarch64/vmlinux DUMPFILE: vmcore.strip [PARTIAL DUMP] CPUS: 224 DATE: Fri Dec 24 01:50:35 EST 2021 UPTIME: 02:11:59 LOAD AVERAGE: 0.00, 0.15, 0.13 TASKS: 2014 NODENAME: hpe-apache-cn99xx-05.khw4.lab.eng.bos.redhat.com RELEASE: 5.14.0-35.el9.aarch64 VERSION: #1 SMP Tue Dec 21 08:37:30 EST 2021 MACHINE: aarch64 (unknown Mhz) MEMORY: 15.9 GB PANIC: "Kernel panic - not syncing: sysrq triggered crash" PID: 23319 COMMAND: "bash" TASK: ffff0009ef61c600 [THREAD_INFO: ffff0009ef61c600] CPU: 204 STATE: TASK_RUNNING (PANIC) crash> foreach bt PID: 0 TASK: ffff8000119e1700 CPU: 0 COMMAND: "swapper/0" #0 [ffff800010003d60] crash_save_cpu at ffff8000101b4384 #1 [ffff800010003f10] do_handle_IPI at ffff800010054af4 #2 [ffff800010003f60] ipi_handler at ffff800010054c84 #3 [ffff800010003f70] handle_percpu_devid_irq at ffff800010161980 #4 [ffff800010003fa0] handle_domain_irq at ffff80001015962c #5 [ffff800010003fd0] gic_handle_irq at ffff800010040190 --- <IRQ stack> --- #6 [ffff8000119c3bc0] call_on_irq_stack at ffff800010044db4 #7 [ffff8000119c3bd0] do_interrupt_handler at ffff800010046b68 #8 [ffff8000119c3be0] el1_interrupt at ffff800010c2f8ac #9 [ffff8000119c3c00] el1h_64_irq_handler at ffff800010c2fc94 #10 [ffff8000119c3d40] el1h_64_irq at ffff800010041348 #11 [ffff8000119c3d60] arch_cpu_idle at ffff800010c30b08 #12 [ffff8000119c3d70] default_idle_call at ffff800010c3d138 #13 [ffff8000119c3d90] cpuidle_idle_call at ffff800010115cf8 #14 [ffff8000119c3dd0] do_idle at ffff800010115e28 #15 [ffff8000119c3e00] cpu_startup_entry at ffff800010116080 #16 [ffff8000119c3e20] rest_init at ffff800010c3147c #17 [ffff8000119c3e40] arch_call_rest_init at ffff80001155151c #18 [ffff8000119c3e50] start_kernel at ffff800011551a54 PID: 0 TASK: ffff000803170000 CPU: 1 COMMAND: "swapper/1" ....... As the message shows, kernel version is "5.14.0-35.el9.aarch64", machine is hpe-apache-cn99xx-05.khw4.lab.eng.bos.redhat.com And crash 8.0.0-3.el9. One thing worth to mention is about the vmcore.strip. It is generated with " makedumpfile -l --message-level 7 -d 31 vmcore vmcore.strip", where vmcore is got by "collector cp" So could you re-test whether the latest kernel has this issue? Thanks, Pingfan