DPDK patches and discussions
 help / color / mirror / Atom feed
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 V2] doc: add known PHY link up issue for i40e
Date: Thu,  8 Nov 2018 15:17:35 +0800	[thread overview]
Message-ID: <1541661455-24523-1-git-send-email-jia.guo@intel.com> (raw)
In-Reply-To: <1539256137-63231-1-git-send-email-jia.guo@intel.com>

If bind i40e NICs with PMD and run application, after application quits,
some kernel driver may not be able to set PHY to link up again by
``ifconfig`` after NICs be rebound to kernel driver.

Signed-off-by: Jeff Guo <jia.guo@intel.com>
---
v2->v1:
refine some typo and word.
---
 doc/guides/rel_notes/known_issues.rst | 27 +++++++++++++++++++++++++++
 1 file changed, 27 insertions(+)

diff --git a/doc/guides/rel_notes/known_issues.rst b/doc/guides/rel_notes/known_issues.rst
index 95e4ce6..f4e3519 100644
--- a/doc/guides/rel_notes/known_issues.rst
+++ b/doc/guides/rel_notes/known_issues.rst
@@ -759,3 +759,30 @@ Netvsc driver and application restart
 
 **Driver/Module**:
    ``uio_hv_generic`` module.
+
+
+PHY link up failed when rebind i40e NICs to kernel driver
+---------------------------------------------------------
+
+**Description**:
+   If bind i40e NICs with PMD and run application, after application quits, some
+   kernel driver may not be able to set PHY to link up again by ``ifconfig``
+   after NICs be rebound to kernel driver.
+
+**Implication**:
+   Before application quits, it will invokes the function ``i40e_dev_stop``,
+   which will set PHY to link down. This is the situation that some kernel
+   driver may not be able to handle link status correctly after it retakes
+   control of the device. It is a known PHY link configure synchronous issue in
+   i40e kernel driver. The fix has been addressed in 2.7.4 rc version. So if
+   the i40e kernel driver is < 2.7.4 and before the fix be backported into the
+   previous versions, it will encounter this issue.
+
+**Resolution/Workaround**:
+   If it does not help by remove and reinsert i40e kernel driver, please reboot system.
+
+**Affected Environment/Platform**:
+   All.
+
+**Driver/Module**:
+   Poll Mode Driver (PMD).
-- 
2.7.4

  parent reply	other threads:[~2018-11-08  7:13 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 ` Jeff Guo [this message]
2018-11-08 17:48   ` [dpdk-dev] [PATCH V2] " Zhang, Qi Z
2018-11-09  2:21     ` Jeff Guo
2018-11-09 16:31       ` Zhang, Qi Z
2018-11-16  2:38 ` [dpdk-dev] [PATCH V3] " Jeff Guo
2018-11-16  9:41   ` 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=1541661455-24523-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).