From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/other Bug 1447] segfault while running dpdk app test ( event_crypto_adapter_autotest )
Date: Wed, 22 May 2024 08:06:10 +0000 [thread overview]
Message-ID: <bug-1447-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 3605 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1447
Bug ID: 1447
Summary: segfault while running dpdk app test (
event_crypto_adapter_autotest )
Product: DPDK
Version: 22.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: other
Assignee: dev@dpdk.org
Reporter: partha.sarkar@intel.com
Target Milestone: ---
Hi,
While running "event_crypto_adapter_autotest" the crash is observed when below
sriov configuration are done on the board. But if sriov configuration are not
done then crash is not observed for the crypto autotest.
modprobe vfio-pci
#Get pci-bdf for qat device
CPMDEV=$(lspci | grep "578a" | cut -f1 -d
echo $CPMDEV
echo "/sys/bus/pci/devices/0000:${CPMDEV}:00.0/sriov_numvfs"
echo "Before update, sriov_numvfs = \c"
cat /sys/bus/pci/devices/0000:${CPMDEV}:00.0/sriov_numvfs;
echo 10 > /sys/bus/pci/devices/0000:${CPMDEV}:00.0/sriov_numvfs
echo "After update, sriov_numvfs = \c"
cat /sys/bus/pci/devices/0000:${CPMDEV}:00.0/sriov_numvfs;
lsmod
if [ ! -z ${RDK_INSTALL+x} ]; then
cd $RDK_INSTALL/dpdk/usertools
else
cd $RTE_SDK/usertools
fi
${RTE_SDK}/usertools/dpdk-devbind.py -b vfio-pci ${CPMDEV}:00.1 ${CPMDEV}:00.2
${CPMDEV}:00.3 ${CPMDEV}:00.4 ${CPMDEV}:00.5 ${CPMDEV}:00.6 ${CPMDEV}:00.7
${CPMDEV}:01.0 ${CPMDEV}:01.1 ${CPMDEV}:01.2
The full gdb backtrace:
(gdb) n
Single stepping until exit from function unit_test_suite_runner,
which has no line number information.
+ TestCase [ 3] : test_crypto_adapter_runtime_params succeeded
Thread 4 "rte-worker-1" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffff0765640 (LWP 2037)]
0x00007ffff6cad4c1 in eca_service_func ()
from
/workspace/sw/swreleases/grr_builds/post-merge-install/main/rdk_i3c_56_2024_03_05/rdk_f623443/dpdk/x86_64-native-linuxapp-gcc/lib/librte_eventdev.so.23
(gdb) bt -full
#0 0x00007ffff6cad4c1 in eca_service_func ()
from
/workspace/sw/swreleases/grr_builds/post-merge-install/main/rdk_i3c_56_2024_03_05/rdk_f623443/dpdk/x86_64-native-linuxapp-gcc/lib/librte_eventdev.so.23
No symbol table info available.
#1 0x00007ffff7ee6bb3 in service_runner_func ()
from
/workspace/sw/swreleases/grr_builds/post-merge-install/main/rdk_i3c_56_2024_03_05/rdk_f623443/dpdk/x86_64-native-linuxapp-gcc/lib/librte_eal.so.23
No symbol table info available.
#2 0x00007ffff7ecb780 in eal_thread_loop.cold ()
from
/workspace/sw/swreleases/grr_builds/post-merge-install/main/rdk_i3c_56_2024_03_05/rdk_f623443/dpdk/x86_64-native-linuxapp-gcc/lib/librte_eal.so.23
No symbol table info available.
#3 0x00007ffff38583c9 in start_thread (arg=0x7ffff0765640) at
pthread_create.c:481
ret = <optimized out>
pd = 0x7ffff0765640
unwind_buf = {cancel_jmp_buf = {{jmp_buf =
{140737227675200, -2731498837051200553, 140737488338894,
140737488338895, 0, 140737227675200, 2731473494489148375, 2731471986132364247}
, mask_was_saved = 0}},
priv = {pad =
{0x0, 0x0, 0x0, 0x0}
, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}}
not_first_call = 0
#4 0x00000030002fc863 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
No locals.
Execution Steps:
$RDK_INSTALL/dpdk/x86_64-native-linuxapp-gcc/bin/dpdk-test --log-level 6
RTE>>event_crypto_adapter_autotest
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 5557 bytes --]
reply other threads:[~2024-05-22 8:06 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-1447-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).