DPDK usage discussions
 help / color / mirror / Atom feed
* [dpdk-users] Not supported card on board, is segfault expected?
@ 2019-02-27 13:01 Filip Janiszewski
  0 siblings, 0 replies; only message in thread
From: Filip Janiszewski @ 2019-02-27 13:01 UTC (permalink / raw)
  To: users

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

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2019-02-27 13:01 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-02-27 13:01 [dpdk-users] Not supported card on board, is segfault expected? Filip Janiszewski

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).