RHEL7: The kernel crashes due to a hard LOCKUP that happens on an idle CPU

Solution Verified - Updated -

Issue

  • The kernel crashes due to a hard LOCKUP that happens on an idle CPU.
[8198531.089880] Kernel panic - not syncing: Hard LOCKUP
[8198531.097354] CPU: 2 PID: 0 Comm: swapper/2 Kdump: loaded Tainted: P            E  ------------   3.10.0-1160.88.1.el7.x86_64 #1
[8198531.113003] Hardware name: Dell Inc. VxFlex-R740xd/06WXJT, BIOS 2.17.1 11/15/2022
[8198531.121295] Call Trace:
[8198531.129533]  <NMI>  [<ffffffffa9db1bec>] dump_stack+0x19/0x1f
[8198531.137927]  [<ffffffffa9dab708>] panic+0xe8/0x21f
[8198531.146365]  [<ffffffffa9630a78>] ? show_regs+0x58/0x290
[8198531.154858]  [<ffffffffa969f523>] nmi_panic+0x43/0x50
[8198531.163394]  [<ffffffffa9757409>] watchdog_overflow_callback+0x119/0x140
[8198531.172081]  [<ffffffffa97b32a7>] __perf_event_overflow+0x57/0x100
[8198531.180833]  [<ffffffffa97bcd64>] perf_event_overflow+0x14/0x20
[8198531.189531]  [<ffffffffa960acf0>] handle_pmi_common+0x1a0/0x260
[8198531.198039]  [<ffffffffa999eb48>] ? ioremap_page_range+0x2e8/0x490
[8198531.206351]  [<ffffffffa9811b54>] ? vunmap_page_range+0x234/0x470
[8198531.214470]  [<ffffffffa9a6af66>] ? ghes_copy_tofrom_phys+0x116/0x220
[8198531.222381]  [<ffffffffa960afef>] intel_pmu_handle_irq+0xcf/0x1d0
[8198531.230155]  [<ffffffffa9dbb039>] perf_event_nmi_handler+0x39/0x60
[8198531.237677]  [<ffffffffa9dbc9cc>] nmi_handle.isra.0+0x8c/0x150
[8198531.245449]  [<ffffffffa9dbcbed>] do_nmi+0x15d/0x460
[8198531.252689]  [<ffffffffa9dbbdf4>] end_repeat_nmi+0x1e/0x81
[8198531.259721]  [<ffffffffa9dba0d4>] ? intel_idle+0xd4/0x225
[8198531.266610]  [<ffffffffa9dba0d4>] ? intel_idle+0xd4/0x225
[8198531.273077]  [<ffffffffa9dba0d4>] ? intel_idle+0xd4/0x225
[8198531.279669]  <EOE>  [<ffffffffa9bebe85>] cpuidle_enter_state+0x45/0xd0
[8198531.285942]  [<ffffffffa9bebfee>] cpuidle_idle_call+0xde/0x230
[8198531.292106]  [<ffffffffa963955e>] arch_cpu_idle+0xe/0xc0
[8198531.298158]  [<ffffffffa970820a>] cpu_startup_entry+0x14a/0x1e0
[8198531.304168]  [<ffffffffa965d3a7>] start_secondary+0x1f7/0x270
[8198531.310534]  [<ffffffffa96000d5>] start_cpu+0x5/0x14

Environment

  • Red Hat Enterprise Linux (RHEL) 7 is affected
  • The similar issue can happen in Red Hat Enterprise Linux 8
  • hardware: the issue is not limited to a single hardware model

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content