Comment 7 for bug 1779756

I have a similar problem.

My setup is a little different:
        67:00.0 Ethernet controller [0200]: Intel Corporation Ethernet Connection X722 for 10GBASE-T [8086:37d2] (rev 09)
        Subsystem: Fujitsu Technology Solutions Ethernet Connection X722 for 10GBASE-T [1734:1230]
        Kernel driver in use: i40e
        Kernel modules: i40e

on a "Fujitsu PRIMERGY RX2540 M4", but the driver in use is the same.

My setup (two of these cards with LACP) worked with Ubuntu 16.04 with kernel 4.13, but with 4.15, the card is behaving strangely, even without LACP. Update to ubuntu 18.04.1 does not solve the problem, nor does running any other kernel (I tried up to 4.19rc5) with 18.04.1.

The behavior for me is the following: after boot, the network does not work at all (no ping in either direction, DNS name resolution seems to be work though). Then, when trying to ping from or to the machine, at some point, that starts to work for *some* IPs. It seems that the issue gets smaller as soon as I have a connection with some other server and put some load on the network.

I already updated the firmware of the card, but that didn't help.
Before, it was
fw 3.1.54559 api 1.5 nvm 3.2d 0x80000b5f 1.1693.0
and I then updated to
fw 3.1.52520 api 1.5 nvm 3.33 0x800010ef 1.1876.0.

I also tried it with a live image of ubuntu 16.04.5 and 18.04.1; in both cases, I do not get a stable network connection.