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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1677337 Title: Mellanox Technologies MT27500 Family [ConnectX-3] no network connectivity Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: In Progress Status in linux source package in Zesty: In Progress Bug description: After a fresh install of Ubuntu 16.04.2 with 4.4.0-70-generic, the Mellanox Technologies MT27500 Family [ConnectX-3] card is detected, brought up and assigned an ip via MAAS. This is where functionality stops on this kernel. Pinging the MAAS server which is connected directly(no switch) fails. There's no traffic from tcpdump. linux-image-generic-hwe-16.04 4.8.0.44.16 fails mainline kernel 4.10.0-041000-generic fails mainline kernel 4.11.0-041100rc1-generic resolves the issue. Both the test server (ppc64le) and MAAS server(amd64) need the upgraded kernel to work. === 4.4.0-70-generic === lspci -v 0008:01:00.0 Ethernet controller: Mellanox Technologies MT27500 Family [ConnectX-3] Subsystem: IBM MT27500 Family [ConnectX-3] Flags: bus master, fast devsel, latency 0, IRQ 473 Memory at 3fe200000000 (64-bit, non-prefetchable) [size=1M] Memory at 240000000000 (64-bit, prefetchable) [size=128M] [virtual] Expansion ROM at 3fe200100000 [disabled] [size=1M] Capabilities: <access denied> Kernel driver in use: mlx4_core Kernel modules: mlx4_core ethtool enP8p1s0 Settings for enP8p1s0: Supported ports: [ FIBRE ] Supported link modes: 1000baseKX/Full 10000baseKX4/Full 10000baseKR/Full 40000baseCR4/Full 40000baseSR4/Full 56000baseCR4/Full 56000baseSR4/Full Supported pause frame use: Symmetric Receive-only Supports auto-negotiation: Yes Advertised link modes: 1000baseKX/Full 10000baseKX4/Full 10000baseKR/Full 40000baseCR4/Full 40000baseSR4/Full Advertised pause frame use: Symmetric Advertised auto-negotiation: Yes Link partner advertised link modes: 40000baseCR4/Full Link partner advertised pause frame use: No Link partner advertised auto-negotiation: Yes Speed: 40000Mb/s Duplex: Full Port: Direct Attach Copper PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: d Wake-on: d Current message level: 0x00000014 (20) link ifdown Link detected: yes dmesg [ 3.494435] mlx4_core: Mellanox ConnectX core driver v2.2-1 (Feb, 2014) [ 3.494624] mlx4_core: Initializing 0008:01:00.0 [ 3.494760] mlx4_core 0008:01:00.0: Using 64-bit DMA iommu bypass [ 8.294713] mlx4_core 0008:01:00.0: PCIe link speed is 8.0GT/s, device supports 8.0GT/s [ 8.294897] mlx4_core 0008:01:00.0: PCIe link width is x8, device supports x8 [ 8.472682] mlx4_en: Mellanox ConnectX HCA Ethernet driver v2.2-1 (Feb 2014) [ 8.472907] mlx4_en 0008:01:00.0: Activating port:1 [ 8.481531] mlx4_en: 0008:01:00.0: Port 1: Using 256 TX rings [ 8.481661] mlx4_en: 0008:01:00.0: Port 1: Using 8 RX rings [ 8.481694] mlx4_en: 0008:01:00.0: Port 1: frag:0 - size:1522 prefix:0 stride:1536 [ 8.481899] mlx4_en: 0008:01:00.0: Port 1: Initializing port [ 8.482320] mlx4_en 0008:01:00.0: registered PHC clock [ 8.485058] mlx4_en 0008:01:00.0: Activating port:2 [ 8.491716] mlx4_en: 0008:01:00.0: Port 2: Using 256 TX rings [ 8.491760] mlx4_en: 0008:01:00.0: Port 2: Using 8 RX rings [ 8.491791] mlx4_en: 0008:01:00.0: Port 2: frag:0 - size:1522 prefix:0 stride:1536 [ 8.503650] mlx4_en: 0008:01:00.0: Port 2: Initializing port [ 8.511021] mlx4_core 0008:01:00.0 enP8p1s0: renamed from eth0 [ 8.530146] mlx4_core 0008:01:00.0 enP8p1s0d1: renamed from eth1 === 4.11.0-041100rc1-generic === lspci -v 0008:01:00.0 Ethernet controller: Mellanox Technologies MT27500 Family [ConnectX-3] Subsystem: IBM MT27500 Family [ConnectX-3] Flags: bus master, fast devsel, latency 0, IRQ 473 Memory at 3fe200000000 (64-bit, non-prefetchable) [size=1M] Memory at 240000000000 (64-bit, prefetchable) [size=128M] [virtual] Expansion ROM at 3fe200100000 [disabled] [size=1M] Capabilities: <access denied> Kernel driver in use: mlx4_core Kernel modules: mlx4_core ethtool enP8p1s0 Settings for enP8p1s0: Supported ports: [ FIBRE ] Supported link modes: 1000baseKX/Full 10000baseKX4/Full 10000baseKR/Full 40000baseCR4/Full 40000baseSR4/Full 56000baseCR4/Full 56000baseSR4/Full Supported pause frame use: Symmetric Receive-only Supports auto-negotiation: Yes Advertised link modes: 1000baseKX/Full 10000baseKX4/Full 10000baseKR/Full 40000baseCR4/Full 40000baseSR4/Full Advertised pause frame use: Symmetric Advertised auto-negotiation: Yes Link partner advertised link modes: 40000baseCR4/Full Link partner advertised pause frame use: No Link partner advertised auto-negotiation: Yes Speed: 40000Mb/s Duplex: Full Port: Direct Attach Copper PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: d Wake-on: d Current message level: 0x00000014 (20) link ifdown Link detected: yes dmesg [ 3.934477] mlx4_core: Mellanox ConnectX core driver v2.2-1 (Feb, 2014) [ 3.934659] mlx4_core: Initializing 0008:01:00.0 [ 8.740796] mlx4_core 0008:01:00.0: PCIe link speed is 8.0GT/s, device supports 8.0GT/s [ 8.740993] mlx4_core 0008:01:00.0: PCIe link width is x8, device supports x8 [ 8.915288] mlx4_en: Mellanox ConnectX HCA Ethernet driver v2.2-1 (Feb 2014) [ 8.915626] mlx4_en 0008:01:00.0: Activating port:1 [ 8.924026] mlx4_en: 0008:01:00.0: Port 1: Using 256 TX rings [ 8.924176] mlx4_en: 0008:01:00.0: Port 1: Using 8 RX rings [ 8.924230] mlx4_en: 0008:01:00.0: Port 1: frag:0 - size:1522 prefix:0 stride:1536 [ 8.924427] mlx4_en: 0008:01:00.0: Port 1: Initializing port [ 8.924680] mlx4_en 0008:01:00.0: registered PHC clock [ 8.926434] mlx4_en 0008:01:00.0: Activating port:2 [ 8.933681] mlx4_en: 0008:01:00.0: Port 2: Using 256 TX rings [ 8.933787] mlx4_en: 0008:01:00.0: Port 2: Using 8 RX rings [ 8.933895] mlx4_en: 0008:01:00.0: Port 2: frag:0 - size:1522 prefix:0 stride:1536 [ 8.950476] mlx4_en: 0008:01:00.0: Port 2: Initializing port [ 8.953686] mlx4_core 0008:01:00.0 enP8p1s0d1: renamed from eth1 [ 8.980067] mlx4_core 0008:01:00.0 enP8p1s0: renamed from eth0 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-70-generic 4.4.0-70.91 ProcVersionSignature: Ubuntu 4.4.0-70.91-generic 4.4.49 Uname: Linux 4.4.0-70-generic ppc64le AlsaDevices: total 0 crw-rw---- 1 root audio 116, 1 Mar 29 17:49 seq crw-rw---- 1 root audio 116, 33 Mar 29 17:49 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.5 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Mar 29 17:54:22 2017 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: root=UUID=a287c2bd-7e5a-488c-8921-5cf86aed177a ro ProcLoadAvg: 0.11 0.24 0.15 1/1249 4656 ProcLocks: 1: POSIX ADVISORY WRITE 4054 00:14:799 0 EOF 2: POSIX ADVISORY WRITE 4023 00:14:789 0 EOF 3: POSIX ADVISORY WRITE 1660 00:14:493 0 EOF 4: FLOCK ADVISORY WRITE 4052 00:14:796 0 EOF 5: POSIX ADVISORY WRITE 4126 00:14:807 0 EOF ProcSwaps: Filename Type Size Used Priority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-70-generic (buildd@bos01-ppc64el-022) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #91-Ubuntu SMP Wed Mar 22 12:46:23 UTC 2017 RelatedPackageVersions: linux-restricted-modules-4.4.0-70-generic N/A linux-backports-modules-4.4.0-70-generic N/A linux-firmware 1.157.8 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 3.955 GHz (cpu 79) max: 3.971 GHz (cpu 82) avg: 3.963 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface to firmware cpu_smt: SMT=8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1677337/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
