DPDK usage discussions
 help / color / mirror / Atom feed
* [dpdk-users] segmention fault while accessing mbuf
@ 2020-06-01 13:24 Alex Kiselev
  2020-06-01 16:17 ` Stephen Hemminger
  0 siblings, 1 reply; 12+ messages in thread
From: Alex Kiselev @ 2020-06-01 13:24 UTC (permalink / raw)
  To: users

Hello,

I've got a segmentation fault error in my data plane path.
I am pretty sure the code where the segfault happened is ok,
so my guess is that I somehow received a corrupted mbuf.
How could I troubleshoot this? Is there any way?
Is it possible that other threads of the application
corrupted that mbuf?

I would really appriciate any advice.
Thanks.

DPDK 18.11.3
NIC: 82599ES

Code:

nb_rx = rte_eth_rx_burst(port_id, queue_id, pkts_burst,
		  MAX_PKT_BURST);

...

for (i=0; i < vec_size; i++) {
	rte_prefetch0(rte_pktmbuf_mtod(m_v[i], void *));

for (i=0; i < vec_size; i++) {
	m = m_v[i];
	eth_hdr = rte_pktmbuf_mtod(m, struct ether_hdr *);
	eth_type = rte_be_to_cpu_16(eth_hdr->ether_type);               <--- 
Segmentation fault
	...

#0  rte_arch_bswap16 (_x=<error reading variable: Cannot access memory 
at address 0x4d80000000053010>)

^ permalink raw reply	[flat|nested] 12+ messages in thread

end of thread, other threads:[~2020-06-07 22:56 UTC | newest]

Thread overview: 12+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-06-01 13:24 [dpdk-users] segmention fault while accessing mbuf Alex Kiselev
2020-06-01 16:17 ` Stephen Hemminger
2020-06-02 18:46   ` Alex Kiselev
2020-06-06 12:59   ` Alex Kiselev
2020-06-07  2:41     ` Cliff Burdick
2020-06-07  9:59       ` Alex Kiselev
2020-06-07 13:16         ` Cliff Burdick
2020-06-07 13:36           ` Alex Kiselev
2020-06-07 15:21             ` Cliff Burdick
2020-06-07 17:11               ` Alex Kiselev
2020-06-07 18:11                 ` Cliff Burdick
2020-06-07 22:56                   ` Alex Kiselev

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