I tested 4.4.0-72 from above and got the same results as 4.4.0-71.

In the process of testing 4.4.0-71 more, I found all is not as well as
we assumed. At first deployment everything seems to be fine. And after
most reboots, we are still able to ping across both interfaces. But
bringing interfaces up and down seems to intermittently bring about the
issue of not being able to ping the interfaces. I cannot seem to find a
pattern of replicated it breaking or even resolving. Sometimes rebooting
is required and even then, sometimes rebooting twice. Other times
bringing up and down the 2 interfaces in some random pattern will allow
both interfaces to be pinged.

One scenario I can replicate is if both enP8p1s0 and enP8p1s0d1 are up
and pingable, if I bring down enP8p1s0, both will become unpingable.
Bringing enP8p1s0 back up does not resolve anything. Bringing enP8p1s0
up and then enP8p1s0d1 down will allow enP8p1s0 to be pingable. Bringing
enP8p1s0d1 up does not make it become bootable. Only after bringing
enP8p1s0 down, then back up, then bringing enP8p1s0d1 up will both
become pingable.

I do not think it is possible to have enP8p1s0d1 up and pingable by
itself. It almost acts like a slave to enP8p1s0.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1677337

Title:
  Mellanox Technologies MT27500 Family [ConnectX-3] no network
  connectivity

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1677337/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to