Skip to content

Fix the random kdump kernel panic with call trace tick_handle_periodic

Baoquan He requested to merge baoquan_he/centos-stream-9:bz2116317 into main

Upstream-status: v6.2-rc4

Bugzilla: https://bugzilla.redhat.com/2116317

Summary of Changes

On some bare metal systems or kvm guest, kdump kernel will randomly hang with the call trace like below. Upstream has fixed ith with commit 5fa55950729d ("x86/i8259: Mark legacy PIC interrupts with IRQ_LEVEL"), so back port it to rhel to fix the issue.

Call Trace: 
 <IRQ> 
 tick_handle_periodic+0x20/0x60 
 timer_interrupt+0x14/0x20 
 __handle_irq_event_percpu+0x3d/0x180 
 handle_irq_event+0x58/0xb0 
 handle_level_irq+0x98/0x170 
 resend_irqs+0x5d/0x60 
 tasklet_action_common.constprop.0+0xa7/0x120 
 __do_softirq+0xca/0x2a8 
 __irq_exit_rcu+0xad/0xe0 
 common_interrupt+0x83/0xa0 
 </IRQ> 
 asm_common_interrupt+0x1e/0x40

Signed-off-by: Baoquan He bhe@redhat.com

Approved Bugzilla Ticket

All submissions to CentOS Stream must reference an approved ticket in Red Hat Bugzilla. Please follow the CentOS Stream contribution documentation for how to file this ticket and have it approved.

Edited by Baoquan He

Merge request reports