From: Stephen Hemminger <stephen@networkplumber.org>
To: "Jim Vaigl" <jimv@rockbridgesoftware.com>
Cc: <users@dpdk.org>
Subject: Re: [dpdk-users] DPDK on Mellanox BlueField Ref Platform
Date: Tue, 24 Sep 2019 10:18:02 -0700 [thread overview]
Message-ID: <20190924101802.273c25d9@hermes.lan> (raw)
In-Reply-To: <004101d572f5$92d479d0$b87d6d70$@com>
On Tue, 24 Sep 2019 12:31:51 -0400
"Jim Vaigl" <jimv@rockbridgesoftware.com> wrote:
> Since no one has chimed in with any build/install/configure suggestion for
> the
> BlueField, I've spent some time debugging and thought I'd share the results.
> Building the l3fwd example application and running it as the docs suggest,
> when
> I try to send it UDP packets from another machine, it dumps core.
>
> Debugging a bit with gdb and printf, I can see that from inside
> process_packet()
> and processx4_step1() the calls to rte_pktmbuf_mtod() return Nil or
> suspicious
> pointer values (i.e. 0x80). The sample apps don't guard against NULL
> pointers
> being returned from this rte call, so that's why it's dumping core.
>
> I still think the problem is related to the driver config, but thought this
> might ring a bell for anyone who's had problems like this.
>
> The thing that still bothers me is that rather than seeing what I was
> expecting
> at init based on what the documentation shows:
> [...]
> EAL: probe driver: 15b3:1013 librte_pmd_mlx5
>
> ... when rte_eal_init() runs, I'm seeing:
> [...]
> EAL: Selected IOVA mode 'PA'
> EAL: Probing VFIO support...
>
> This still seems wrong, and I've verified that specifying the BlueField
> target ID
> string in the make is causing "CONFIG_RTE_LIBRTE_MLX5_PMD=y" to appear in
> the .config.
>
> Regards,
> --Jim Vaigl
> 614 886 5999
>
>
make sure you have latest version of rdma-core installed (v25).
The right version is not in most distros
next prev parent reply other threads:[~2019-09-24 17:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-24 16:31 Jim Vaigl
2019-09-24 17:18 ` Stephen Hemminger [this message]
2019-09-24 19:10 ` Jim Vaigl
2019-09-26 10:59 ` Asaf Penso
2019-09-26 19:46 ` Jim Vaigl
2019-10-04 17:35 ` Jim Vaigl
2019-10-04 18:28 ` Kiran Vedere
2019-10-07 16:52 ` Jim Vaigl
2019-10-07 17:00 ` Kiran Vedere
2019-10-07 17:02 ` Kiran Vedere
2019-10-07 18:10 ` Jim Vaigl
-- strict thread matches above, loose matches on Subject: below --
2019-09-20 19:34 Jim Vaigl
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=20190924101802.273c25d9@hermes.lan \
--to=stephen@networkplumber.org \
--cc=jimv@rockbridgesoftware.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).