From: "Zhang, Helin" <helin.zhang@intel.com>
To: "Zhang, Qi Z" <qi.z.zhang@intel.com>,
Ivan Nardi <nardi.ivan@gmail.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Olivier MATZ <olivier.matz@6wind.com>,
Christos Ricudis <ricudis.christos@gmail.com>,
"Rowden, Aaron F" <aaron.f.rowden@intel.com>,
"Wu, Jingjing" <jingjing.wu@intel.com>
Subject: Re: [dpdk-dev] i40e_aq_get_phy_capabilities() fails when using SFP+ with no link
Date: Mon, 6 Feb 2017 01:36:45 +0000 [thread overview]
Message-ID: <F35DEAC7BCE34641BA9FAC6BCA4A12E71A9B598A@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <039ED4275CED7440929022BC67E706115305832F@SHSMSX103.ccr.corp.intel.com>
Hi guys
There may have firmware dependencies, new DPDK version + old firmware version may not work. Please refer to below link to see what type of firmware has been validated with 16.11 DPDK.
http://dpdk.org/doc/guides/rel_notes/release_16_11.html#tested-nics
Then first, you need to upgrade your firmware. Then let us know if the issue is still there. Thanks!
Regards,
Helin
-----Original Message-----
From: Zhang, Qi Z
Sent: Monday, February 6, 2017 9:05 AM
To: Ivan Nardi <nardi.ivan@gmail.com>; dev@dpdk.org
Cc: Olivier MATZ <olivier.matz@6wind.com>; Christos Ricudis <ricudis.christos@gmail.com>; Rowden, Aaron F <aaron.f.rowden@intel.com>; Zhang, Helin <helin.zhang@intel.com>; Wu, Jingjing <jingjing.wu@intel.com>
Subject: RE: [dpdk-dev] i40e_aq_get_phy_capabilities() fails when using SFP+ with no link
Hi Ivan:
I'm looking at this issue, but I can't repeat it on my environment both with X710x4 and XL710x1
Not sure if you could try below things to help narrow down this issue.
1) move i40e_dev_sync_phy_type call after i40e_set_fc call, to see if the problem still exist, since without i40e_dev_sync_phy_type, i40e_set_fc is the first place i40e_aq_get_phy_capabilities get called and we didn't see this issue before 16.11.
2) if above change works, at least we have a work around, if above still fail, please modify the parameter of i40e_aq_get_phy_capabilities in i40e_dev_sync_phy_type as below and check result.
- status = i40e_aq_get_phy_capabilities(hw, false, true, &phy_ab,
- NULL);
+ status = i40e_aq_get_phy_capabilities(hw, false, false, &phy_ab,
+ NULL);
Thank you!
Regards
Qi
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Ivan Nardi
> Sent: Monday, February 6, 2017 4:19 AM
> To: dev@dpdk.org
> Cc: Olivier MATZ <olivier.matz@6wind.com>; Christos Ricudis
> <ricudis.christos@gmail.com>; Rowden, Aaron F
> <aaron.f.rowden@intel.com>; Zhang, Helin <helin.zhang@intel.com>; Wu,
> Jingjing <jingjing.wu@intel.com>
> Subject: Re: [dpdk-dev] i40e_aq_get_phy_capabilities() fails when
> using SFP+ with no link
>
> HI
> same issue with 17.02-rc2
> It seems to me the problem I am facing is similar to the ones reported
> in these mails; if not, I apologize to have used this thread
>
> Ivan
>
> On 5 February 2017 at 16:30, Ivan Nardi <nardi.ivan@gmail.com> wrote:
>
> > Hi guys
> > any updates on this issue?
> > We are facing a very similar problem.
> > We have a server with 4 nics X710 4*10Gbit and the dpdk randomly
> > failed to start with the error:
> >
> > PMD: eth_i40e_dev_init(): FW 4.40 API 1.4 NVM 04.05.03 eetrack
> > 80001cd8
> > PMD: eth_i40e_dev_init(): Failed to sync phy type: -95
> >
> > It happens randomly (sometimes it works properly, sometimes not),
> > the "failed" port index is random too and it happens whether the
> > fibers have been connected or not.
> >
> > We are using dpdk 16.11.
> >
> > Any help would be appreciated
> > Thanks in advance
> >
> > Ivan
> >
> > On 18 January 2017 at 11:15, Christos Ricudis
> > <ricudis.christos@gmail.com>
> > wrote:
> >
> >> 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.
> >>
> >>
> >
next prev parent reply other threads:[~2017-02-06 1:36 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
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 [this message]
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=F35DEAC7BCE34641BA9FAC6BCA4A12E71A9B598A@SHSMSX103.ccr.corp.intel.com \
--to=helin.zhang@intel.com \
--cc=aaron.f.rowden@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=nardi.ivan@gmail.com \
--cc=olivier.matz@6wind.com \
--cc=qi.z.zhang@intel.com \
--cc=ricudis.christos@gmail.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).