Article ID: 120203, created on Feb 18, 2014, last review on Jun 17, 2016

  • Applies to:
  • Virtuozzo 6.0

Symptoms

Containers created based on custom config while running kernel 2.6.32-042stab084.20 or 2.6.32-042stab084.21 cause hardlock on a host which causes watchdog to trigger crash with similar Call Trace:

<0>[28373.880315] Kernel panic - not syncing: Watchdog detected hard LOCKUP on cpu 1
<4>[28373.880543] Pid: 121275, comm: ploop48457 veid: 0 Tainted: P           --------------- 2.6.32-042stab084.21 #1
<4>[28373.880771] Call Trace:
<4>[28373.880880]  <NMI>  [<ffffffff81516317>] ? panic+0xa7/0x16f
<4>[28373.881021]  [<ffffffff810f43fd>] ? watchdog_overflow_callback+0xcd/0xd0
<4>[28373.881149]  [<ffffffff8112c5b0>] ? __perf_event_overflow+0xb0/0x2a0
<4>[28373.881272]  [<ffffffff8101ac4d>] ? x86_perf_event_update+0x5d/0xb0
<4>[28373.881389]  [<ffffffff8101bbdd>] ? x86_perf_event_set_period+0xdd/0x170
<4>[28373.881505]  [<ffffffff8112cbd4>] ? perf_event_overflow+0x14/0x20
<4>[28373.881624]  [<ffffffff81020c62>] ? intel_pmu_handle_irq+0x192/0x300
<4>[28373.881838]  [<ffffffff8151c606>] ? kprobe_exceptions_notify+0x16/0x430
<4>[28373.881956]  [<ffffffff8151b179>] ? perf_event_nmi_handler+0x39/0xb0
<4>[28373.882071]  [<ffffffff8151cc35>] ? notifier_call_chain+0x55/0x80
<4>[28373.882188]  [<ffffffff8151cc9a>] ? atomic_notifier_call_chain+0x1a/0x20
<4>[28373.882311]  [<ffffffff810a3ade>] ? notify_die+0x2e/0x30
<4>[28373.882424]  [<ffffffff8151a90b>] ? do_nmi+0x1bb/0x350
<4>[28373.882537]  [<ffffffff8151a1d0>] ? nmi+0x20/0x30
<4>[28373.882652]  [<ffffffff81519965>] ? _spin_lock_irq+0x25/0x40
<4>[28373.882764]  <<EOE>>  [<ffffffffa04c61d3>] ? ploop_entry_request+0x7e3/0xf40 [ploop]
<4>[28373.883014]  [<ffffffffa04c6d75>] ? ploop_req_state_process+0x445/0x710 [ploop]
<4>[28373.883242]  [<ffffffffa04cb08b>] ? ploop_thread+0x14b/0x6b0 [ploop]
<4>[28373.883372]  [<ffffffff8109d930>] ? autoremove_wake_function+0x0/0x40
<4>[28373.883498]  [<ffffffffa04caf40>] ? ploop_thread+0x0/0x6b0 [ploop]
<4>[28373.883619]  [<ffffffff8109d356>] ? kthread+0x96/0xa0
<4>[28373.883740]  [<ffffffff8100c1aa>] ? child_rip+0xa/0x20
<4>[28373.883858]  [<ffffffff8109d2c0>] ? kthread+0x0/0xa0
<4>[28373.883973]  [<ffffffff8100c1a0>] ? child_rip+0x0/0x20

Cause

The issue has been identified as a bug. Its internal ID is PSBM-24917.

Resolution

The bug PSBM-24917 has been already fixed in kernel 2.6.32-042stab084.25..

Search Words

ploop_entry_request

Watchdog detected hard LOCKUP on cpu

kernel panic

hard lockup

c62e8726973f80975db0531f1ed5c6a2 2897d76d56d2010f4e3a28f864d69223 0dd5b9380c7d4884d77587f3eb0fa8ef

Email subscription for changes to this article
Save as PDF