From: Jeff Guo <jia.guo@intel.com>
To: beilei.xing@intel.com, marko.kovacevic@intel.com,
john.mcnamara@intel.com, qi.z.zhang@intel.com
Cc: dev@dpdk.org, jia.guo@intel.com, helin.zhang@intel.com,
jingjing.wu@intel.com
Subject: [dpdk-dev] [PATCH V3] doc: add known PHY link up issue for i40e
Date: Fri, 16 Nov 2018 10:38:18 +0800 [thread overview]
Message-ID: <1542335898-148573-1-git-send-email-jia.guo@intel.com> (raw)
In-Reply-To: <1539256137-63231-1-git-send-email-jia.guo@intel.com>
Some kernel drivers are not able to handle the link status correctly
after DPDK application sets the PHY to link down.
Signed-off-by: Jeff Guo <jia.guo@intel.com>
---
doc/guides/rel_notes/known_issues.rst | 28 ++++++++++++++++++++++++++++
1 file changed, 28 insertions(+)
diff --git a/doc/guides/rel_notes/known_issues.rst b/doc/guides/rel_notes/known_issues.rst
index 95e4ce6..03fe163 100644
--- a/doc/guides/rel_notes/known_issues.rst
+++ b/doc/guides/rel_notes/known_issues.rst
@@ -759,3 +759,31 @@ Netvsc driver and application restart
**Driver/Module**:
``uio_hv_generic`` module.
+
+
+PHY link up fails when rebinding i40e NICs to kernel driver
+-----------------------------------------------------------
+
+**Description**:
+ Some kernel drivers are not able to handle the link status correctly
+ after DPDK application sets the PHY to link down.
+
+**Implication**:
+ The link status can't be set to "up" after the NIC is rebound to the
+ kernel driver. Before a DPDK application quits it will invokes the
+ function ``i40e_dev_stop()`` which will sets the PHY to link down. Some
+ kernel drivers may not be able to handle the link status correctly after
+ it retakes control of the device. This is a known PHY link configuration
+ issue in the i40e kernel driver. The fix has been addressed in the 2.7.4 rc
+ version. So if the i40e kernel driver is < 2.7.4 and doesn't have the
+ fix backported it will encounter this issue.
+
+**Resolution/Workaround**:
+ First try to remove and reinsert the i40e kernel driver. If that fails
+ reboot the system.
+
+**Affected Environment/Platform**:
+ All.
+
+**Driver/Module**:
+ Poll Mode Driver (PMD).
--
2.7.4
next prev parent reply other threads:[~2018-11-16 2:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-11 11:08 [dpdk-dev] [PATCH] " Jeff Guo
2018-10-19 18:05 ` Zhang, Qi Z
2018-11-08 7:05 ` Guo, Jia
2018-11-08 7:17 ` [dpdk-dev] [PATCH V2] " Jeff Guo
2018-11-08 17:48 ` Zhang, Qi Z
2018-11-09 2:21 ` Jeff Guo
2018-11-09 16:31 ` Zhang, Qi Z
2018-11-16 2:38 ` Jeff Guo [this message]
2018-11-16 9:41 ` [dpdk-dev] [PATCH V3] " Kovacevic, Marko
2018-11-16 19:32 ` Zhang, Qi Z
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=1542335898-148573-1-git-send-email-jia.guo@intel.com \
--to=jia.guo@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=helin.zhang@intel.com \
--cc=jingjing.wu@intel.com \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.com \
--cc=qi.z.zhang@intel.com \
/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).