Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DPDK initialization failure #72

Open
marinosi opened this issue Mar 18, 2024 · 0 comments
Open

DPDK initialization failure #72

marinosi opened this issue Mar 18, 2024 · 0 comments

Comments

@marinosi
Copy link

marinosi commented Mar 18, 2024

Hi,

Using the latest commit 77788ed603671a8e50fb7a84512f24a530d0b93d DPDK fails to be initialize the appropriate driver (mlx5_net):

EAL: Setting policy MPOL_PREFERRED for socket 0
EAL: Restoring previous memory policy: 0
EAL: request: mp_malloc_sync
EAL: Heap on socket 0 was expanded by 2MB
EAL: PCI device da7a:00:02.0 on NUMA socket 0
EAL:   probe driver: 15b3:1016 mlx5_pci
EAL: Probe PCI driver: mlx5_pci (15b3:1016) device: da7a:00:02.0 (socket 0)
EAL: Mem event callback 'MLX5_MEM_EVENT_CB:(nil)' registered
mlx5_net: No available register for sampler.
EAL: Trying to obtain current memory policy.
EAL: Setting policy MPOL_PREFERRED for socket 0
EAL: Restoring previous memory policy: 0
EAL: Calling mem event callback 'MLX5_MEM_EVENT_CB:(nil)'
EAL: request: mp_malloc_sync
EAL: Heap on socket 0 was expanded by 4MB
EAL: memzone_reserve_aligned_thread_unsafe(): memzone <mlx5_pmd_shared_data> already exists
mlx5_net: Cannot allocate mlx5 shared data
mlx5_net: Unable to init PMD global data: File exists
mlx5_common: Failed to load driver mlx5_eth
EAL: Calling mem event callback 'MLX5_MEM_EVENT_CB:(nil)'

It looks like it tries to create a memzone with the same name twice and it fails on the second time. When using dpdk-testpmd from the same DPDK installation (v22.11) the driver works and initialization completes. Same arguments are being used for rte_eal_init. I am running this code on an Azure F8sv2 VM, Ubuntu 22.04 and Mellanox CX4 NIC.

Have you seen such behavior before?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant