DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jeff Guo <jia.guo@intel.com>
To: qi.z.zhang@intel.com, beilei.xing@intel.com
Cc: jingjing.wu@intel.com, dev@dpdk.org, jia.guo@intel.com,
	helin.zhang@intel.com
Subject: [dpdk-dev] [PATCH] doc: add known PHY link up issue for i40e
Date: Thu, 11 Oct 2018 19:04:03 +0800	[thread overview]
Message-ID: <1539255843-63090-1-git-send-email-jia.guo@intel.com> (raw)

When application stop i40e nics and quit itself, if i40e nics be rebinded
from pmd to kernel driver, sometimes PHY can not be link up again any more.

Signed-off-by: Jeff Guo <jia.guo@intel.com>
---
 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..3378bb7 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**:
+   When application stop i40e nics and quit itself, if i40e nics be rebinded
+   from pmd to kernel driver, sometimes PHY can not be link up again any more.
+
+**Implication**:
+   when DPDK application quit and invoke the function ``i40e_dev_stop``, I40e
+   pmd will set PHY to be link down. After these unexpected configure which not
+   come from kernel driver, it will encounter link configure failure by using
+   kernel driver config tools ``ifconfig``. 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 privous versions, use these kernel drivers will perhaps
+   have this issue.
+
+**Resolution/Workaround**:
+   If it does not help by re-insmod kernel driver, please reboot system.
+
+**Affected E0nvironment/Platform**:
+   All.
+
+**Driver/Module**:
+   Poll Mode Driver (PMD).
-- 
2.7.4

             reply	other threads:[~2018-10-11 11:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-11 11:04 Jeff Guo [this message]
2018-10-11 11:08 Jeff Guo
2018-10-19 18:05 ` Zhang, Qi Z
2018-11-08  7:05   ` Guo, Jia

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=1539255843-63090-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=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).