From: Bruce Richardson <bruce.richardson@intel.com>
To: Thao Hull <thaohull@gmail.com>
Cc: "Mikulicz,
Szymon (Nokia - PL/Krakow)" <szymon.mikulicz@nokia.com>,
dev@dpdk.org, users@dpdk.org
Subject: Re: [dpdk-users] [dpdk-dev] EAL: failed to parse device "XX:XX.X" on CentOS 7
Date: Tue, 17 Aug 2021 15:47:09 +0100 [thread overview]
Message-ID: <YRvL7UW93iIf4ExB@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <CANYnVsQdPq+VTi-jEKAQo0a7-nLukDCJSQQ_QxNmWyUjFFKNFw@mail.gmail.com>
On Mon, Aug 16, 2021 at 07:13:54AM -0600, Thao Hull wrote:
> Thank you! Will try that when I get back from vacation. Thao
>
> On Mon, Aug 16, 2021, 4:48 AM Mikulicz, Szymon (Nokia - PL/Krakow) <
> szymon.mikulicz@nokia.com> wrote:
>
> > Hi Thao,
> >
> > the original issue was resolved by updating pkg-config. I compiled a new
> > version of it on our centos 7 setup. We are currently using pkg-config 0.29.2
> > and it works.
> >
> > BR,
> > SM
> >
The likely cause of the inability to parse the address is the PCI driver
not being linked into the binary for a static build. This could indeed be
caused by incorrect output from pkg-config, and the default pkg-config on
centos 7 is known to have such an issue. Updating pkg-config, or use
pkgconf instead, is recommended to fix this, as suggested above.
/Bruce
> > On 8/13/21 12:32 AM, Thao Hull wrote:
> >
> > Hi.
> >
> > This looks similar to the problem I am having.
> > https://lore.kernel.org/dpdk-dev/bug-689-3@http.bugs.dpdk.org%2F/T/
> >
> > I can't figure out how this issue was resolved on Centos7 per the thread.
> > Can someone please explain how to get past this failure error? Just like
> > this user, testpmd works fine for me. My device is in slot b3:00.0. I am
> > using arkville on a bittware FPGA card. My error is slightly different as
> > shown below:
> >
> > EAL: Detected 24 lcore(s)
> > EAL: Detected 2 NUMA nodes
> > EAL: Detected static linkage of DPDK
> > EAL: failed to parse device "b3:00.0"
> > EAL: Unable to parse device 'b3:00.0, Pkt_dir=0xF0000, Pkt_gen=./pg.conf'
> >
> > EAL: Error - exiting with EAL initialization
> >
> > I'm using dpdk version 21.08.0
> >
> > Any thoughts on how to debug, if not fix this? I am new to dpdk.
> >
> > Thank you!
> > Thao
> >
> >
prev parent reply other threads:[~2021-08-17 14:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-12 22:32 [dpdk-users] " Thao Hull
2021-08-16 10:48 ` Mikulicz, Szymon (Nokia - PL/Krakow)
2021-08-16 13:13 ` Thao Hull
2021-08-17 14:47 ` Bruce Richardson [this message]
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=YRvL7UW93iIf4ExB@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=szymon.mikulicz@nokia.com \
--cc=thaohull@gmail.com \
--cc=users@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).