From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1034] [dpdk-22.07] ipsec-secgw inline test fail
Date: Tue, 14 Jun 2022 19:07:33 +0000 [thread overview]
Message-ID: <bug-1034-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=1034
Bug ID: 1034
Summary: [dpdk-22.07] ipsec-secgw inline test fail
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: examples
Assignee: dev@dpdk.org
Reporter: vladimir.medvedkin@intel.com
Target Milestone: ---
To reproduce:
NIC used with test:
Network devices using DPDK-compatible driver
============================================
0000:af:00.1 '82599ES 10-Gigabit SFI/SFP+ Network Connection 10fb' drv=vfio-pci
unused=ixgbe
running command:
./examples/ipsec-secgw/test/run_test.sh -4i
starting inline test trs_aesgcm
Test environment configuration:
[enabled] library mode
[disabled] extended sequence number
[disabled] sequence number atomic behavior
[enabled] inline crypto mode
[disabled] crypto fallback mode
[disabled] multi-segment test
...
ERROR: ./examples/ipsec-secgw/test/linux_test.sh failed for dst=192.168.31.14,
sz=1
inline test IPv4 trs_aesgcm finished with status 1
ERROR inline test trs_aesgcm FAILED
First bad commit:
commit d24471e5786b71e0c1cb3c2362397a1a27201a74 (HEAD, refs/bisect/bad)
Author: Nithin Dabilpuram <ndabilpuram@marvell.com>
Date: Sat Apr 30 02:14:11 2022 +0530
examples/ipsec-secgw: disable Tx checksum for inline
Enable Tx IPv4 checksum offload only when Tx inline crypto, lookaside
crypto/protocol or cpu crypto is needed.
For Tx Inline protocol offload, checksum computation
is implicitly taken care by HW.
Signed-off-by: Nithin Dabilpuram <ndabilpuram@marvell.com>
Acked-by: Akhil Goyal <gakhil@marvell.com>
Acked-by: Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2022-06-14 19:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-14 19:07 bugzilla [this message]
2022-07-04 11:21 ` 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-1034-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).