I'm having this issue as well, with the 5.0.0-16-generic kernel on amd64 and an Intel I219-V NIC using the e1000e driver. I have a test case that can reproduce it somewhat reliably (involving a lot of concurrent back- and-forth chatter on my LAN).
I was able to reproduce it even after this command: ethtool -K enp0s31f6 gso off gro off tso off rx off tx off although anecdotally, disabling those features makes reproduction harder. After the original oops with backtrace (similar to the one posted above), the problem presents simply as: Jun 14 03:54:43 good-fortune systemd-networkd[7815]: enp0s31f6: Lost carrier Jun 14 03:54:43 good-fortune systemd-networkd[7815]: enp0s31f6: DHCP lease lost with no further backtraces. -- 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/1832101 Title: systemd-networkd: Lost carrier e1000 Status in linux package in Ubuntu: Confirmed Bug description: Just installed a fresh installation of ubuntu 19 on our server and we're having a lot of carrier-lost erros. There is no really good indicaton why this is hapening. Tried the following : disabled ipv6 (just to be sure), on nic set GSO,GRO,TSO to off. removed netplan, switched to systemd-networkd and added configurewithoutcarrier to true, the option ignorecarrierlost is not accepted by systemd. Description: Ubuntu 19.04 Release: 19.04 Kernel Log Jun 8 12:11:17 mc2 kernel: [30304.199050] ------------[ cut here ]------------ Jun 8 12:11:17 mc2 kernel: [30304.199052] NETDEV WATCHDOG: eno1 (e1000e): transmit queue 0 timed out Jun 8 12:11:17 mc2 kernel: [30304.199062] WARNING: CPU: 8 PID: 0 at net/sched/sch_generic.c:461 dev_watchdog+0x221/0x230 Jun 8 12:11:17 mc2 kernel: [30304.199062] Modules linked in: intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 crypto_simd cryptd glue_helper intel_cstate intel_rapl_perf intel_wmi_thunderbolt wmi_bmof intel_pch_thermal mac_hid acpi_pad ip6t_REJE CT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt ipt_REJECT nf_reject_ipv4 nf_log_ipv4 nf_log_common xt_LOG xt_multiport xt_limit xt_tcpudp xt_addrtype sch_fq_codel xt_conntrack ip6 table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_filter bpfilter ip_ tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear raid1 e1000e nvme ahci i2c_i801 libahci nvme_core wmi video pinctrl_cannonlake pinctrl_intel Jun 8 12:11:17 mc2 kernel: [30304.199080] CPU: 8 PID: 0 Comm: swapper/8 Not tainted 5.0.0-16-generic #17-Ubuntu Jun 8 12:11:17 mc2 kernel: [30304.199081] Hardware name: Gigabyte Technology Co., Ltd. B360 HD3P-LM/B360HD3PLM-CF, BIOS F4 HZ 04/30/2019 Jun 8 12:11:17 mc2 kernel: [30304.199082] RIP: 0010:dev_watchdog+0x221/0x230 Jun 8 12:11:17 mc2 kernel: [30304.199083] Code: 00 49 63 4e e0 eb 92 4c 89 ef c6 05 9a 92 f0 00 01 e8 13 38 fc ff 89 d9 4c 89 ee 48 c7 c7 68 5e da 95 48 89 c2 e8 71 f1 79 ff <0f> 0b eb c0 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 Jun 8 12:11:17 mc2 kernel: [30304.199083] RSP: 0018:ffff93adff203e68 EFLAGS: 00010286 Jun 8 12:11:17 mc2 kernel: [30304.199084] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000006 Jun 8 12:11:17 mc2 kernel: [30304.199084] RDX: 0000000000000007 RSI: 0000000000000096 RDI: ffff93adff216440 Jun 8 12:11:17 mc2 kernel: [30304.199084] RBP: ffff93adff203e98 R08: 0000000000000001 R09: 0000000000000c61 Jun 8 12:11:17 mc2 kernel: [30304.199085] R10: 0000000000000004 R11: 0000000000000000 R12: 0000000000000001 Jun 8 12:11:17 mc2 kernel: [30304.199085] R13: ffff93adec480000 R14: ffff93adec4804c0 R15: ffff93adeca74080 Jun 8 12:11:17 mc2 kernel: [30304.199086] FS: 0000000000000000(0000) GS:ffff93adff200000(0000) knlGS:0000000000000000 Jun 8 12:11:17 mc2 kernel: [30304.199086] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jun 8 12:11:17 mc2 kernel: [30304.199086] CR2: 00007f7783ea4300 CR3: 000000043920e003 CR4: 00000000003606e0 Jun 8 12:11:17 mc2 kernel: [30304.199087] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Jun 8 12:11:17 mc2 kernel: [30304.199087] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Jun 8 12:11:17 mc2 kernel: [30304.199087] Call Trace: Jun 8 12:11:17 mc2 kernel: [30304.199088] <IRQ> Jun 8 12:11:17 mc2 kernel: [30304.199090] ? pfifo_fast_enqueue+0x120/0x120 Jun 8 12:11:17 mc2 kernel: [30304.199091] call_timer_fn+0x30/0x130 Jun 8 12:11:17 mc2 kernel: [30304.199092] run_timer_softirq+0x3e4/0x420 Jun 8 12:11:17 mc2 kernel: [30304.199093] ? ktime_get+0x3c/0xa0 Jun 8 12:11:17 mc2 kernel: [30304.199095] ? lapic_next_deadline+0x26/0x30 Jun 8 12:11:17 mc2 kernel: [30304.199096] ? clockevents_program_event+0x93/0xf0 Jun 8 12:11:17 mc2 kernel: [30304.199097] __do_softirq+0xdc/0x2f3 Jun 8 12:11:17 mc2 kernel: [30304.199099] irq_exit+0xc0/0xd0 Jun 8 12:11:17 mc2 kernel: [30304.199099] smp_apic_timer_interrupt+0x79/0x140 Jun 8 12:11:17 mc2 kernel: [30304.199100] apic_timer_interrupt+0xf/0x20 Jun 8 12:11:17 mc2 kernel: [30304.199101] </IRQ> Jun 8 12:11:17 mc2 kernel: [30304.199102] RIP: 0010:cpuidle_enter_state+0xbd/0x450 Jun 8 12:11:17 mc2 kernel: [30304.199103] Code: ff e8 87 36 87 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 63 03 00 00 31 ff e8 ba 65 8d ff fb 66 0f 1f 44 00 00 < 45> 85 ed 0f 88 8d 02 00 00 49 63 cd 48 8b 75 d0 48 2b 75 c8 48 8d Jun 8 12:11:17 mc2 kernel: [30304.199103] RSP: 0018:ffffbd934635be60 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff13 Jun 8 12:11:17 mc2 kernel: [30304.199104] RAX: ffff93adff222d80 RBX: ffffffff96153c80 RCX: 000000000000001f Jun 8 12:11:17 mc2 kernel: [30304.199104] RDX: 00001b8fbf04fa77 RSI: 00000000238e38e3 RDI: 0000000000000000 Jun 8 12:11:17 mc2 kernel: [30304.199104] RBP: ffffbd934635bea0 R08: 0000000000000000 R09: 0000000000022640 Jun 8 12:11:17 mc2 kernel: [30304.199105] R10: 00006352c2dadb3e R11: ffff93adff221c04 R12: ffff93adff22d800 Jun 8 12:11:17 mc2 kernel: [30304.199105] R13: 0000000000000006 R14: ffffffff96153ed8 R15: ffffffff96153ec0 Jun 8 12:11:17 mc2 kernel: [30304.199106] cpuidle_enter+0x17/0x20 Jun 8 12:11:17 mc2 kernel: [30304.199108] call_cpuidle+0x23/0x40 Jun 8 12:11:17 mc2 kernel: [30304.199109] do_idle+0x23a/0x280 Jun 8 12:11:17 mc2 kernel: [30304.199110] cpu_startup_entry+0x1d/0x20 Jun 8 12:11:17 mc2 kernel: [30304.199111] start_secondary+0x1ab/0x200 Jun 8 12:11:17 mc2 kernel: [30304.199112] secondary_startup_64+0xa4/0xb0 Jun 8 12:11:17 mc2 kernel: [30304.199113] ---[ end trace c329b3b416c2fdf3 ]--- Jun 8 12:11:17 mc2 kernel: [30304.199121] e1000e 0000:00:1f.6 eno1: Reset adapter unexpectedly Jun 8 12:11:21 mc2 kernel: [30308.410432] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx --- ProblemType: Bug AlsaDevices: total 0 crw-rw---- 1 root audio 116, 1 Jun 9 03:15 seq crw-rw---- 1 root audio 116, 33 Jun 9 03:15 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 19.04 HibernationDevice: IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. B360 HD3P-LM Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-16-generic root=UUID=272b751b-985b-4a98-b5a3-635ea2ec16c5 ro netcfg/do_not_use_netplan=true nomodeset consoleblank=0 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-16-generic N/A linux-backports-modules-5.0.0-16-generic N/A linux-firmware 1.178.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: disco Uname: Linux 5.0.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/30/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 HZ dmi.board.asset.tag: Default string dmi.board.name: B360HD3PLM-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4HZ:bd04/30/2019:svnGigabyteTechnologyCo.,Ltd.:pnB360HD3P-LM:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB360HD3PLM-CF:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B360 HD3P-LM dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832101/+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
