[Kernel-packages] [Bug 1832101] Re: systemd-networkd: Lost carrier e1000

2019-06-17 Thread Poloskey
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

[Kernel-packages] [Bug 1832101] Re: systemd-networkd: Lost carrier e1000

2019-06-15 Thread Poloskey
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 Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1832101] Re: systemd-networkd: Lost carrier e1000

2019-06-14 Thread Poloskey
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 Kernel

[Kernel-packages] [Bug 1832101] Re: systemd-networkd: Lost carrier e1000

2019-06-14 Thread Poloskey
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

[Kernel-packages] [Bug 1832101] Re: systemd-networkd: Lost carrier e1000

2019-06-13 Thread Poloskey
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

[Kernel-packages] [Bug 1832101] Re: systemd-networkd: Lost carrier e1000

2019-06-12 Thread Poloskey
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

[Kernel-packages] [Bug 1832101] ProcModules.txt

2019-06-10 Thread Poloskey
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1832101/+attachment/5269981/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1832101] ProcEnviron.txt

2019-06-10 Thread Poloskey
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1832101/+attachment/5269979/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1832101] WifiSyslog.txt

2019-06-10 Thread Poloskey
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1832101/+attachment/5269983/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1832101] UdevDb.txt

2019-06-10 Thread Poloskey
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1832101/+attachment/5269982/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1832101] ProcInterrupts.txt

2019-06-10 Thread Poloskey
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1832101/+attachment/5269980/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1832101] ProcCpuinfoMinimal.txt

2019-06-10 Thread Poloskey
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1832101/+attachment/5269978/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1832101] ProcCpuinfo.txt

2019-06-10 Thread Poloskey
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1832101/+attachment/5269977/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1832101] Lspci.txt

2019-06-10 Thread Poloskey
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1832101/+attachment/5269976/+files/Lspci.txt -- 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

[Kernel-packages] [Bug 1832101] CurrentDmesg.txt

2019-06-10 Thread Poloskey
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1832101/+attachment/5269975/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1832101] Re: systemd-networkd: Lost carrier e1000

2019-06-10 Thread Poloskey
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