From: Kiran Shinde <Kiran.Shinde@enea.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-users] Upgrading the Mellanox drivers to v 4.4.3 removes infiniband devices
Date: Tue, 2 Feb 2021 05:25:59 +0000 [thread overview]
Message-ID: <DB7PR03MB42518E9D877D7C89473D9BB9F6B59@DB7PR03MB4251.eurprd03.prod.outlook.com> (raw)
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.
next reply other threads:[~2021-02-07 9:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-02 5:25 Kiran Shinde [this message]
2021-02-07 12:23 ` Raslan Darawsheh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DB7PR03MB42518E9D877D7C89473D9BB9F6B59@DB7PR03MB4251.eurprd03.prod.outlook.com \
--to=kiran.shinde@enea.com \
--cc=users@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).