From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 462] command kvargs_autotest excute failed on freebsd with gcc and clang
Date: Sun, 26 Apr 2020 06:41:32 +0000 [thread overview]
Message-ID: <bug-462-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=462
Bug ID: 462
Summary: command kvargs_autotest excute failed on freebsd with
gcc and clang
Product: DPDK
Version: 20.05
Hardware: x86
OS: FreeBSD
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: testpmd
Assignee: dev@dpdk.org
Reporter: zhiminx.huang@intel.com
Target Milestone: ---
---------------------------------Description-----------------------------------
when i start up testpmd and excuted 'kvargs_autotest' with gcc and clang on
freebsd,the dpdk output 'Segmentation fault' and testpmd drop out,the expected
output is 'test ok'.
---------------------------------reproduce steps-------------------------------
1.compile dpdk by clang
export RTE_SDK=`pwd`
export RTE_TARGET=x86_64-native-bsdapp-clang
gmake -j install T=x86_64-native-bsdapp-clang
2.load driver and bind nic driver in freebsd
kldload ./x86_64-native-bsdapp-clang/kmod/contigmem.ko
kldload ./x86_64-native-bsdapp-clang/kmod/nic_uio.ko
Pciconf -l
kenv hw.nic_uio.bdfs="134:0:0,134:0:1"
3.start testpmd
./x86_64-native-bsdapp-clang/app/test -l 1,2,4,6 -n 4
4.execute command
kvargs_autotest
5.output
RTE>>kvargs_autotest
== test valid case ==
== test invalid case ==
Segmentation fault
6.Expected Result
RTE>>kvargs_autotest
== test valid case ==
== test invalid case ==
Test OK
comments：gcc have the same issue as clang.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2020-04-26 6:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-26 6:41 bugzilla [this message]
2020-05-06 9:52 ` 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-462-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).