From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 249] kni cause a kernel crash on avx512 supported platform with gcc 8.3.1
Date: Tue, 09 Apr 2019 17:03:48 +0000 [thread overview]
Message-ID: <bug-249-3@http.bugs.dpdk.org/> (raw)
Message-ID: <20190409170348.ITmC_Y3-6UoiacbRB8v8bpq9-KDaPChHbLmHjNWn3Z4@z> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=249
Bug ID: 249
Summary: kni cause a kernel crash on avx512 supported platform
with gcc 8.3.1
Product: DPDK
Version: 18.11
Hardware: All
OS: All
Status: CONFIRMED
Severity: normal
Priority: Normal
Component: core
Assignee: dev@dpdk.org
Reporter: ferruh.yigit@intel.com
Target Milestone: ---
The reason of the crash looks like kni library is filling the rx_q with wrong
values.
This only happens on SkyLake platform when avx512 is enabled, disabling the
avx512 via "-mno-avx512f" prevents the crash, also using clang (7.0.1) prevents
the issue although it generates avx512 code.
For reference, binutils version: 2.31.1-24.fc29
At first glance suspected instruction is 'vpgatherqq' but it needs to be
debugged more. Also will submit a defect to gcc.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2019-04-09 17:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-09 17:03 bugzilla [this message]
2019-04-09 17:03 ` 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-249-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).