Background: RHEL version: Red Hat Enterprise Linux Server release 7.5 (Maipo) DPDK version: 17.11.4 Current Mellanox driver version: 4.0.2 lspci | grep Mell 00:06.0 Ethernet controller: Mellanox Technologies MT27500/MT27520 Family [ConnectX-3/ConnectX-3 Pro Virtual Function] 00:07.0 Ethernet controller: Mellanox Technologies MT27500/MT27520 Family [ConnectX-3/ConnectX-3 Pro Virtual Function] 00:08.0 Ethernet controller: Mellanox Technologies MT27500/MT27520 Family [ConnectX-3/ConnectX-3 Pro Virtual Function] 00:09.0 Ethernet controller: Mellanox Technologies MT27500/MT27520 Family [ConnectX-3/ConnectX-3 Pro Virtual Function]
We have a system with above configuration running, we have below infiniband devices in place before upgrade. ls -lrt /sys/class/infiniband/ total 0 lrwxrwxrwx 1 root root 0 Jan 29 13:06 mlx4_3 -> ../../devices/pci0000:00/0000:00:09.0/infiniband/mlx4_3 lrwxrwxrwx 1 root root 0 Jan 29 13:06 mlx4_2 -> ../../devices/pci0000:00/0000:00:08.0/infiniband/mlx4_2 lrwxrwxrwx 1 root root 0 Jan 29 13:06 mlx4_1 -> ../../devices/pci0000:00/0000:00:07.0/infiniband/mlx4_1 lrwxrwxrwx 1 root root 0 Jan 29 13:06 mlx4_0 -> ../../devices/pci0000:00/0000:00:06.0/infiniband/mlx4_0 When we upgrade Mellanox driver to mlnx-en-4.4-2.0.7.0 and restart the /etc/init.d/mlnx-en.d, we see all above devices get removed and hence ibv_get_device_list function is not able to find any device. Please note we have used image mlnx-en-4.4-2.0.7.0-rhel7.5-x86_64.iso to upgrade the drivers. Has anyone faced this type of problems earlier, are there any explicit steps we need to perform to make sure the infiniband devices are not removed during upgrade of Mellanox drivers? Regards, Kiran This message, including attachments, is CONFIDENTIAL. It may also be privileged or otherwise protected by law. If you received this email by mistake please let us know by reply and then delete it from your system; you should not copy it or disclose its contents to anyone. All messages sent to and from Enea may be monitored to ensure compliance with internal policies and to protect our business. Emails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of email transmission. Anyone who communicates with us by email accepts these risks.
