[Bug 1832101] Re: systemd-networkd: Lost carrier e1000
The issue I mentioned above appears to be caused by the ax88179_178a (and in turn triggering an issue in the e1000e driver) -- I can reproduce it with just two ax88179_178a. It might be a memory leak, I'm not sure. When I modify the configuration to use two vlans on the e1000e instead of a second interface, I still get device resets, but that *may* be resolved by turning off options with ethtool. I'm waiting to see. tl;dr computers are terrible, everything sucks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832101 Title: systemd-networkd: Lost carrier e1000 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832101] Re: systemd-networkd: Lost carrier e1000
Is there any additional information we should collect in order to report this to LKML? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832101 Title: systemd-networkd: Lost carrier e1000 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832101] Re: systemd-networkd: Lost carrier e1000
For me personally, the issue only appeared after upgrading from 18.04 -> 19.04. Based on dpkg.log, the last working kernel I had was either 4.15.0-45.48 or 4.15.0.43.45. I haven't tried downgrading the kernel yet: the machine is headless and manual interventions are a pain. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832101 Title: systemd-networkd: Lost carrier e1000 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832101] Re: systemd-networkd: Lost carrier e1000
Does any previous kernel work without this issue? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832101 Title: systemd-networkd: Lost carrier e1000 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832101] Re: systemd-networkd: Lost carrier e1000
Sorry for the delay, I was busy. The out-of-tree e1000e driver does not resolve the issue. Running, for example, "wget http://ping.online.net/1000Mo.dat -O /dev/null" from the host, with all traffic on the non-e1000e interface, and no traffic on the e1000e interface, causes the e1000e interface to reset. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832101 Title: systemd-networkd: Lost carrier e1000 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832101] Re: systemd-networkd: Lost carrier e1000
I have already tried mainline kernels, and every combination of ethtool knob-twiddling. No luck. Disabling TSO *may* make the 'random' e1000e resets happen less frequently (it's hard to say), but wget/apt-get *on the other interface* reliably trigger the e1000e to hang and reset regardless of settings. I will try the out-of-tree driver this evening. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832101 Title: systemd-networkd: Lost carrier e1000 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832101] Re: systemd-networkd: Lost carrier e1000
1) Please try disabling TSO. Multiple users reported positive results after TSO is disabled. 2) Please try mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2-rc5/ 3) Please try out-of-tree e1000e, which has some extra sauce not in upstream: https://sourceforge.net/projects/e1000/files/e1000e%20stable/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832101 Title: systemd-networkd: Lost carrier e1000 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832101] Re: systemd-networkd: Lost carrier e1000
Ah, sorry, it's also an I219-V 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:5904] (rev 02) 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) 00:08.0 System peripheral [0880]: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model [8086:1911] 00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller [8086:9d2f] (rev 21) 00:14.2 Signal processing controller [1180]: Intel Corporation Sunrise Point-LP Thermal subsystem [8086:9d31] (rev 21) 00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP CSME HECI #1 [8086:9d3a] (rev 21) 00:17.0 SATA controller [0106]: Intel Corporation Sunrise Point-LP SATA Controller [AHCI mode] [8086:9d03] (rev 21) 00:1c.0 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port #1 [8086:9d10] (rev f1) 00:1f.0 ISA bridge [0601]: Intel Corporation Intel(R) 100 Series Chipset Family LPC Controller/eSPI Controller - 9D4E [8086:9d4e] (rev 21) 00:1f.2 Memory controller [0580]: Intel Corporation Sunrise Point-LP PMC [8086:9d21] (rev 21) 00:1f.4 SMBus [0c05]: Intel Corporation Sunrise Point-LP SMBus [8086:9d23] (rev 21) 00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection (4) I219-V [8086:15d8] (rev 21) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832101 Title: systemd-networkd: Lost carrier e1000 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832101] Re: systemd-networkd: Lost carrier e1000
Please provide the output of `lspci -nn`. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832101 Title: systemd-networkd: Lost carrier e1000 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832101] Re: systemd-networkd: Lost carrier e1000
I might have the same issue, I'm not sure. I have a Ubuntu 19.04 server with an onboard e1000e interface and a usb ax88179_178a interface, routing traffic between the two. The e1000e interface drops a couple of times a day and I see "Detected Hardware Unit Hang" / "Reset adapter unexpectedly" messages in syslog. I don't know what triggers that, there's no significant traffic in my graphs. I can trigger the e1000e to drop reliably, but the trigger doesn't make sense: I can send as much traffic as I want from ax88179_178a through e1000e and vice versa. I can send as much traffic as I want to the server itself from the e1000e. If I send any moderate amount of traffic to the server from the ax88179_178a, then the e1000e drops. For example, apt- get will cause the e1000e to drop. The server is fine, the ax88179_178a is fine, the apt-get or wget or whatever will complete and eventually my TCP session will usually recover after the e1000e resets. If the files are large enough, this may happen several times. It doesn't seem to matter if it's writing to disk or to /dev/null. I have swapped out the switch, the cable, and the USB ethernet interface (both for another ax88179_178a and some other chipset I don't remember.) I have tried kernels from the mainline ppa. I have tried every combination of ethtool knob-twiddling. No luck. The issue first appeared for me after upgrading from 18.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832101 Title: systemd-networkd: Lost carrier e1000 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832101] Re: systemd-networkd: Lost carrier e1000
It's challenging for me to test mainline kernels because it means losing access to ZFS, but I can probably do this later this week. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832101 Title: systemd-networkd: Lost carrier e1000 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832101] Re: systemd-networkd: Lost carrier e1000
i'm testing with settings ethtool -K eno1 gso off gro off tso off rx off tx off Few days ago my provider replaced all hardware, and attach network to another switch port. Also network cable is replaced Cannot test kernel at this moment. System is already live. Maybe Shivaram Lingamneni can run some tests -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832101 Title: systemd-networkd: Lost carrier e1000 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832101] Re: systemd-networkd: Lost carrier e1000
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2-rc5/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832101 Title: systemd-networkd: Lost carrier e1000 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832101] Re: systemd-networkd: Lost carrier e1000
ethtool reports "highdma: on [fixed]", and won't let me switch it off. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832101 Title: systemd-networkd: Lost carrier e1000 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832101] Re: systemd-networkd: Lost carrier e1000
Today two times cost carrier. Seems that Shivaram Lingamneni is right. With the changed settings there are still lost carriers, but not that often. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832101 Title: systemd-networkd: Lost carrier e1000 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832101] Re: systemd-networkd: Lost carrier e1000
I also installed networkd-dispatcher and added in the directory routable.d a file with #!/bin/sh ethtool -K eno1 gso off gro off tso off rx off tx off so i don't have to manual change the settings when rebooting. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832101 Title: systemd-networkd: Lost carrier e1000 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832101] Re: systemd-networkd: Lost carrier e1000
Can you check the nic settings and see if hidma is fixed or not? (ethtool -k ) If it is not fixed, then try disable it ethtool -K highdma off https://lauri.xn--vsandi-pxa.com/2016/02/fixing-broadcom-bcm5762-on- ubuntu.html Another option is to disable netplan and switch to networkd-systemd so you can set (this is the first thing i tried) [NETWORK] IgnoreCarrierLoss=true ConfigureWithoutCarrier=true -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832101 Title: systemd-networkd: Lost carrier e1000 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832101] Re: systemd-networkd: Lost carrier e1000
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832101 Title: systemd-networkd: Lost carrier e1000 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832101] Re: systemd-networkd: Lost carrier e1000
yes and no. I did disabled tso, but still had some problems, after that i enabled tso and disabled rx/tx checksum That also did not resolve the issue, so as last resort i disabled GSO,GRO,TSO offload and ,RX,TX checksum check ethtool -K gso off gro off tso off rx off tx off -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832101 Title: systemd-networkd: Lost carrier e1000 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832101] Re: systemd-networkd: Lost carrier e1000
Does disabling TSO help? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832101 Title: systemd-networkd: Lost carrier e1000 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832101] Re: systemd-networkd: Lost carrier e1000
issue only occurs when there is a high netwerk load. Only disableling rx tx checksum check did not resolve the issue. There is also a older bug for the e1000 with almost the same issue. So seems that this issue is a long and known issue in earlier versions. Also there is a simulair bug (broadcom) where the solution is to disable hi-dma. That option cannot be change on the e1000, so could not try that. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832101 Title: systemd-networkd: Lost carrier e1000 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832101] Re: systemd-networkd: Lost carrier e1000
apport information ** Tags added: apport-collected ** Description changed: 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:93adff203e68 EFLAGS: 00010286 Jun 8 12:11:17 mc2 kernel: [30304.199084] RAX: RBX: RCX: 0006 Jun 8 12:11:17 mc2 kernel: [30304.199084] RDX: 0007 RSI: 0096 RDI: 93adff216440 Jun 8 12:11:17 mc2 kernel: [30304.199084] RBP: 93adff203e98 R08: 0001 R09: 0c61 Jun 8 12:11:17 mc2 kernel: [30304.199085] R10: 0004 R11: R12: 0001 Jun 8 12:11:17 mc2 kernel: [30304.199085] R13: 93adec48 R14: 93adec4804c0 R15: 93adeca74080 Jun 8 12:11:17 mc2 kernel: [30304.199086] FS: () GS:93adff20() knlGS: Jun 8 12:11:17 mc2 kernel: [30304.199086] CS: 0010 DS: ES: CR0: 80050033 Jun 8 12:11:17 mc2 kernel: [30304.199086] CR2: 7f7783ea4300 CR3: 00043920e003 CR4: 003606e0 Jun 8 12:11:17 mc2 kernel: [30304.199087] DR0: DR1: DR2: Jun 8 12:11:17 mc2 kernel: [30304.199087] DR3: DR6: fffe0ff0 DR7: 0400 Jun 8 12:11:17 mc2 kernel: [30304.199087] Call Trace: Jun 8 12:11:17 mc2 kernel: [30304.199088] 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] 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:bd934635be60 EFLAGS: 0246
[Bug 1832101] Re: systemd-networkd: Lost carrier e1000
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832101 Title: systemd-networkd: Lost carrier e1000 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832101] Re: systemd-networkd: Lost carrier e1000
Did resolve this error by disabling GSO,GRO,TSO offload and ,RX,TX checksum check ethtool -K eno1 gso off gro off tso off rx off tx off -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832101 Title: systemd-networkd: Lost carrier e1000 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1832101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832101] Re: systemd-networkd: Lost carrier e1000
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode. To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1832101/+editstatus and add the package name in the text box next to the word Package. [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: bot-comment -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832101 Title: systemd-networkd: Lost carrier e1000 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1832101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
