DPDK patches and discussions
 help / color / mirror / Atom feed
From: Christos Ricudis <ricudis.christos@gmail.com>
To: Olivier MATZ <olivier.matz@6wind.com>
Cc: "Rowden, Aaron F" <aaron.f.rowden@intel.com>,
	"Zhang, Helin" <helin.zhang@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"Wu, Jingjing" <jingjing.wu@intel.com>
Subject: Re: [dpdk-dev] i40e_aq_get_phy_capabilities() fails when using SFP+ with no link
Date: Wed, 18 Jan 2017 18:15:29 +0800	[thread overview]
Message-ID: <7F35F791-2981-47EF-A0B0-3DE4D6E3CF02@gmail.com> (raw)
In-Reply-To: <20170112145554.44506d05@glumotte.dev.6wind.com>

Hi, 

> On 12 Jan 2017, at 21:55, Olivier MATZ <olivier.matz@6wind.com> wrote:
> 
> Hi,
> 
> On Wed, 11 Jan 2017 20:51:58 +0000, "Rowden, Aaron F"
> <aaron.f.rowden@intel.com> wrote:
>> Hi Helin,
>> 
>> I'm checking on this to see why it could be failing but I don’t think
>> this is one part of formal validation. Intel modules are always what
>> is recommended.
>> 
>> Aaron
>> 
>>> Hi Helin, 
>>> 
>>>> On 11 Jan 2017, at 09:08, Zhang, Helin <helin.zhang@intel.com>
>>>> wrote:
>>>> 
>>>> Hi Aaron
>>>> 
>>>> Is the SFP+ (Finisar FTLX8571D3BCL) supported and validated by
>>>> Intel? It seems there is some PHY issue in this case.  
>>> 
>>> As the original reporter of this issue, I will test with validated
>>> SFP+s and will report on my testing. 
>>> 
>>> Shouldn’t unsupported SFP+s be blacklisted in the I40E driver? 
>>> 
> 
> Just to let you know that in my case the SFP are Intel ones.
> Maybe it's a different issue.
> 
> I see there are some i40e fixes in the net-next repo, I'll give a try
> with this version.
> 
> Regards,
> Olivier

After further testing, I can confirm that this issue persists with supported Intel SFPs (Intel FTLX8571D3BCV-IT). 

As for the changeset introducing this issue - we had failure reports with previous DPDK versions, probably related to LSE handling, but these weren’t properly investigated. The change in 16.11 which calls get_phy_capability too early in initialization stage might have alleviated the issue making it easier for us to detect and confirm. 

Best regards, 
Christos Ricudis. 

  parent reply	other threads:[~2017-01-18 10:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-10 12:32 Christos Ricudis
2017-01-10 15:28 ` Olivier MATZ
2017-01-11  1:08   ` Zhang, Helin
2017-01-11  3:00     ` Christos Ricudis
     [not found]       ` <FC7A99FCE8F15942AB8D6F91FF66D8F694836A60@ORSMSX112.amr.corp.intel.com>
2017-01-12 13:55         ` Olivier MATZ
2017-01-13 13:24           ` Olivier Matz
2017-01-17 12:50             ` Wu, Jingjing
2017-01-18 10:15           ` Christos Ricudis [this message]
2017-02-05 15:30             ` Ivan Nardi
2017-02-05 20:19               ` Ivan Nardi
2017-02-06  1:04                 ` Zhang, Qi Z
2017-02-06  1:36                   ` Zhang, Helin
2017-02-07 14:56                     ` Olivier MATZ
2017-02-07 14:58                       ` Zhang, Helin
2017-02-12 16:13                       ` Ivan Nardi
2017-02-06 21:06                   ` Ivan Nardi

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=7F35F791-2981-47EF-A0B0-3DE4D6E3CF02@gmail.com \
    --to=ricudis.christos@gmail.com \
    --cc=aaron.f.rowden@intel.com \
    --cc=dev@dpdk.org \
    --cc=helin.zhang@intel.com \
    --cc=jingjing.wu@intel.com \
    --cc=olivier.matz@6wind.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).