RHEL 6.7: Kernel panic - not syncing: Watchdog detected hard LOCKUP on cpu 1

Solution Unverified - Updated -

Issue

  • Kernel panics with following call traces:
 Kernel panic - not syncing: Watchdog detected hard LOCKUP on cpu 2
Pid: 44952, comm: java Tainted: G           --L------------    2.6.32-573.22.1.el6.x86_64 #1
Call Trace:
 <NMI>  [<ffffffff81538c41>] ? panic+0xa7/0x16f
 [<ffffffff81014a19>] ? sched_clock+0x9/0x10
 [<ffffffff810ed83d>] ? watchdog_overflow_callback+0xcd/0xd0
 [<ffffffff811243b7>] ? __perf_event_overflow+0xa7/0x240
 [<ffffffff8101dca4>] ? x86_perf_event_set_period+0xf4/0x180
 [<ffffffff81124a04>] ? perf_event_overflow+0x14/0x20
 [<ffffffff81024a52>] ? intel_pmu_handle_irq+0x202/0x3f0
 [<ffffffff8153df69>] ? perf_event_nmi_handler+0x39/0xb0
 [<ffffffff8153fa25>] ? notifier_call_chain+0x55/0x80
 [<ffffffff8153fa8a>] ? atomic_notifier_call_chain+0x1a/0x20
 [<ffffffff810a7bfe>] ? notify_die+0x2e/0x30
 [<ffffffff8153d6e3>] ? do_nmi+0x1c3/0x350
 [<ffffffff8153cfa0>] ? nmi+0x20/0x30
 [<ffffffff8129dff9>] ? __write_lock_failed+0x9/0x20
 <<EOE>>  [<ffffffff8153c7ee>] ? _write_lock_irq+0x1e/0x20
 [<ffffffff81075d76>] ? copy_process+0xb76/0x1500
 [<ffffffff81076856>] ? do_fork+0x96/0x4c0
 [<ffffffff810567a6>] ? sys32_clone+0x26/0x30
 [<ffffffff81056595>] ? ia32_ptregs_common+0x25/0x50

Environment

  • Red Hat Enterprise Linux 6.7

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.