I am seeing this on a Intel Corporation Ethernet Connection I218-V. DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.2 LTS"
Linux server 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:24 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Jun 27 22:16:23 server kernel: [ 95.305441] ------------[ cut here ]------------ Jun 27 22:16:23 server kernel: [ 95.305445] NETDEV WATCHDOG: eno1 (e1000e): transmit queue 0 timed out Jun 27 22:16:23 server kernel: [ 95.305481] WARNING: CPU: 3 PID: 0 at /build/linux-jmOa1Y/linux-4.15.0/net/sched/sch_generic.c:323 dev_watchdog+0x221/0x230 Jun 27 22:16:23 server kernel: [ 95.305482] Modules linked in: dm_crypt algif_skcipher af_alg nls_iso8859_1 ppdev intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass intel_cstate intel_rapl_perf input_leds serio_raw parport_pc snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic parport snd_hda_intel acpi_pad snd_hda_codec snd_hda_core snd_hwdep mei_me mei snd_pcm shpchp lpc_ich mac_hid snd_timer snd soundcore sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid0 multipath linear raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 hid_generic usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i915 aesni_intel aes_x86_64 crypto_simd Jun 27 22:16:23 server kernel: [ 95.305591] glue_helper mxm_wmi cryptd i2c_algo_bit drm_kms_helper syscopyarea e1000e sysfillrect sysimgblt fb_sys_fops ahci ptp drm libahci pps_core wmi video Jun 27 22:16:23 server kernel: [ 95.305621] CPU: 3 PID: 0 Comm: swapper/3 Not tainted 4.15.0-54-generic #58-Ubuntu Jun 27 22:16:23 server kernel: [ 95.305623] Hardware name: MSI MS-7817/H97M ECO (MS-7817), BIOS V26.8 02/18/2016 Jun 27 22:16:23 server kernel: [ 95.305629] RIP: 0010:dev_watchdog+0x221/0x230 Jun 27 22:16:23 server kernel: [ 95.305631] RSP: 0018:ffff967b9eb83e58 EFLAGS: 00010286 Jun 27 22:16:23 server kernel: [ 95.305635] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000006 Jun 27 22:16:23 server kernel: [ 95.305638] RDX: 0000000000000007 RSI: 0000000000000092 RDI: ffff967b9eb96490 Jun 27 22:16:23 server kernel: [ 95.305641] RBP: ffff967b9eb83e88 R08: 0000000000000001 R09: 000000000000044c Jun 27 22:16:23 server kernel: [ 95.305643] R10: ffffdaca8f63f580 R11: 0000000000000000 R12: 0000000000000001 Jun 27 22:16:23 server kernel: [ 95.305646] R13: ffff967b80934000 R14: ffff967b80934478 R15: ffff967b81020880 Jun 27 22:16:23 server kernel: [ 95.305650] FS: 0000000000000000(0000) GS:ffff967b9eb80000(0000) knlGS:0000000000000000 Jun 27 22:16:23 server kernel: [ 95.305653] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jun 27 22:16:23 server kernel: [ 95.305655] CR2: 0000555b6574ea28 CR3: 000000025a40a006 CR4: 00000000001606e0 Jun 27 22:16:23 server kernel: [ 95.305658] Call Trace: Jun 27 22:16:23 server kernel: [ 95.305662] <IRQ> Jun 27 22:16:23 server kernel: [ 95.305671] ? dev_deactivate_queue.constprop.33+0x60/0x60 Jun 27 22:16:23 server kernel: [ 95.305678] call_timer_fn+0x30/0x130 Jun 27 22:16:23 server kernel: [ 95.305683] run_timer_softirq+0x3fb/0x450 Jun 27 22:16:23 server kernel: [ 95.305689] ? ktime_get+0x43/0xa0 Jun 27 22:16:23 server kernel: [ 95.305697] ? lapic_next_deadline+0x26/0x30 Jun 27 22:16:23 server kernel: [ 95.305705] __do_softirq+0xe4/0x2bb Jun 27 22:16:23 server kernel: [ 95.305713] irq_exit+0xb8/0xc0 Jun 27 22:16:23 server kernel: [ 95.305718] smp_apic_timer_interrupt+0x79/0x130 Jun 27 22:16:23 server kernel: [ 95.305723] apic_timer_interrupt+0x84/0x90 Jun 27 22:16:23 server kernel: [ 95.305725] </IRQ> Jun 27 22:16:23 server kernel: [ 95.305735] RIP: 0010:cpuidle_enter_state+0xa7/0x2f0 Jun 27 22:16:23 server kernel: [ 95.305737] RSP: 0018:ffffa32c41933e68 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff11 Jun 27 22:16:23 server kernel: [ 95.305742] RAX: ffff967b9eba2840 RBX: 0000001630a50a51 RCX: 000000000000001f Jun 27 22:16:23 server kernel: [ 95.305744] RDX: 0000001630a50a51 RSI: fffffffca1795958 RDI: 0000000000000000 Jun 27 22:16:23 server kernel: [ 95.305747] RBP: ffffa32c41933ea8 R08: 0000000000000ee2 R09: 00000000000008f8 Jun 27 22:16:23 server kernel: [ 95.305749] R10: ffffa32c41933e38 R11: 0000000000000edf R12: ffff967b9ebacc00 Jun 27 22:16:23 server kernel: [ 95.305752] R13: 0000000000000005 R14: ffffffffb3d71e38 R15: 0000000000000000 Jun 27 22:16:23 server kernel: [ 95.305760] ? cpuidle_enter_state+0x97/0x2f0 Jun 27 22:16:23 server kernel: [ 95.305767] cpuidle_enter+0x17/0x20 Jun 27 22:16:23 server kernel: [ 95.305774] call_cpuidle+0x23/0x40 Jun 27 22:16:23 server kernel: [ 95.305780] do_idle+0x18c/0x1f0 Jun 27 22:16:23 server kernel: [ 95.305786] cpu_startup_entry+0x73/0x80 Jun 27 22:16:23 server kernel: [ 95.305792] start_secondary+0x1ab/0x200 Jun 27 22:16:23 server kernel: [ 95.305799] secondary_startup_64+0xa5/0xb0 Jun 27 22:16:23 server kernel: [ 95.305802] Code: 37 00 49 63 4e e8 eb 92 4c 89 ef c6 05 19 a6 d8 00 01 e8 d3 33 fd ff 89 d9 48 89 c2 4c 89 ee 48 c7 c7 40 f8 99 b3 e8 4f 7b 80 ff <0f> 0b eb c0 90 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 Jun 27 22:16:23 server kernel: [ 95.305889] ---[ end trace 6c82fad167e817f1 ]--- Jun 27 22:16:23 server kernel: [ 95.305911] e1000e 0000:00:19.0 eno1: Reset adapter unexpectedly Jun 27 22:16:27 server kernel: [ 99.183038] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx Jun 27 22:16:37 server kernel: [ 109.384725] e1000e 0000:00:19.0 eno1: Reset adapter unexpectedly Jun 27 22:16:41 server kernel: [ 113.202828] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx Connected to a d-link DGS-1210-28 Cable path has tested passing both with a hand held and via switch cable diagnostics. This only recently has started occurring, this system has been stable for a long time prior to this issue coming up. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1785171 Title: Intel I219-V Ethernet Interface on Ubuntu Linux Using e1000e Driver keeps Dropping Internet Connection Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: I've turned up many, many new server and workstation systems over the years on both Linux and Windows. Never seen anything like this behaviour I'm witnessing on Ubuntu Server 18.04 before where I simply lose Internet connectivity while using a browser. Ethernet interfaces usually either work or they don't work. I've configured the Intel I219-V Ethernet interface (wired Ethernet connection, there is no wifi on this system) using the e1000e driver for Ubuntu. The Ethernet connection is configured to use NetworkManager via Netplan on Ubuntu 18.04 LTS Server version. ASRock Z370m Pro4 motherboard. The Ethernet interface will drop the Internet connectivity when I'm using either the Firefox or Chrome browser. It usually happens when I'm using the search features of the browser. I can't figure out what would cause this type of behaviour. When the Internet connection drops, the only way to get back Internet connectivity is to disconnect the wired connection using the Ubuntu features and then re-connect (this restarts the NetworkManager service I notice). In the NetworkManager logs I do notice an "auth" error about a file or directory not found. I've never seen that before. Note: The auth error does not coincide with the loss of Internet connectivity, but it does proceed it. Often there can be many hours between the auth error and the actual loss of Internet connectivity. After I reconnect the connection (via re-starting the NetworkManager service) all will be fine for up to a day or so, but then I stress test it with a bunch of searches using the browser and usually I can get the Internet connectivity to drop again. Repeat the disconnect and reconnect process again (aka re-start NetworkManager) and the Internet connectivity will be fine again. The longest I've seen it go without an "Internet connectivity drop" issue is about 36 hours. I notice that the e1000e driver does not list the I219-V as a supported Ethernet interface in the Intel documentation for the Linux version of the driver. I'm not sure why that is. The I219-V is supposed to used another driver, but it's not clear there's a Linux version for of the driver for the I219-V. I'm really disappointed that I've run into this issue with Ubuntu Server LTS 18.04 on this motherboard. I had CentOS Server 7.4 (my standard server OS, a great Linux distro) on this same motherboard for a week with no issues, so I know the motherboard and the I219-V Ethernet interface are 100% good hardware wise and can work properly. CentOS 7.4 uses NetworkManager as the default for managing the Ethernet interface. The only reason I'm using Ubuntu Server 18.04 on this motherboard is because of a specific package that Ubuntu has a newer packaged version than CentOS. CentOS is extremely stable when it comes to basic server functionality. Hopefully, this bug with the I219-V Ethernet interface using the e1000e drive for Linux can be verified and a fix rolled out. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785171/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
