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
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
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
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:
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
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
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:
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]:
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:
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"
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:
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
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
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
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.
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,
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
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
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
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:
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
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
** 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:
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:
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
25 matches
Mail list logo
