From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 4] Segfault while running txonly mode with 4 16B SGEs packets
Date: Tue, 07 Nov 2017 08:42:11 +0000 [thread overview]
Message-ID: <bug-4-3@http.dpdk.org/tracker/> (raw)
http://dpdk.org/tracker/show_bug.cgi?id=4
Bug ID: 4
Summary: Segfault while running txonly mode with 4 16B SGEs
packets
Product: DPDK
Version: 17.08
Hardware: x86
OS: Linux
Status: CONFIRMED
Severity: major
Priority: Normal
Component: testpmd
Assignee: dev@dpdk.org
Reporter: salehals@mellanox.com
Target Milestone: ---
Testpmd crashes when any segment size is <= 18 bytes
testpmd command:
./x86_64-native-linuxapp-gcc/build/app/test-pmd/testpmd c 0x003f -n 4 --no-pci
--vdev net_ring0 --vdev net_ring1 -- --burst=64 --mbcache=512 --portmask 0x3 -i
--txd=1024 --rxd=256 --rxq=1 --txq=1 --coremask 0x001e --disable-crc-strip
--forward-mode=txonly --txpkts=16,16,16,16 -a
Trace:
#0 0x0000000000475698 in pkt_burst_transmit ()
#1 0x000000000045713a in run_pkt_fwd_on_lcore ()
#2 0x0000000000457244 in start_pkt_forward_on_core ()
#3 0x00000000004b9994 in eal_thread_loop ()
#4 0x00007ffff7093e25 in start_thread () from /lib64/libpthread.so.0
#5 0x00007ffff6dc134d in clone () from /lib64/libc.so.6
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2017-11-07 8:42 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=bug-4-3@http.dpdk.org/tracker/ \
--to=bugzilla@dpdk.org \
--cc=dev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.