From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 404] i40e: "i40e_res_pool_free(): Failed to find entry" error when rte_flow are flushed
Date: Fri, 21 Feb 2020 16:14:06 +0000 [thread overview]
Message-ID: <bug-404-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=404
Bug ID: 404
Summary: i40e: "i40e_res_pool_free(): Failed to find entry"
error when rte_flow are flushed
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: maxime.leroy@6wind.com
Target Milestone: ---
With dpdk master (commit id d0e160a00233), I got the following error when I try
to flush a rte_flow a second time (i.e. create a flow, delete, recreate and
then delete).
./build/app/testpmd --legacy-mem -c 1f -n 4 -w 0000:85:00.1 -- -i --rxq=1
--txq=1 --total-num-mbufs=10000
EAL: Detected 40 lcore(s)
EAL: Detected 2 NUMA nodes
EAL: Static memory layout is selected, amount of reserved memory can be
adjusted with -m or --socket-mem
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'VA'
EAL: No available hugepages reported in hugepages-1048576kB
EAL: Probing VFIO support...
EAL: VFIO support initialized
EAL: PCI device 0000:85:00.1 on NUMA socket 1
EAL: probe driver: 8086:1583 net_i40e
EAL: using IOMMU type 1 (Type 1)
Interactive-mode selected
...
testpmd> flow create 0 ingress pattern eth / ipv4 / tcp dst is 179 / end
actions queue index 0 / end
Flow rule #0 created
testpmd> flow flush 0
testpmd> flow create 0 ingress pattern eth / ipv4 / tcp dst is 179 / end
actions queue index 0 / end
Flow rule #0 created
testpmd> flow flush 0
i40e_res_pool_free(): Failed to find entry
testpmd>
The error happens in i40e_res_pool_free:
4951│ /* Not find, return */
4952│ if (valid_entry == NULL) {
4953├> PMD_DRV_LOG(ERR, "Failed to find entry");
4954│ return -EINVAL;
4955│ }
4956│
(gdb) bt
#0 i40e_res_pool_free (pool=0x112c3fe510, base=0) at
/root/dpdk/drivers/net/i40e/i40e_ethdev.c:4953
#1 0x000055718b6fa489 in i40e_vsi_release (vsi=0x20015ab80) at
/root/dpdk/drivers/net/i40e/i40e_ethdev.c:5426
#2 0x000055718b8c6c8c in i40e_fdir_teardown (pf=0x112c3fe4f8) at
/root/dpdk/drivers/net/i40e/i40e_fdir.c:286
#3 0x000055718b97dc8e in i40e_flow_flush_fdir_filter (pf=0x112c3fe4f8) at
/root/dpdk/drivers/net/i40e/i40e_flow.c:5186
#4 0x000055718b97da24 in i40e_flow_flush (dev=0x55718e4e9300
<rte_eth_devices>, error=0x7fffd7360320) at
/root/dpdk/drivers/net/i40e/i40e_flow.c:5114
#5 0x000055718acc91dc in rte_flow_flush (port_id=0, error=0x7fffd7360320) at
/root/dpdk/lib/librte_ethdev/rte_flow.c:412
..
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2020-02-21 16:14 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-404-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 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.