Article ID: 118719, created on Nov 18, 2013, last review on May 1, 2014

  • Applies to:
  • Virtuozzo 6.0
  • Virtuozzo containers for Linux
  • Virtuozzo hypervisor

Symptoms

A hardware node crashes with the following message sequence in dmesg:

<0>[544607.617553] Kernel panic - not syncing: Watchdog detected hard LOCKUP on cpu 6
<4>[544607.617771] Pid: 0, comm: swapper veid: 0 Tainted: P           ---------------    2.6.32-042stab081.5 #1
<4>[544607.617990] Call Trace:
<4>[544607.618096]  <NMI>  [<ffffffff81515f93>] ? panic+0xa7/0x16f
<4>[544607.618227]  [<ffffffff810f43bd>] ? watchdog_overflow_callback+0xcd/0xd0
<4>[544607.618347]  [<ffffffff8112c550>] ? __perf_event_overflow+0xb0/0x2a0
<4>[544607.618465]  [<ffffffff8101ac3d>] ? x86_perf_event_update+0x5d/0xb0
<4>[544607.618585]  [<ffffffff8101bbcd>] ? x86_perf_event_set_period+0xdd/0x170
<4>[544607.618704]  [<ffffffff8112cb74>] ? perf_event_overflow+0x14/0x20
<4>[544607.618823]  [<ffffffff81020c52>] ? intel_pmu_handle_irq+0x192/0x300
<4>[544607.618946]  [<ffffffff8151c276>] ? kprobe_exceptions_notify+0x16/0x430
<4>[544607.619068]  [<ffffffff8151ade9>] ? perf_event_nmi_handler+0x39/0xb0
<4>[544607.619186]  [<ffffffff8151c8a5>] ? notifier_call_chain+0x55/0x80
<4>[544607.619304]  [<ffffffff8151c90a>] ? atomic_notifier_call_chain+0x1a/0x20
<4>[544607.619424]  [<ffffffff810a350e>] ? notify_die+0x2e/0x30
<4>[544607.619539]  [<ffffffff8151a57b>] ? do_nmi+0x1bb/0x350
<4>[544607.619654]  [<ffffffff81519e40>] ? nmi+0x20/0x30
<4>[544607.619770]  [<ffffffff810af31e>] ? tick_nohz_stop_sched_tick+0x35e/0x3c0
<4>[544607.619887]  <<EOE>>  <IRQ>  [<ffffffff8100c2ac>] ? call_softirq+0x1c/0x30
<4>[544607.620021]  [<ffffffff8107aa63>] ? irq_exit+0x93/0xd0
<4>[544607.620137]  [<ffffffff81520460>] ? smp_apic_timer_interrupt+0x70/0x9b
<4>[544607.620259]  [<ffffffff8100bc53>] ? apic_timer_interrupt+0x13/0x20
<4>[544607.620377]  <EOI>  [<ffffffff812e00ee>] ? intel_idle+0xde/0x170
<4>[544607.620508]  [<ffffffff812e00d1>] ? intel_idle+0xc1/0x170
<4>[544607.620627]  [<ffffffff81422cc7>] ? cpuidle_idle_call+0xa7/0x140
<4>[544607.620745]  [<ffffffff8100a026>] ? cpu_idle+0xb6/0x110
<4>[544607.620861]  [<ffffffff8150fa0d>] ? start_secondary+0x2ac/0x2ef

Cause

The problem is recognized as a product bug with internal ID PSBM-22956.

Resolution

The fix will be included in one of the future updates of Parallels Cloud Server.

Search Words

pstorage node crash

Watchdog detected hard LOCKUP on cpu

a26b38f94253cdfbf1028d72cf3a498b 2897d76d56d2010f4e3a28f864d69223 e8e50b42231236b82df27684e7ec0beb d02f9caf3e11b191a38179103495106f c62e8726973f80975db0531f1ed5c6a2 0dd5b9380c7d4884d77587f3eb0fa8ef

Email subscription for changes to this article
Save as PDF