System crashed with hard lockup as a process spent time on _write_lock_irq() too long

Solution Verified - Updated -

Issue

  • System was crashed as hard LOCKUP was detected
Kernel panic - not syncing: Watchdog detected hard LOCKUP on cpu 2
Pid: 26329, comm: java Tainted: G        W  ---------------    2.6.32-358.el6.x86_64 #1
Call Trace:
 <NMI>  [<ffffffff8150cfc8>] ? panic+0xa7/0x16f
 [<ffffffff810e10fd>] ? watchdog_overflow_callback+0xcd/0xd0
 [<ffffffff81116f00>] ? __perf_event_overflow+0xb0/0x2a0
 [<ffffffff8101a7bd>] ? x86_perf_event_update+0x5d/0xb0
 [<ffffffff8101b74d>] ? x86_perf_event_set_period+0xdd/0x170
 [<ffffffff81117524>] ? perf_event_overflow+0x14/0x20
 [<ffffffff810207e2>] ? intel_pmu_handle_irq+0x192/0x300
 [<ffffffff81512ba6>] ? kprobe_exceptions_notify+0x16/0x430
 [<ffffffff81511719>] ? perf_event_nmi_handler+0x39/0xb0
 [<ffffffff815131d5>] ? notifier_call_chain+0x55/0x80
 [<ffffffff8151323a>] ? atomic_notifier_call_chain+0x1a/0x20
 [<ffffffff8109cbfe>] ? notify_die+0x2e/0x30
 [<ffffffff81510e9b>] ? do_nmi+0x1bb/0x340
 [<ffffffff81510760>] ? nmi+0x20/0x30
 [<ffffffff81283369>] ? __write_lock_failed+0x9/0x20
 <<EOE>>  [<ffffffff8150ffae>] ? _write_lock_irq+0x1e/0x20
 [<ffffffff8106c900>] ? copy_process+0xaf0/0x1450
 [<ffffffff81435b25>] ? sys_sendto+0x185/0x190
 [<ffffffff8106d2f4>] ? do_fork+0x94/0x460
 [<ffffffff8118173f>] ? vfs_read+0x12f/0x1a0
 [<ffffffff81009598>] ? sys_clone+0x28/0x30
 [<ffffffff8100b393>] ? stub_clone+0x13/0x20
 [<ffffffff8100b072>] ? system_call_fastpath+0x16/0x1b

Environment

  • Red Hat Enterprise Linux 6

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