From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 306] Intel X722 chipset DPDK driver issue with WindRiver Titianium R18.03 platform - CentOS 7.4
Date: Fri, 05 Jul 2019 14:52:25 +0000 [thread overview]
Message-ID: <bug-306-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=306
Bug ID: 306
Summary: Intel X722 chipset DPDK driver issue with WindRiver
Titianium R18.03 platform - CentOS 7.4
Product: DPDK
Version: 17.11
Hardware: x86
OS: Linux
Status: CONFIRMED
Severity: critical
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: lionel.fiat@atos.net
Target Milestone: ---
Created attachment 46
--> https://bugs.dpdk.org/attachment.cgi?id=46&action=edit
Different CLI and logs on the server = analyzis
Intel X722 chipset DPDK driver issue with WindRiver Titianium R18.03 platform
(CentOS 7.4):
Issue: 10G Intel X722 Interface lost when uses with DPDK with BullSequana Edge
1) PROBLEM : We have an issue with a partner product (WindRiver Titianium) that
is using DPDK and we have troubles on some network Titanium features when we
install it on BullSequana Edge.
2) We are using DPDK 17.11 / kernel 2.1.26: i40e PMD (librte_pmd_i40e) provides
poll mode driver failure
3) See details in attached files
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2019-07-05 14:52 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-306-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.