From: Filip Janiszewski <contact@filipjaniszewski.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-users] Not supported card on board, is segfault expected?
Date: Wed, 27 Feb 2019 14:01:13 +0100 [thread overview]
Message-ID: <ba3f3b90-d864-fdec-5b83-dcebe7b76cb0@filipjaniszewski.com> (raw)
Hi,
I'm running DPDK 18.05 with a nic card that is not present in the list
of supported devices: MCX512F-ACAT (ConnectX®-5 EN network interface
card, 25GbE dual-port SFP28, PCIe3.0 x16, tall bracket), during
rte_eal_init there's a segfault:
.
#0 0x00007ffff77a98ce in mlx5_alloc_td () from /lib64/libmlx5.so.1
#1 0x0000000000784008 in mlx5_pci_probe (pci_drv=<optimized out>,
pci_dev=0xfc04d0)
at dpdk-18.05/drivers/net/mlx5/mlx5.c:1021
#2 0x0000000000599a7f in pci_probe_all_drivers.part.1 ()
#3 0x0000000000599bbe in rte_pci_probe ()
#4 0x000000000057ad7c in rte_bus_probe ()
#5 0x000000000056a73e in rte_eal_init ()
#6 0x000000000047312a in main (argc=4, argv=0x7fffffffe5a8) at
/home/fjaniszewski/SDC/P2D/repo/p2d-megamole/mm_main.c:163
.
Shall I always expect segmentation faults like this when DPDK is
executed on a system with unsupported nic card? Shouldn't those cards
just be ignored? Did any of you encountered a similar segfault?
Thanks
--
BR, Filip
+48 666 369 823
reply other threads:[~2019-02-27 13:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=ba3f3b90-d864-fdec-5b83-dcebe7b76cb0@filipjaniszewski.com \
--to=contact@filipjaniszewski.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).