From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by dpdk.org (Postfix) with ESMTP id 526AA1BE0 for ; Fri, 9 Nov 2018 03:21:34 +0100 (CET) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga005.jf.intel.com ([10.7.209.41]) by fmsmga104.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 08 Nov 2018 18:21:33 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.54,481,1534834800"; d="scan'208";a="272589331" Received: from jguo15x-mobl.ccr.corp.intel.com (HELO [10.67.68.85]) ([10.67.68.85]) by orsmga005.jf.intel.com with ESMTP; 08 Nov 2018 18:21:31 -0800 To: "Zhang, Qi Z" , "Xing, Beilei" , "Kovacevic, Marko" , "Mcnamara, John" Cc: "dev@dpdk.org" , "Zhang, Helin" , "Wu, Jingjing" References: <1539256137-63231-1-git-send-email-jia.guo@intel.com> <1541661455-24523-1-git-send-email-jia.guo@intel.com> <039ED4275CED7440929022BC67E70611532E1726@SHSMSX103.ccr.corp.intel.com> From: Jeff Guo Message-ID: <07a9d79a-18d6-632f-d38e-87c00ed32f97@intel.com> Date: Fri, 9 Nov 2018 10:21:31 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.3.0 MIME-Version: 1.0 In-Reply-To: <039ED4275CED7440929022BC67E70611532E1726@SHSMSX103.ccr.corp.intel.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US Subject: Re: [dpdk-dev] [PATCH V2] doc: add known PHY link up issue for i40e X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Nov 2018 02:21:34 -0000 On 11/9/2018 1:48 AM, Zhang, Qi Z wrote: > >> -----Original Message----- >> From: Guo, Jia >> Sent: Thursday, November 8, 2018 12:18 AM >> To: Xing, Beilei ; Kovacevic, Marko >> ; Mcnamara, John >> ; Zhang, Qi Z >> Cc: dev@dpdk.org; Guo, Jia ; Zhang, Helin >> ; Wu, Jingjing >> Subject: [PATCH V2] doc: add known PHY link up issue for i40e >> >> 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 >> --- >> 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. > Should we switch the content of "description" and "implication"? I think **Description** is aim to explain the meaning of the title and give the detail of the phenomenon to acknowledge it. And **Implication** is what is the true thing behind the phenomenon and show which version will be expected to fix. I believe other part in document is the same and it will no have a big gap here. If you find the problem, please give your solid reason here. Anyway, i think it should be fine and want you could accept my explanation. >> + >> +**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