[dpdk-dev] [Bug 713] Failure in latest DPDK build: Cannot init any port in AWS ENA

[dpdk-dev] [Bug 713] Failure in latest DPDK build: Cannot init any port in AWS ENA

[bugzilla]

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

            Bug ID: 713
           Summary: Failure in latest DPDK build: Cannot init any port in
                    AWS ENA
           Product: DPDK
           Version: 20.11
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: ethdev
          Assignee: dev@dpdk.org
          Reporter: kaprakashr@gmail.com
  Target Milestone: ---

Created attachment 156
  --> https://bugs.dpdk.org/attachment.cgi?id=156&action=edit
Snapshot of issue

Issue Description
-----------------
With AWS running Ubuntu 20.04 agains latest DPDK version. We are not able to
init the ports
(More info: testpmd is able to detect and load all ports, but
dpdk_skeleton(basic packet forwarding) always fails to init ports)

Steps to reproduce
------------------
Below is the issue we are facing, while trying to start the basic dpdk packet
forwarding,
(1) The core allocation was successful
(2) The interface binding was successful
(3) Port init is failing

__SnapShot__of__issue__
=======================

ubuntu@ip-172-31-23-251:~/dpdk-21.02/build/examples$ sudo ./dpdk-skeleton -l1
-n4
EAL: Detected 4 lcore(s)
EAL: Detected 1 NUMA nodes
EAL: Detected static linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'PA'
EAL: No available 1048576 kB hugepages reported
EAL: Probing VFIO support...
EAL:   Invalid NUMA socket, default to 0
EAL:   Invalid NUMA socket, default to 0
EAL: Probe PCI driver: net_ena (1d0f:ec20) device: 0000:00:06.0 (socket 0)
EAL:   Invalid NUMA socket, default to 0
EAL: Probe PCI driver: net_ena (1d0f:ec20) device: 0000:00:07.0 (socket 0)
EAL: No legacy callbacks, legacy socket not created
Port 0 MAC: 06 66 dc 11 e8 30
EAL: Error - exiting with code: 1
  Cause: Cannot init port 0

ubuntu@ip-172-31-23-251:~/dpdk-21.02/build/examples$ cd ../..

Network devices using DPDK-compatible driver
============================================
0000:00:06.0 'Elastic Network Adapter (ENA) ec20' drv=igb_uio unused=ena
0000:00:07.0 'Elastic Network Adapter (ENA) ec20' drv=igb_uio unused=ena

Network devices using kernel driver
===================================
0000:00:05.0 'Elastic Network Adapter (ENA) ec20' if=ens5 drv=ena
unused=igb_uio *Active*

-- 
You are receiving this mail because:
You are the assignee for the bug.

[dpdk-dev] [Bug 713] Cannot init ENA port in skeleton example

[bugzilla]

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

kalyan (kaprakashr@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |WORKSFORME
             Status|UNCONFIRMED                 |RESOLVED

--- Comment #2 from kalyan (kaprakashr@gmail.com) ---
Hi David,

Thanks much! After I masked that check it works(snapshot below),

Besides, could you throw some light on the future implications of masking this
check in AWS ENA? (And also the reason behind introducing this check) 

__Snap shot__
oot@ip-172-31-23-251:/home/ubuntu/dpdk-stable-20.11.1/build/examples#
./dpdk-skeleton -l 1 -n 2
EAL: Detected 4 lcore(s)
EAL: Detected 1 NUMA nodes
EAL: Detected static linkage of DPDK
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:   Invalid NUMA socket, default to 0
EAL:   Invalid NUMA socket, default to 0
EAL: Probe PCI driver: net_ena (1d0f:ec20) device: 0000:00:06.0 (socket 0)
EAL:   Invalid NUMA socket, default to 0
EAL: Probe PCI driver: net_ena (1d0f:ec20) device: 0000:00:07.0 (socket 0)
EAL: No legacy callbacks, legacy socket not created
Port 0 MAC: 06 66 dc 11 e8 30
Port 1 MAC: 06 b7 8f e2 7e 6e

Core 1 forwarding packets.

Thanks,
Kalyan

-- 
You are receiving this mail because:
You are the assignee for the bug.