Skip to contentSkip to conversation

mlx5: cannot probe ConnectX-6 Dx if socket-limit is too small on NUMA socket 0

Bug 887 [email protected] 1 participant 2 messages Nov 17, 2021 – Oct 28, 2025

lore
Share & tools
lore
#0 lore raw

https://bugs.dpdk.org/show_bug.cgi?id=887

Bug ID: 887
Summary: mlx5: cannot probe ConnectX-6 Dx if socket-limit is
too small on NUMA socket 0
Product: DPDK
Version: 21.08
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---

Our client has a ConnectX-6 Dx Ethernet adapter, installed on a PCI slot belonging to NUMA socket 1.
When DPDK is initialized with flags "--socket-limit 1,2048 -a c1:00.0", PCI probe fails with this message:

EAL: No available 2048 kB hugepages reported
EAL: No free 2048 kB hugepages reported on node 0
EAL: No free 2048 kB hugepages reported on node 1
EAL: No available 2048 kB hugepages reported
mlx5_net: probe of PCI device 0000:c1:00.0 aborted after encountering an error:
Cannot allocate memory
mlx5_common: Failed to load driver mlx5_eth
EAL: Requested device 0000:c1:00.0 cannot be used
EAL: Bus (pci) probe failed.

I suspect somewhere in the driver is trying to allocate certain objects on NUMA socket 0, but I don't know which.
It should be changed to allow allocation on any NUMA socket.

Signature · 2 lines
You are receiving this mail because:
You are the assignee for the bug.
#1 lore raw

http://bugs.dpdk.org/show_bug.cgi?id=887

[email protected] ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------

                 CC|                            |[email protected]
         Resolution|---                         |WONTFIX
             Status|UNCONFIRMED                 |RESOLVED

--- Comment #3 from [email protected] ([email protected]) --- old issue, no response, closing.

Signature · 2 lines
You are receiving this mail because:
You are the assignee for the bug.