Article ID: 118416, created on May 20, 2015, last review on May 20, 2015

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

Síntomas

El nodo se bloquea con el siguiente stack:

<0>[1738150.100921] Kernel panic - not syncing: Watchdog detected hard LOCKUP on cpu 0
<4>[1738150.101139] Pid: 0, comm: swapper veid: 0 Tainted: P           ---------------    2.6.32-042stab081.3 #1
<4>[1738150.101366] Call Trace:
<4>[1738150.101473]  <NMI>  [<ffffffff81516003>] ? panic+0xa7/0x16f
<4>[1738150.101608]  [<ffffffff810f43bd>] ? watchdog_overflow_callback+0xcd/0xd0
<4>[1738150.101734]  [<ffffffff8112c550>] ? __perf_event_overflow+0xb0/0x2a0
<4>[1738150.101861]  [<ffffffff8101ac3d>] ? x86_perf_event_update+0x5d/0xb0
<4>[1738150.101989]  [<ffffffff8101bbcd>] ? x86_perf_event_set_period+0xdd/0x170
<4>[1738150.102113]  [<ffffffff8112cb74>] ? perf_event_overflow+0x14/0x20
<4>[1738150.102237]  [<ffffffff81020c52>] ? intel_pmu_handle_irq+0x192/0x300
<4>[1738150.102365]  [<ffffffff8151c2e6>] ? kprobe_exceptions_notify+0x16/0x430
<4>[1738150.102486]  [<ffffffff8151ae59>] ? perf_event_nmi_handler+0x39/0xb0
<4>[1738150.102605]  [<ffffffff8151c915>] ? notifier_call_chain+0x55/0x80
<4>[1738150.102726]  [<ffffffff8151c97a>] ? atomic_notifier_call_chain+0x1a/0x20
<4>[1738150.102855]  [<ffffffff810a350e>] ? notify_die+0x2e/0x30
<4>[1738150.102974]  [<ffffffff8151a5eb>] ? do_nmi+0x1bb/0x350
<4>[1738150.103093]  [<ffffffff81519eb0>] ? nmi+0x20/0x30
<4>[1738150.103213]  [<ffffffff8151960f>] ? _spin_lock_irqsave+0x2f/0x40
<4>[1738150.103336]  <<EOE>>  <IRQ>  [<ffffffff810607af>] ? calc_global_load+0x1df/0x290
<4>[1738150.103580]  [<ffffffff810a84e9>] ? do_timer+0x329/0x590
<4>[1738150.103709]  [<ffffffff810f9cfe>] ? force_quiescent_state+0x7e/0x1a0
<4>[1738150.103839]  [<ffffffff810ae850>] ? tick_sched_timer+0x0/0xc0
<4>[1738150.103963]  [<ffffffff810ae6e6>] ? tick_do_update_jiffies64+0x76/0xd0
<4>[1738150.104091]  [<ffffffff810ae908>] ? tick_sched_timer+0xb8/0xc0
<4>[1738150.104215]  [<ffffffff810a1ace>] ? __run_hrtimer+0x8e/0x1d0
<4>[1738150.104340]  [<ffffffff810a87ef>] ? ktime_get_update_offsets+0x4f/0xd0
<4>[1738150.104461]  [<ffffffff810a1e66>] ? hrtimer_interrupt+0xe6/0x260
<4>[1738150.104587]  [<ffffffff815204cb>] ? smp_apic_timer_interrupt+0x6b/0x9b
<4>[1738150.104710]  [<ffffffff8100bc53>] ? apic_timer_interrupt+0x13/0x20
<4>[1738150.104830]  <EOI>  [<ffffffff812e015e>] ? intel_idle+0xde/0x170
<4>[1738150.104969]  [<ffffffff812e0141>] ? intel_idle+0xc1/0x170
<4>[1738150.105091]  [<ffffffff81422d37>] ? cpuidle_idle_call+0xa7/0x140
<4>[1738150.105212]  [<ffffffff8100a026>] ? cpu_idle+0xb6/0x110
<4>[1738150.105332]  [<ffffffff814fc595>] ? rest_init+0x85/0x90
<4>[1738150.105451]  [<ffffffff81c32f6e>] ? start_kernel+0x412/0x41e
<4>[1738150.105569]  [<ffffffff81c3233a>] ? x86_64_start_reservations+0x125/0x129
<4>[1738150.105691]  [<ffffffff81c32438>] ? x86_64_start_kernel+0xfa/0x109

O bien:

<0>[576492.063108] Kernel panic - not syncing: Watchdog detected hard LOCKUP on cpu 2
<4>[576492.063221] Pid: 3014, comm: vzstat veid: 0 Not tainted 2.6.32-042stab081.5 #1
<4>[576492.063328] Call Trace:
<4>[576492.063366]  <NMI>  [<ffffffff81515f93>] ? panic+0xa7/0x16f
<4>[576492.063461]  [<ffffffff810f43bd>] ? watchdog_overflow_callback+0xcd/0xd0
<4>[576492.063562]  [<ffffffff8112c550>] ? __perf_event_overflow+0xb0/0x2a0
<4>[576492.063656]  [<ffffffff8101ac3d>] ? x86_perf_event_update+0x5d/0xb0
<4>[576492.063750]  [<ffffffff8101bbcd>] ? x86_perf_event_set_period+0xdd/0x170
<4>[576492.063849]  [<ffffffff8112cb74>] ? perf_event_overflow+0x14/0x20
<4>[576492.063941]  [<ffffffff81020c52>] ? intel_pmu_handle_irq+0x192/0x300
<4>[576492.064035]  [<ffffffff8151c276>] ? kprobe_exceptions_notify+0x16/0x430
<4>[576492.064149]  [<ffffffff8151ade9>] ? perf_event_nmi_handler+0x39/0xb0
<4>[576492.064241]  [<ffffffff8151c8a5>] ? notifier_call_chain+0x55/0x80
<4>[576492.064332]  [<ffffffff8151c90a>] ? atomic_notifier_call_chain+0x1a/0x20
<4>[576492.064432]  [<ffffffff810a350e>] ? notify_die+0x2e/0x30
<4>[576492.064512]  [<ffffffff8151a57b>] ? do_nmi+0x1bb/0x350
<4>[576492.064589]  [<ffffffff81519e40>] ? nmi+0x20/0x30
<4>[576492.064661]  [<ffffffffa04a0bd1>] ? vzstat_mon_loop+0xfe1/0x1024 [vzstat]
<4>[576492.064760]  <<EOE>>  [<ffffffffa049fbf0>] ? vzstat_mon_loop+0x0/0x1024 [vzstat]
<4>[576492.064878]  [<ffffffffa049fbf0>] ? vzstat_mon_loop+0x0/0x1024 [vzstat]
<4>[576492.064979]  [<ffffffff8109cd86>] ? kthread+0x96/0xa0
<4>[576492.065057]  [<ffffffff8100c1aa>] ? child_rip+0xa/0x20
<4>[576492.065135]  [<ffffffff8109ccf0>] ? kthread+0x0/0xa0
<4>[576492.065207]  [<ffffffff8100c1a0>] ? child_rip+0x0/0x20

Causa

Se trata de un fallo del producto cuyo ID es PSBM-23293.

Resolución

La incidencia ha sido corregida en el kernel 2.6.32-042stab083.2. Instale todas las actualizaciones pendientes para así evitar este fallo.

c62e8726973f80975db0531f1ed5c6a2 2897d76d56d2010f4e3a28f864d69223 0dd5b9380c7d4884d77587f3eb0fa8ef a26b38f94253cdfbf1028d72cf3a498b e8e50b42231236b82df27684e7ec0beb d02f9caf3e11b191a38179103495106f 0c05f0c76fec3dd785e9feafce1099a9

Email subscription for changes to this article
Save as PDF