VirtualBox

Opened 8 years ago

Last modified 3 years ago

#15845 new defect

e1000 Detected Tx Unit Hang

Reported by: LordChaos Owned by:
Component: network Version: VirtualBox 5.1.2
Keywords: Cc:
Guest type: Linux Host type: Windows

Description (last modified by janitor)

Hi,

My Arch Linux desktop (client) is sometimes hanging, seems like the kernel module is detecting a disconnection:

aug 22 11:25:07 virtwin nm-dispatcher[4102]: req:1 'dhcp4-change' [enp0s3]: new request (0 scripts)
aug 22 11:25:07 virtwin nm-dispatcher[4102]: req:1 'dhcp4-change' [enp0s3]: completed: no scripts
aug 22 11:25:08 virtwin chromium.desktop[1507]: [1507:1530:0822/112508:ERROR:connection_factory_impl.cc(369)] Failed 
aug 22 11:25:38 virtwin NetworkManager[271]: <info>  [1471857938.2914] device (enp0s3): link disconnected (deferring 
aug 22 11:25:38 virtwin kernel: e1000 0000:00:03.0 enp0s3: Reset adapter
aug 22 11:25:38 virtwin NetworkManager[271]: <info>  [1471857938.3570] device (enp0s3): link connected
aug 22 11:25:38 virtwin NetworkManager[271]: <info>  [1471857938.3571] device (enp0s3): DHCPv4 lease renewal requeste
aug 22 11:25:38 virtwin kernel: e1000: enp0s3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
aug 22 11:25:38 virtwin NetworkManager[271]: <info>  [1471857938.3753] dhcp4 (enp0s3): canceled DHCP transaction, DHC
aug 22 11:25:38 virtwin NetworkManager[271]: <info>  [1471857938.3753] dhcp4 (enp0s3): state changed bound -> done
aug 22 11:25:38 virtwin NetworkManager[271]: <info>  [1471857938.3760] dhcp4 (enp0s3): activation: beginning transact
aug 22 11:25:38 virtwin NetworkManager[271]: <info>  [1471857938.3783] dhcp4 (enp0s3): dhclient started with pid 4117
aug 22 11:25:38 virtwin dhclient[4117]: DHCPREQUEST on enp0s3 to 255.255.255.255 port 67
aug 22 11:25:41 virtwin kernel: e1000 0000:00:03.0 enp0s3: Detected Tx Unit Hang
                                  Tx Queue             <0>
                                  TDH                  <1>
                                  TDT                  <9>
                                  next_to_use          <9>
                                  next_to_clean        <2>
                                buffer_info[next_to_clean]
                                  time_stamp           <10012adce>
                                  next_to_watch        <2>
                                  jiffies              <10012b100>
                                  next_to_watch.status <0>

I must admit I do all my work in this virtual machine, but I can't recall to have seen disconnects in Windows (the host).

Guest OS: Arch Linux Kernel: 4.7.1-1-ARCH

Change History (12)

comment:1 by LordChaos, 8 years ago

aug 22 11:25:03 virtwin kernel: ------------[ cut here ]------------
aug 22 11:25:03 virtwin kernel: WARNING: CPU: 1 PID: 0 at net/sched/sch_generic.c:272 dev_watchdog+0x22a/0x230
aug 22 11:25:03 virtwin kernel: NETDEV WATCHDOG: enp0s3 (e1000): transmit queue 0 timed out
aug 22 11:25:03 virtwin kernel: Modules linked in: fuse intel_powerclamp crct10dif_pclmul crc32_pclmul crc32c_intel g
aug 22 11:25:03 virtwin kernel: CPU: 1 PID: 0 Comm: swapper/1 Tainted: G           O    4.7.1-1-ARCH #1
aug 22 11:25:03 virtwin kernel: Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006
aug 22 11:25:03 virtwin kernel:  0000000000000286 9e00b9688129fa78 ffff88011fd03d90 ffffffff812eb042
aug 22 11:25:03 virtwin kernel:  ffff88011fd03de0 0000000000000000 ffff88011fd03dd0 ffffffff8107a3ab
aug 22 11:25:03 virtwin kernel:  000001101fd16740 0000000000000000 ffff8800daa35680 0000000000000001
aug 22 11:25:03 virtwin kernel: Call Trace:
aug 22 11:25:03 virtwin kernel:  <IRQ>  [<ffffffff812eb042>] dump_stack+0x63/0x81
aug 22 11:25:03 virtwin kernel:  [<ffffffff8107a3ab>] __warn+0xcb/0xf0
aug 22 11:25:03 virtwin kernel:  [<ffffffff8107a42f>] warn_slowpath_fmt+0x5f/0x80
aug 22 11:25:03 virtwin kernel:  [<ffffffff810921fa>] ? __queue_work+0x17a/0x4b0
aug 22 11:25:03 virtwin kernel:  [<ffffffff814fb37a>] dev_watchdog+0x22a/0x230
aug 22 11:25:03 virtwin kernel:  [<ffffffff814fb150>] ? qdisc_rcu_free+0x40/0x40
aug 22 11:25:03 virtwin kernel:  [<ffffffff810e71c5>] call_timer_fn+0x35/0x150
aug 22 11:25:03 virtwin kernel:  [<ffffffff814fb150>] ? qdisc_rcu_free+0x40/0x40
aug 22 11:25:03 virtwin kernel:  [<ffffffff810e7516>] run_timer_softirq+0x236/0x2e0
aug 22 11:25:03 virtwin kernel:  [<ffffffff815e0286>] __do_softirq+0xe6/0x2ec
aug 22 11:25:03 virtwin kernel:  [<ffffffff8107f983>] irq_exit+0xa3/0xb0
aug 22 11:25:03 virtwin kernel:  [<ffffffff815e0072>] smp_apic_timer_interrupt+0x42/0x50
aug 22 11:25:03 virtwin kernel:  [<ffffffff815de372>] apic_timer_interrupt+0x82/0x90
aug 22 11:25:03 virtwin kernel:  <EOI>  [<ffffffff8105e856>] ? native_safe_halt+0x6/0x10
aug 22 11:25:03 virtwin kernel:  [<ffffffff81037b90>] default_idle+0x20/0x110
aug 22 11:25:03 virtwin kernel:  [<ffffffff8103836f>] arch_cpu_idle+0xf/0x20
aug 22 11:25:03 virtwin kernel:  [<ffffffff810bd31a>] default_idle_call+0x2a/0x40
aug 22 11:25:03 virtwin kernel:  [<ffffffff810bd668>] cpu_startup_entry+0x338/0x390
aug 22 11:25:03 virtwin kernel:  [<ffffffff8104fcdc>] start_secondary+0x15c/0x190
aug 22 11:25:03 virtwin kernel: ---[ end trace f6c0850b25696252 ]---

comment:2 by LordChaos, 8 years ago

aug 22 11:25:03 virtwin kernel: e1000 0000:00:03.0 enp0s3: Reset adapter
aug 22 11:25:03 virtwin NetworkManager[271]: <info>  [1471857903.3367] device (enp0s3): link connected
aug 22 11:25:03 virtwin NetworkManager[271]: <info>  [1471857903.3371] device (enp0s3): DHCPv4 lease renewal requeste
aug 22 11:25:03 virtwin kernel: e1000: enp0s3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
aug 22 11:25:03 virtwin NetworkManager[271]: <info>  [1471857903.3539] dhcp4 (enp0s3): canceled DHCP transaction, DHC
aug 22 11:25:03 virtwin NetworkManager[271]: <info>  [1471857903.3539] dhcp4 (enp0s3): state changed bound -> done
aug 22 11:25:03 virtwin NetworkManager[271]: <info>  [1471857903.3543] dhcp4 (enp0s3): activation: beginning transact
aug 22 11:25:03 virtwin NetworkManager[271]: <info>  [1471857903.3559] dhcp4 (enp0s3): dhclient started with pid 4091
aug 22 11:25:03 virtwin dhclient[4091]: DHCPREQUEST on enp0s3 to 255.255.255.255 port 67
aug 22 11:25:07 virtwin kernel: e1000 0000:00:03.0 enp0s3: Detected Tx Unit Hang
                                  Tx Queue             <0>
                                  TDH                  <5>
                                  TDT                  <b>
                                  next_to_use          <b>
                                  next_to_clean        <3>
                                buffer_info[next_to_clean]
                                  time_stamp           <1001285bd>
                                  next_to_watch        <4>
                                  jiffies              <1001289b7>
                                  next_to_watch.status <1>

comment:3 by LordChaos, 8 years ago

➜  ~ ethtool -i enp0s3
driver: e1000
version: 7.3.21-k8-NAPI
firmware-version: 
expansion-rom-version: 
bus-info: 0000:00:03.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: no

comment:4 by astehlik, 6 years ago

Hi there,

I experienced some similar problems.

System environment

Some information about my system environment:

  • Host System: Fedora 26 (Desktop, KDE)
  • VirtualBox Version 5.2.0 r118431 (Qt5.9.2)
  • Guest System: centos/7 Vagrant box Version v1710.01 (all Updates installed)

The problem

The network connection is regularly breaking down. Depending on the selected adapter type two different error messages appear inside the box:

  • eth0: Reset adapter
  • eth0: transmit timed out; status 0073, resetting

eth0 is the default NAT adapter created by Vagrant with an SSH port forwarding.

Workaround

I found some similar error reportings:

None of them helped (changing adapter type, disconnect unused adapters).

I found one solution though: I stopped installing the VirtualBox Guest Additions in the VM.

When using the default operating system drivers everything seems to work stable.

I hope this helps tracking down the problem.

Cheers, Alex

comment:5 by astehlik, 5 years ago

I tested again today with Virtualbox 6.0.2 and a current CentOS Vagrant box 1812.01 and the problem seems to be solved.

I can install the VirtualBox Guest Additions and experience no network problems any more.

comment:6 by Rainer, 5 years ago

I am still seeing this with Virtualbox 6.0.4 and Ubuntu 18.10 host. Guest is also Ubuntu 18.10. Once the vm has booted, the guest is working normal.

Here is kernel log of guest

[    8.508707] e1000: enp0s17 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
[    8.509523] e1000 0000:00:11.0 enp0s17: Detected Tx Unit Hang
                 Tx Queue             <0>
                 TDH                  <0>
                 TDT                  <1>
                 next_to_use          <1>
                 next_to_clean        <0>
               buffer_info[next_to_clean]
                 time_stamp           <fffee18d>
                 next_to_watch        <0>
                 jiffies              <fffee358>
                 next_to_watch.status <0>
[    8.958512] 10:13:06.780146 automount Error: vbsvcAutomounterMountIt: Failed to mount 'Downloads' on '/media/sf_Downloads' because it is probably mounted elsewhere arleady! (-1,22)
[   10.523838] e1000 0000:00:11.0 enp0s17: Detected Tx Unit Hang
                 Tx Queue             <0>
                 TDH                  <0>
                 TDT                  <1>
                 next_to_use          <1>
                 next_to_clean        <0>
               buffer_info[next_to_clean]
                 time_stamp           <fffee18d>
                 next_to_watch        <0>
                 jiffies              <fffee550>
                 next_to_watch.status <0>
[   12.539558] e1000 0000:00:11.0 enp0s17: Detected Tx Unit Hang
                 Tx Queue             <0>
                 TDH                  <0>
                 TDT                  <1>
                 next_to_use          <1>
                 next_to_clean        <0>
               buffer_info[next_to_clean]
                 time_stamp           <fffee18d>
                 next_to_watch        <0>
                 jiffies              <fffee748>
                 next_to_watch.status <0>
[   14.041426] ------------[ cut here ]------------
[   14.041481] NETDEV WATCHDOG: enp0s17 (e1000): transmit queue 0 timed out
[   14.041556] WARNING: CPU: 1 PID: 0 at net/sched/sch_generic.c:461 dev_watchdog+0x221/0x230
[   14.041564] Modules linked in: vboxvideo(OE) vboxsf(OE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd cryptd glue_helper joydev intel_rapl_perf input_leds serio_raw vboxguest(OE) mac_hid sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 xfs libcrc32c hid_generic usbhid hid vmwgfx ttm drm_kms_helper syscopyarea sysfillrect sysimgblt ahci psmouse libahci fb_sys_fops video drm e1000 i2c_piix4
[   14.041661] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G           OE     4.18.0-15-generic #16-Ubuntu
[   14.041664] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006
[   14.041672] RIP: 0010:dev_watchdog+0x221/0x230
[   14.041673] Code: 00 49 63 4e e8 eb 92 4c 89 ef c6 05 af 46 d6 00 01 e8 03 c5 fc ff 89 d9 4c 89 ee 48 c7 c7 30 13 fb a4 48 89 c2 e8 b1 10 7c ff <0f> 0b eb c0 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 
[   14.041786] RSP: 0018:ffffa08cffd03e68 EFLAGS: 00010286
[   14.041792] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 000000000000083f
[   14.041795] RDX: 0000000000000000 RSI: 00000000000000f6 RDI: 000000000000083f
[   14.041799] RBP: ffffa08cffd03e98 R08: 0000000000000001 R09: 0000000000000212
[   14.041801] R10: 0000000000000004 R11: 0000000000000000 R12: 0000000000000001
[   14.041805] R13: ffffa08cf1eea000 R14: ffffa08cf1eea4b8 R15: ffffa08cb469ba80
[   14.041810] FS:  0000000000000000(0000) GS:ffffa08cffd00000(0000) knlGS:0000000000000000
[   14.041813] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[   14.041817] CR2: 000055c8b0a01620 CR3: 000000001820a005 CR4: 00000000000606e0
[   14.041827] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[   14.041831] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
[   14.041833] Call Trace:
[   14.041837]  <IRQ>
[   14.041850]  ? pfifo_fast_change_tx_queue_len+0x2e0/0x2e0
[   14.041867]  call_timer_fn+0x30/0x130
[   14.041874]  run_timer_softirq+0x3ea/0x420
[   14.041882]  ? ktime_get+0x3c/0xa0
[   14.041888]  ? native_apic_msr_write+0x2b/0x30
[   14.041895]  ? lapic_next_event+0x20/0x30
[   14.041903]  ? clockevents_program_event+0x93/0xf0
[   14.041911]  __do_softirq+0xdc/0x2d4
[   14.041920]  irq_exit+0xc0/0xd0
[   14.041927]  smp_apic_timer_interrupt+0x79/0x140
[   14.041933]  apic_timer_interrupt+0xf/0x20
[   14.041937]  </IRQ>
[   14.041946] RIP: 0010:native_safe_halt+0x6/0x10
[   14.041951] Code: ff ff 7f 5d c3 65 48 8b 04 25 00 5c 01 00 f0 80 48 02 20 48 8b 00 a8 08 75 c3 eb 8b 90 90 90 90 90 90 90 90 55 48 89 e5 fb f4 <5d> c3 0f 1f 84 00 00 00 00 00 55 48 89 e5 f4 5d c3 90 90 90 90 90 
[   14.042071] RSP: 0018:ffffad9f80387e68 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff13
[   14.042076] RAX: ffffffffa47f28a0 RBX: 0000000000000001 RCX: ffffffffa5271020
[   14.042079] RDX: 0000000000021f66 RSI: ffffffffa522fc88 RDI: 0000000000000087
[   14.042082] RBP: ffffad9f80387e68 R08: 00000005ee680dab R09: 00000003432e2700
[   14.042086] R10: 000000000002815c R11: 0000000000000001 R12: 0000000000000001
[   14.042089] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
[   14.042097]  ? ldsem_down_write+0x200/0x200
[   14.042110]  default_idle+0x20/0xe0
[   14.042117]  arch_cpu_idle+0x15/0x20
[   14.042124]  default_idle_call+0x2c/0x30
[   14.042131]  do_idle+0x1f8/0x280
[   14.042137]  cpu_startup_entry+0x73/0x80
[   14.042143]  start_secondary+0x1ab/0x200
[   14.042150]  secondary_startup_64+0xa5/0xb0
[   14.042156] ---[ end trace f641e18c4e7b9c8c ]---
[   14.042569] e1000 0000:00:11.0 enp0s17: Reset adapter
[   16.152596] e1000: enp0s17 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX

comment:7 by Rainer, 5 years ago

I have more simple kernel log without the failed vboxsf mount but with guest additions version information:

    5.043682] vboxsf: Successfully loaded version 6.0.4 (interface 0x00010004)
[    5.246845] 10:39:38.062081 main     VBoxService 6.0.4 r128413 (verbosity: 0) linux.amd64 (Jan 25 2019 19:35:06) release log
               10:39:38.062084 main     Log opened 2019-02-18T10:39:38.062030000Z
[    5.246871] 10:39:38.062155 main     OS Product: Linux
[    5.246882] 10:39:38.062170 main     OS Release: 4.18.0-15-generic
[    5.246893] 10:39:38.062181 main     OS Version: #16-Ubuntu SMP Thu Feb 7 10:56:39 UTC 2019
[    5.246912] 10:39:38.062192 main     Executable: /opt/VBoxGuestAdditions-6.0.4/sbin/VBoxService
               10:39:38.062193 main     Process ID: 1136
               10:39:38.062193 main     Package type: LINUX_64BITS_GENERIC
[    5.247391] 10:39:38.062672 main     6.0.4 r128413 started. Verbose level = 0
[    5.248549] 10:39:38.063817 main     vbglR3GuestCtrlDetectPeekGetCancelSupport: Supported (#1)
[    6.268423] e1000: enp0s17 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
[    8.288336] e1000 0000:00:11.0 enp0s17: Detected Tx Unit Hang
                 Tx Queue             <0>
                 TDH                  <0>
                 TDT                  <1>
                 next_to_use          <1>
                 next_to_clean        <0>
               buffer_info[next_to_clean]
                 time_stamp           <fffedf49>
                 next_to_watch        <0>
                 jiffies              <fffee321>
                 next_to_watch.status <0>
[   10.298723] e1000 0000:00:11.0 enp0s17: Detected Tx Unit Hang
                 Tx Queue             <0>
                 TDH                  <0>
                 TDT                  <1>
                 next_to_use          <1>
                 next_to_clean        <0>
               buffer_info[next_to_clean]
                 time_stamp           <fffedf49>
                 next_to_watch        <0>
                 jiffies              <fffee518>
                 next_to_watch.status <0>
[   11.993585] ------------[ cut here ]------------
[   11.993587] NETDEV WATCHDOG: enp0s17 (e1000): transmit queue 0 timed out
[   11.993604] WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:461 dev_watchdog+0x221/0x230
[   11.993605] Modules linked in: vboxvideo(OE) vboxsf(OE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd cryptd glue_helper intel_rapl_perf joydev input_leds serio_raw vboxguest(OE) mac_hid sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 xfs libcrc32c hid_generic usbhid hid vmwgfx ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm ahci video libahci e1000 psmouse i2c_piix4
[   11.993627] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G           OE     4.18.0-15-generic #16-Ubuntu
[   11.993628] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006
[   11.993630] RIP: 0010:dev_watchdog+0x221/0x230
[   11.993630] Code: 00 49 63 4e e8 eb 92 4c 89 ef c6 05 af 46 d6 00 01 e8 03 c5 fc ff 89 d9 4c 89 ee 48 c7 c7 30 13 9b bb 48 89 c2 e8 b1 10 7c ff <0f> 0b eb c0 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 
[   11.993650] RSP: 0018:ffff91417fc03e68 EFLAGS: 00010286
[   11.993651] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000006
[   11.993652] RDX: 0000000000000007 RSI: 0000000000000096 RDI: ffff91417fc164b0
[   11.993652] RBP: ffff91417fc03e98 R08: 0000000000000001 R09: 000000000000020a
[   11.993653] R10: 0000000000000004 R11: 0000000000000000 R12: 0000000000000001
[   11.993654] R13: ffff914134530000 R14: ffff9141345304b8 R15: ffff914134643880
[   11.993655] FS:  0000000000000000(0000) GS:ffff91417fc00000(0000) knlGS:0000000000000000
[   11.993655] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[   11.993656] CR2: 0000558b880d1b88 CR3: 000000003bc0a006 CR4: 00000000000606f0
[   11.993658] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[   11.993659] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
[   11.993659] Call Trace:
[   11.993660]  <IRQ>
[   11.993663]  ? pfifo_fast_change_tx_queue_len+0x2e0/0x2e0
[   11.993667]  call_timer_fn+0x30/0x130
[   11.993669]  run_timer_softirq+0x3ea/0x420
[   11.993670]  ? ktime_get+0x3c/0xa0
[   11.993672]  ? native_apic_msr_write+0x2b/0x30
[   11.993673]  ? lapic_next_event+0x20/0x30
[   11.993675]  ? clockevents_program_event+0x93/0xf0
[   11.993677]  __do_softirq+0xdc/0x2d4
[   11.993679]  irq_exit+0xc0/0xd0
[   11.993680]  smp_apic_timer_interrupt+0x79/0x140
[   11.993682]  apic_timer_interrupt+0xf/0x20
[   11.993682]  </IRQ>
[   11.993684] RIP: 0010:native_safe_halt+0x6/0x10
[   11.993684] Code: ff ff 7f 5d c3 65 48 8b 04 25 00 5c 01 00 f0 80 48 02 20 48 8b 00 a8 08 75 c3 eb 8b 90 90 90 90 90 90 90 90 55 48 89 e5 fb f4 <5d> c3 0f 1f 84 00 00 00 00 00 55 48 89 e5 f4 5d c3 90 90 90 90 90 
[   11.993704] RSP: 0018:ffffffffbbc03e10 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff13
[   11.993705] RAX: ffffffffbb1f28a0 RBX: 0000000000000000 RCX: ffffffffbbc71020
[   11.993706] RDX: 000000000000bfd2 RSI: ffffffffbbc2fc88 RDI: 0000000000000000
[   11.993707] RBP: ffffffffbbc03e10 R08: 00000005155795f2 R09: 0000000000000001
[   11.993707] R10: 0000000000000000 R11: 0000000000000400 R12: 0000000000000000
[   11.993708] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
[   11.993709]  ? ldsem_down_write+0x200/0x200
[   11.993711]  default_idle+0x20/0xe0
[   11.993713]  arch_cpu_idle+0x15/0x20
[   11.993714]  default_idle_call+0x2c/0x30
[   11.993716]  do_idle+0x1f8/0x280
[   11.993717]  cpu_startup_entry+0x73/0x80
[   11.993718]  rest_init+0xae/0xb0
[   11.993724]  start_kernel+0x539/0x55a
[   11.993725]  x86_64_start_reservations+0x24/0x26
[   11.993726]  x86_64_start_kernel+0x74/0x77
[   11.993728]  secondary_startup_64+0xa5/0xb0
[   11.993729] ---[ end trace a2c9f551deec4d4a ]---
[   11.993743] e1000 0000:00:11.0 enp0s17: Reset adapter
[   14.072716] e1000: enp0s17 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX

comment:8 by janitor, 5 years ago

Description: modified (diff)

comment:9 by slackerman, 5 years ago

If using a Linux guest, just switch over to the paravirtual (virtio) network adapter. You won't see this sort of error and it should run faster...

comment:10 by Rainer, 5 years ago

I see this #16925. I use e1000.

Last edited 3 years ago by Valery Ushakov (previous) (diff)

comment:11 by Mihai Hanor, 4 years ago

Duplicate: #16221

comment:12 by Sanitariu, 3 years ago

Virtualbox 6.1.14 problem is still there ! This is funny .... 10 years and still no fix for the intel adapters. Yes we can try virtio but my virtual machine stuck after 1 day and need power cycle .... using PCnet is not an option because i need gigabit. Here is the log:

[Fri Dec 11 04:23:07 2020] ------------[ cut here ]------------ [Fri Dec 11 04:23:07 2020] WARNING: CPU: 0 PID: 2883 at /build/linux-o3gOgM/linux-4.9.189/net/sched/sch_generic.c:316 dev_watchdog+0x233/0x240 [Fri Dec 11 04:23:07 2020] NETDEV WATCHDOG: enp0s3 (e1000): transmit queue 0 timed out [Fri Dec 11 04:23:07 2020] Modules linked in: vboxvideo(O) ipt_REJECT nf_reject_ipv4 xt_multiport xt_tcpudp ip6table_filter ip6_tables iptable_filter iTCO_wdt sb_edac edac_core iTCO_vendor_support intel_powerclamp kvm_intel kvm irqbypass vmwgfx evdev sg crct10dif_pclmul crc32_pclmul ttm drm_kms_helper serio_raw pcspkr lpc_ich mfd_core rng_core vboxguest(O) ghash_clmulni_intel intel_rapl_perf drm video ac button ip_tables x_tables autofs4 ext4 crc16 jbd2 crc32c_generic fscrypto ecb mbcache sd_mod ata_generic crc32c_intel aesni_intel aes_x86_64 glue_helper lrw gf128mul ablk_helper cryptd ata_piix ahci libahci psmouse e1000 libata scsi_mod i2c_piix4 [Fri Dec 11 04:23:07 2020] CPU: 0 PID: 2883 Comm: bzip2 Tainted: G O 4.9.0-11-amd64 #1 Debian 4.9.189-3+deb9u2 [Fri Dec 11 04:23:07 2020] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006 [Fri Dec 11 04:23:07 2020] 0000000000000000 ffffffffa9736404 ffff923823c03e20 0000000000000000 [Fri Dec 11 04:23:07 2020] ffffffffa947b83b 0000000000000000 ffff923823c03e78 ffff92380cd98000 [Fri Dec 11 04:23:07 2020] 0000000000000000 ffff92380d238c80 0000000000000001 ffffffffa947b8bf [Fri Dec 11 04:23:07 2020] Call Trace: [Fri Dec 11 04:23:07 2020] <IRQ> [Fri Dec 11 04:23:07 2020] [<ffffffffa9736404>] ? dump_stack+0x5c/0x78 [Fri Dec 11 04:23:07 2020] [<ffffffffa947b83b>] ? warn+0xcb/0xf0 [Fri Dec 11 04:23:07 2020] [<ffffffffa947b8bf>] ? warn_slowpath_fmt+0x5f/0x80 [Fri Dec 11 04:23:07 2020] [<ffffffffa993eb93>] ? dev_watchdog+0x233/0x240 [Fri Dec 11 04:23:07 2020] [<ffffffffa993e960>] ? dev_deactivate_queue.constprop.26+0x60/0x60 [Fri Dec 11 04:23:07 2020] [<ffffffffa94ea292>] ? call_timer_fn+0x32/0x120 [Fri Dec 11 04:23:07 2020] [<ffffffffa94ea607>] ? run_timer_softirq+0x1d7/0x430 [Fri Dec 11 04:23:07 2020] [<ffffffffa973f564>] ? timerqueue_add+0x54/0xa0 [Fri Dec 11 04:23:07 2020] [<ffffffffa94ec2f8>] ? enqueue_hrtimer+0x38/0x80 [Fri Dec 11 04:23:07 2020] [<ffffffffa9a220ad>] ? do_softirq+0x10d/0x2b0 [Fri Dec 11 04:23:07 2020] [<ffffffffa9481e52>] ? irq_exit+0xc2/0xd0 [Fri Dec 11 04:23:07 2020] [<ffffffffa9a21b2c>] ? smp_apic_timer_interrupt+0x4c/0x60 [Fri Dec 11 04:23:07 2020] [<ffffffffa9a2025e>] ? apic_timer_interrupt+0x9e/0xb0 [Fri Dec 11 04:23:07 2020] <EOI> [Fri Dec 11 04:23:07 2020] ---[ end trace 9fe5a7fbc0d2ec75 ]--- [Fri Dec 11 04:23:07 2020] e1000 0000:00:03.0 enp0s3: Reset adapter [Fri Dec 11 04:23:09 2020] e1000: enp0s3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX [Fri Dec 11 04:32:22 2020] e1000 0000:00:03.0 enp0s3: Reset adapter [Fri Dec 11 04:32:24 2020] e1000: enp0s3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX [Fri Dec 11 16:28:48 2020] e1000 0000:00:03.0 enp0s3: Reset adapter [Fri Dec 11 16:28:50 2020] e1000: enp0s3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX [Fri Dec 11 16:35:12 2020] e1000 0000:00:03.0 enp0s3: Reset adapter [Fri Dec 11 16:35:14 2020] e1000: enp0s3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX [Fri Dec 11 16:54:03 2020] e1000 0000:00:03.0 enp0s3: Reset adapter [Fri Dec 11 16:54:05 2020] e1000: enp0s3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX [Sun Dec 13 04:55:27 2020] e1000 0000:00:03.0 enp0s3: Reset adapter [Sun Dec 13 04:55:29 2020] e1000: enp0s3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX [Sun Dec 13 07:44:21 2020] e1000 0000:00:03.0 enp0s3: Reset adapter [Sun Dec 13 07:44:23 2020] e1000: enp0s3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX [Sun Dec 13 08:53:51 2020] e1000 0000:00:03.0 enp0s3: Reset adapter [Sun Dec 13 08:53:53 2020] e1000: enp0s3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX [Sun Dec 13 08:54:34 2020] e1000 0000:00:03.0 enp0s3: Reset adapter [Sun Dec 13 08:54:36 2020] e1000: enp0s3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX [Sun Dec 13 09:03:54 2020] e1000 0000:00:03.0 enp0s3: Reset adapter [Sun Dec 13 09:03:56 2020] e1000: enp0s3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX [Sun Dec 13 09:08:37 2020] e1000 0000:00:03.0 enp0s3: Reset adapter [Sun Dec 13 09:08:39 2020] e1000: enp0s3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX [Sun Dec 13 09:36:31 2020] e1000 0000:00:03.0 enp0s3: Reset adapter [Sun Dec 13 09:36:33 2020] e1000: enp0s3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX [Sun Dec 13 09:40:53 2020] e1000 0000:00:03.0 enp0s3: Reset adapter [Sun Dec 13 09:40:55 2020] e1000: enp0s3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX [Sun Dec 13 11:58:12 2020] e1000 0000:00:03.0 enp0s3: Reset adapter [Sun Dec 13 11:58:15 2020] e1000: enp0s3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX [Sun Dec 13 12:00:26 2020] e1000 0000:00:03.0 enp0s3: Reset adapter [Sun Dec 13 12:00:28 2020] e1000: enp0s3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX [Sun Dec 13 12:21:04 2020] e1000 0000:00:03.0 enp0s3: Reset adapter [Sun Dec 13 12:21:06 2020] e1000: enp0s3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX [Sun Dec 13 12:29:08 2020] e1000 0000:00:03.0 enp0s3: Reset adapter [Sun Dec 13 12:29:11 2020] e1000: enp0s3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX [Sun Dec 13 12:30:44 2020] e1000 0000:00:03.0 enp0s3: Reset adapter [Sun Dec 13 12:30:47 2020] e1000: enp0s3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX [Sun Dec 13 12:35:17 2020] e1000 0000:00:03.0 enp0s3: Reset adapter [Sun Dec 13 12:35:19 2020] e1000: enp0s3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX [Sun Dec 13 12:52:21 2020] e1000 0000:00:03.0 enp0s3: Reset adapter [Sun Dec 13 12:52:23 2020] e1000: enp0s3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX [Sun Dec 13 13:03:06 2020] e1000 0000:00:03.0 enp0s3: Reset adapter [Sun Dec 13 13:03:08 2020] e1000: enp0s3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX [Sun Dec 13 13:11:38 2020] e1000 0000:00:03.0 enp0s3: Reset adapter [Sun Dec 13 13:11:40 2020] e1000: enp0s3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX [Sun Dec 13 13:45:41 2020] e1000 0000:00:03.0 enp0s3: Reset adapter [Sun Dec 13 13:45:43 2020] e1000: enp0s3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX [Sun Dec 13 18:07:16 2020] TCP: enp0s3: Driver has suspect GRO implementation, TCP performance may be compromised. [Mon Dec 14 04:15:37 2020] e1000 0000:00:03.0 enp0s3: Reset adapter [Mon Dec 14 04:15:39 2020] e1000: enp0s3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX [Mon Dec 14 04:56:36 2020] e1000 0000:00:03.0 enp0s3: Reset adapter [Mon Dec 14 04:56:38 2020] e1000: enp0s3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX [Tue Dec 15 04:16:56 2020] e1000 0000:00:03.0 enp0s3: Reset adapter [Tue Dec 15 04:16:59 2020] e1000: enp0s3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX [Tue Dec 15 08:18:54 2020] e1000 0000:00:03.0 enp0s3: Reset adapter [Tue Dec 15 08:18:56 2020] e1000: enp0s3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX [Tue Dec 15 08:52:40 2020] e1000 0000:00:03.0 enp0s3: Reset adapter [Tue Dec 15 08:52:42 2020] e1000: enp0s3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX [Wed Dec 16 10:13:49 2020] e1000 0000:00:03.0 enp0s3: Reset adapter [Wed Dec 16 10:13:51 2020] e1000: enp0s3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX [Wed Dec 16 13:51:19 2020] e1000 0000:00:03.0 enp0s3: Reset adapter [Wed Dec 16 13:51:21 2020] e1000: enp0s3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX [Thu Dec 17 10:22:05 2020] e1000 0000:00:03.0 enp0s3: Reset adapter [Thu Dec 17 10:22:07 2020] e1000: enp0s3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX

Version 1, edited 3 years ago by Sanitariu (previous) (next) (diff)
Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use