From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 366] i40e PMD returns 0 for secondary invoking rx_burst on queue 0, when Primary dies
Date: Wed, 13 Nov 2019 15:43:26 +0000 [thread overview]
Message-ID: <bug-366-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=366
Bug ID: 366
Summary: i40e PMD returns 0 for secondary invoking rx_burst on
queue 0, when Primary dies
Product: DPDK
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: vipin.varghese@intel.com
Target Milestone: ---
DPDK version: dpdk-stable-19.08.1
Linux: 4.15.0-66-generic
i40e: driverversion=2.1.14-k firmware=6.01
DPDK build: make EXTRA_CFLAGS="-g -O0"
BT:
(gdb) bt
#0 i40e_recv_pkts_vec (rx_queue=0x17ff32c40, rx_pkts=0x7fffffffe010,
nb_pkts=<optimized out>)
at
/home/saesrv02/Downloads/dpdksrc/dpdk-stable-19.08.1/drivers/net/i40e/i40e_rxtx_vec_sse.c:470
#1 0x00005555555b6d42 in rte_eth_rx_burst (nb_pkts=32, rx_pkts=0x7fffffffe010,
queue_id=0, port_id=0)
at
/home/saesrv02/Downloads/dpdksrc/dpdk-stable-19.08.1//x86_64-native-linuxapp-gcc/include/rte_ethdev.h:4097
#2 lcore_main () at
/home/saesrv02/Downloads/dpdksrc/dpdk-stable-19.08.1/examples/skeleton/basicfwd.c:135
#3 0x00005555555b6f1d in main (argc=<optimized out>, argv=<optimized out>)
at
/home/saesrv02/Downloads/dpdksrc/dpdk-stable-19.08.1/examples/skeleton/basicfwd.c:226
Application:
Primary: initializes X710 via i40e PMD and iterates in while(1)
Secondary: probes rx_burst successfully with packets until the primary is
killed.
test app:
CMD-1: ./build/basicfwd -w 08:00.2 -l 3
CMD-2: gdb --args ./build/basicfwd -w 08:00.2 -l 4 --proc-type=secondary
traffic generator: ./build/l2fwd -w 83:00.2 --vdev net_tap0,iface=test =l 5
--file-prefix vipin -- -p 3 -T 1
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2019-11-13 15:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-13 15:43 bugzilla [this message]
2023-10-31 2:33 ` bugzilla
2023-11-20 1:46 ` bugzilla
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-366-3@http.bugs.dpdk.org/ \
--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 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).