From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 689] RTE bus list not populated causing EAL: failed to parse device "XX:XX.X" on CentOS 7
Date: Mon, 26 Apr 2021 11:25:19 +0000 [thread overview]
Message-ID: <bug-689-3@http.bugs.dpdk.org/> (raw)
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.
next reply other threads:[~2021-04-26 11:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-26 11:25 bugzilla [this message]
2021-04-27 14:19 ` [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
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=bug-689-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@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).