DPDK usage discussions
 help / color / mirror / Atom feed
From: "jiangheng (G)" <jiangheng14@huawei.com>
To: "users@dpdk.org" <users@dpdk.org>,
	"matan@mellanox.com" <matan@mellanox.com>
Cc: Caowangbao <caowangbao@huawei.com>,
	"Yanan (Euler)" <yanan@huawei.com>,
	liaichun <liaichun@huawei.com>
Subject: net_mlx5: port 2 cannot get MAC address, is mlx5_en loaded? (errno: Function not implemented)
Date: Tue, 29 Aug 2023 09:58:35 +0000	[thread overview]
Message-ID: <72cdc44a3e254c8a95b6d597065a120c@huawei.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1017 bytes --]

Hi matan:
I have enabled mlx5 hotplug based on the failsafe pmd:
"--vdev", "net_failsafe0,mac=04:e8:92:7d:dd:e4,dev(08:00.0)", "-b", "08:00.0"
08:00.0 is mlx5 NIC.
The app started successfully.

However, I had some problems verifying the hotplug function. Here are the steps:
echo 1 > /sys/bus/pci/devices/0000:08:00.0/remove
echo 1 > /sys/bus/pci/rescan

The app had the following error:
EAL: PCI device 0000:08:00.0 on NUMA socket 0
EAL:   probe driver: 15b3:1017 net_mlx5
net_mlx5: port 2 cannot get MAC address, is mlx5_en loaded? (errno: Function not implemented)
net_mlx5: probe of PCI device 0000:08:00.0 aborted after encountering an error: No such device
EAL: Driver cannot attach the device (08:00.0)
EAL: Failed to attach device on primary process
net_failsafe: sub_device 0 probe failed (No such device)


Look at the code it is through the ioctl function to obtain the MAC address.
I wonder if there are other configurations that have not been done, causing this problem

Thanks!

[-- Attachment #2: Type: text/html, Size: 4465 bytes --]

             reply	other threads:[~2023-08-29  9:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-29  9:58 jiangheng (G) [this message]
2023-08-31 11:16 jiangheng (G)
2023-09-02  9:01 jiangheng (G)

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=72cdc44a3e254c8a95b6d597065a120c@huawei.com \
    --to=jiangheng14@huawei.com \
    --cc=caowangbao@huawei.com \
    --cc=liaichun@huawei.com \
    --cc=matan@mellanox.com \
    --cc=users@dpdk.org \
    --cc=yanan@huawei.com \
    /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).