From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/cryptodev Bug 1903] [dpdk-26.03]cryptodev_qat_asym_autotest: Segmentation fault
Date: Wed, 18 Mar 2026 08:39:05 +0000 [thread overview]
Message-ID: <bug-1903-3@http.bugs.dpdk.org/> (raw)
http://bugs.dpdk.org/show_bug.cgi?id=1903
Bug ID: 1903
Summary: [dpdk-26.03]cryptodev_qat_asym_autotest: Segmentation
fault
Product: DPDK
Version: 26.03
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: cryptodev
Assignee: dev@dpdk.org
Reporter: yux.jiang@intel.com
Target Milestone: ---
[DPDK 26.03RC2]
[Reproduced steps]:
1, Build dpdk
rm -rf x86_64-native-linuxapp-gcc/
CC=gcc meson -Dlibdir=lib --default-library=static x86_64-native-linuxapp-gcc/
ninja -C x86_64-native-linuxapp-gcc/
2, Bind qat vf device
./usertools/dpdk-devbind.py -b vfio-pci 0000:81:00.1
3, Run cryptodev_qat_asym_autotest
./x86_64-native-linuxapp-gcc/app/test/dpdk-test -l 9,10 -a 0000:81:00.1
RTE>>cryptodev_qat_asym_autotest
[Logs]:
.................
+ TestCase [ 1] : ECDSA Elliptic Curve tests succeeded
+ ------------------------------------------------------- +
+ Test Suite Summary : Cryptodev ASYM ECDSA Unit Test Suite
+ ------------------------------------------------------- +
+ Tests Total : 2
+ Tests Skipped : 0
+ Tests Executed : 2
+ Tests Unsupported: 0
+ Tests Passed : 1
+ Tests Failed : 1
+ ------------------------------------------------------- +
+ ------------------------------------------------------- +
+ Test Suite : Cryptodev ASYM ECPM Unit Test Suite
+ ------------------------------------------------------- +
Segmentation fault
[Bad commit]
commit 064ef1b098d1827d62a053d5424db9a1b10b5029 (HEAD -> 2-064ef1b098)
Author: Rupesh Chiluka <rchiluka@marvell.com>
Date: Tue Dec 30 14:33:26 2025 +0530
test/crypto: remove PMD-specific asym test suites
Change PMD specific asymmetric testsuites to
capabilities based testsuites.
Signed-off-by: Rupesh Chiluka <rchiluka@marvell.com>
Acked-by: Akhil Goyal <gakhil@marvell.com>
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2026-03-18 8:39 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-1903-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.