From: "Zhao, Ping" <ping.zhao@intel.com>
To: "users@dpdk.org" <users@dpdk.org>
Cc: "Du, Alek" <alek.du@intel.com>
Subject: Re: [dpdk-users] Mellanox CX-5 failed with DPDK 20.05, but ok with DPDK 19.11.3
Date: Mon, 13 Jul 2020 14:35:29 +0000 [thread overview]
Message-ID: <CY4PR11MB170269D85B13D419632BB3E8ED600@CY4PR11MB1702.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CY4PR11MB1702D57557E810D38CF465C8ED600@CY4PR11MB1702.namprd11.prod.outlook.com>
The issue is fixed after enable the MLX5_PMD flag. Sorry to disturb!
Regards,
Ping
From: Zhao, Ping
Sent: Monday, July 13, 2020 2:40 PM
To: 'users@dpdk.org' <users@dpdk.org>
Cc: Zhao, Ping <ping.zhao@intel.com>; Du, Alek <alek.du@intel.com>
Subject: Mellanox CX-5 failed with DPDK 20.05, but ok with DPDK 19.11.3
Dear DPDK Users,
I met a problem with DPDK 20.05 + Mellanox CX-5 NIC. Does anyone know how to fix it? Thanks a lot!
Problem:
Mellanox CX-5 card ok with DPDK 19.11.3 but failed with DPDK 20.05.
20.05 Reports no ethernet device, ok with 19.11.3
Configuration:
Mellanox CX-5 OFED package: MLNX_OFED_LINUX-5.0-2.1.8.0-rhel8.1
DPDK 20.05
DPDK stable 19.11.3
Test:
Test with DPDK testpmd app.
Logs:
Testpmd in DPDK 20.05
EAL: Detected 112 lcore(s)
EAL: Detected 2 NUMA nodes
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'PA'
EAL: No available hugepages reported in hugepages-1048576kB
EAL: Probing VFIO support...
EAL: VFIO support initialized
EAL: No legacy callbacks, legacy socket not created
testpmd: No probed ethernet devices
testpmd: create a new mbuf pool <mbuf_pool_socket_0>: n=163456, size=2176, socket=0
testpmd: preferred mempool ops selected: ring_mp_mc
Done
Devices:
./usertools/dpdk-devbind.py --status
Network devices using kernel driver
===================================
0000:18:00.0 'MT28800 Family [ConnectX-5 Ex] 1019' if=ens785f0 drv=mlx5_core unused=vfio-pci
0000:18:00.1 'MT28800 Family [ConnectX-5 Ex] 1019' if=ens785f1 drv=mlx5_core unused=vfio-pci
0000:3d:00.1 'Ethernet Connection X722 for 10GBASE-T 37d2' if=eno2 drv=i40e unused=vfio-pci *Active*
# ibstat
CA 'mlx5_0'
CA type: MT4121
Number of ports: 1
Firmware version: 16.27.2008
Hardware version: 0
Node GUID: 0x0c42a103003a1298
System image GUID: 0x0c42a103003a1298
Port 1:
State: Active
Physical state: LinkUp
Rate: 100
Base lid: 0
LMC: 0
SM lid: 0
Capability mask: 0x00010000
Port GUID: 0x0e42a1fffe3a1298
Link layer: Ethernet
CA 'mlx5_1'
CA type: MT4121
Number of ports: 1
Firmware version: 16.27.2008
Hardware version: 0
Node GUID: 0x0c42a103003a1299
System image GUID: 0x0c42a103003a1298
Port 1:
State: Active
Physical state: LinkUp
Rate: 100
Base lid: 0
LMC: 0
SM lid: 0
Capability mask: 0x00010000
Port GUID: 0x0e42a1fffe3a1299
Link layer: Ethernet
Thanks,
Ping
next prev parent reply other threads:[~2020-07-17 10:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 6:39 Zhao, Ping
2020-07-13 14:35 ` Zhao, Ping [this message]
2020-07-13 17:22 ` David Christensen
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=CY4PR11MB170269D85B13D419632BB3E8ED600@CY4PR11MB1702.namprd11.prod.outlook.com \
--to=ping.zhao@intel.com \
--cc=alek.du@intel.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).