Article ID: 120369, created on Feb 27, 2014, last review on May 11, 2014

  • Applies to:
  • Virtuozzo 6.0
  • Virtuozzo hypervisor


The virtual machine running RHEL OS hangs. Similar messages can be seen in dmesg output in the guest operating system:

e1000 0000:00:05.0: eth0: Detected Tx Unit Hang
 Tx Queue             <0>
 TDH                  <d2>
 TDT                  <f8>
  next_to_use          <f8>
  next_to_clean        <d2>
  time_stamp           <2bbe53280>
  next_to_watch        <d6>
  jiffies              <2bbe54c75>
  next_to_watch.status <0>
------------[ cut here ]------------
WARNING: at net/sched/sch_generic.c:261 dev_watchdog+0x26d/0x280() (Tainted: P      ---------------   )
Hardware name: Parallels Virtual Platform
NETDEV WATCHDOG: eth0 (e1000): transmit queue 0 timed out
Modules linked in: prl_fs_freeze(P)(U) prl_eth(P)(U) ipv6 prl_fs(P)(U) dm_mod sg virtio_balloon     shpchp e1000 prl_tg(P)(U) ext4 mbcache jbd2 sd_mod crc_t10dif ahci pata_acpi ata_generic ata_piix virtio_pci virtio_ring virtio [last unloaded: scsi_wait_scan]
Pid: 0, comm: swapper Tainted: P           ---------------    2.6.32-279.22.1.el6.x86_64 #1
Call Trace:
 <IRQ>  [<ffffffff8106a2a7>] ? warn_slowpath_common+0x87/0xc0
 [<ffffffff8106a396>] ? warn_slowpath_fmt+0x46/0x50
 [<ffffffff81447d0d>] ? dev_watchdog+0x26d/0x280
 [<ffffffff8107c7c5>] ? internal_add_timer+0xb5/0x110
 [<ffffffff81447aa0>] ? dev_watchdog+0x0/0x280
 [<ffffffff8107d3f7>] ? run_timer_softirq+0x197/0x340
 [<ffffffff8102adad>] ? lapic_next_event+0x1d/0x30
 [<ffffffff81072ac1>] ? __do_softirq+0xc1/0x1e0
 [<ffffffff81095760>] ? hrtimer_interrupt+0x140/0x250
 [<ffffffff8100c1cc>] ? call_softirq+0x1c/0x30
 [<ffffffff8100de05>] ? do_softirq+0x65/0xa0
 [<ffffffff810728a5>] ? irq_exit+0x85/0x90
 [<ffffffff814f2360>] ? smp_apic_timer_interrupt+0x70/0x9b
 [<ffffffff8100bb93>] ? apic_timer_interrupt+0x13/0x20
 <EOI>  [<ffffffff810377cb>] ? native_safe_halt+0xb/0x10
 [<ffffffff8101485d>] ? default_idle+0x4d/0xb0
 [<ffffffff81009fc6>] ? cpu_idle+0xb6/0x110
 [<ffffffff814d147a>] ? rest_init+0x7a/0x80
 [<ffffffff81c21f7b>] ? start_kernel+0x424/0x430
 [<ffffffff81c2133a>] ? x86_64_start_reservations+0x125/0x129
 [<ffffffff81c21438>] ? x86_64_start_kernel+0xfa/0x109
---[ end trace b3012b7484f3ff15 ]---
e1000 0000:00:05.0: eth0: Reset adapter
INFO: task events/0:19 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
events/0      D 0000000000000000     0    19      2 0x00000000
 ffff88014cc75b90 0000000000000046 ffff880090d42ad8 0000000011a60a6e
 ffff880090d42aa0 0000000000000001 ffff88014cc75b40 ffffffff81061d25
 ffff88014cc73af8 ffff88014cc75fd8 000000000000fb88 ffff88014cc73af8
Call Trace:
 [<ffffffff81061d25>] ? enqueue_entity+0x125/0x410
 [<ffffffff8105a5c3>] ? perf_event_task_sched_out+0x33/0x80
 [<ffffffff814eae85>] schedule_timeout+0x215/0x2e0
 [<ffffffff810629bb>] ? dequeue_task_fair+0x12b/0x130
 [<ffffffff810096f0>] ? __switch_to+0xd0/0x320
 [<ffffffff814eab03>] wait_for_common+0x123/0x180
 [<ffffffff8105fa40>] ? default_wake_function+0x0/0x20
 [<ffffffff814eac1d>] wait_for_completion+0x1d/0x20
 [<ffffffff8108bea3>] __cancel_work_timer+0x1b3/0x1e0
 [<ffffffff8108b7f0>] ? wq_barrier_func+0x0/0x20
 [<ffffffff8108bf00>] cancel_work_sync+0x10/0x20
 [<ffffffffa00e7ca5>] e1000_down_and_stop+0x25/0x50 [e1000]
 [<ffffffffa00ed695>] e1000_down+0x155/0x200 [e1000]
 [<ffffffffa00edcb0>] ? e1000_reset_task+0x0/0xe0 [e1000]
 [<ffffffffa00edd1e>] e1000_reset_task+0x6e/0xe0 [e1000]
 [<ffffffff8108b370>] worker_thread+0x170/0x2a0
 [<ffffffff81090be0>] ? autoremove_wake_function+0x0/0x40
 [<ffffffff8108b200>] ? worker_thread+0x0/0x2a0
 [<ffffffff81090876>] kthread+0x96/0xa0
 [<ffffffff8100c0ca>] child_rip+0xa/0x20
 [<ffffffff810907e0>] ? kthread+0x0/0xa0
 [<ffffffff8100c0c0>] ? child_rip+0x0/0x20
INFO: task events/0:19 blocked for more than 120 seconds.


Trigger: System hangs when interface, that use e1000 driver, configured to receive IP from DHCP.

The problem is caused by a bug in RHEL6.3 kernel.


The problem has been fixed in RHEL6.4 kernels, updating kernel inside the virtual machine should solve the issue.

Search Words

vm hang

Detected Tx Unit Hang

rhel vm

red hat vm

task events/0:19 blocked for more than 120 seconds

a26b38f94253cdfbf1028d72cf3a498b 2897d76d56d2010f4e3a28f864d69223 c62e8726973f80975db0531f1ed5c6a2 0dd5b9380c7d4884d77587f3eb0fa8ef

Email subscription for changes to this article
Save as PDF