[dpdk-dev] [Bug 689] RTE bus list not populated causing EAL: failed to parse device "XX:XX.X" on CentOS 7

[dpdk-dev] [Bug 689] RTE bus list not populated causing EAL: failed to parse device "XX:XX.X" on CentOS 7

[bugzilla]

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

            Bug ID: 689
           Summary: RTE bus list not populated causing EAL: failed to
                    parse device "XX:XX.X" on CentOS 7
           Product: DPDK
           Version: 20.11
          Hardware: x86
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: core
          Assignee: dev@dpdk.org
          Reporter: szymon.mikulicz@nokia.com
  Target Milestone: ---

On our CI setup we build DPDK on CentOS 7
There are no problems with compilation, we are able to compile it and our
application. However when starting EAL: (rte_eal_init())


"./app -l 2-5 --file-prefix 04:00.0 -a 04:00.0
EAL: Detected 24 lcore(s)
EAL: Detected 2 NUMA nodes
EAL: Detected static linkage of DPDK
EAL: failed to parse device "04:00.0"
EAL: Unable to parse device '04:00.0'
Cant init EAL"


I've traced it back to PCI bus list being empty, none of the buses are
registered for some reason. I am not sure how the buses are supposed to be
registered with all the macro RTE_INIT_PRIO magic happening so I stopped there.

The output from meson doesn't seem to be any different on the CentOS machine to
more modern systems where everything works as expected

Do you have any idea what might be happening and how to continue debugging?

I've found that testpmd works ./dpdk-testpmd -l 2-5 --file-prefix 04:00.0 -a
04:00.0

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

[dpdk-dev] [Bug 689] RTE bus list not populated causing EAL: failed to parse device "XX:XX.X" on CentOS 7 with static linkage

[bugzilla]

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

Thomas Monjalon (thomas@monjalon.net) changed:

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

--- Comment #5 from Thomas Monjalon (thomas@monjalon.net) ---
I've closed it, thanks.

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