From: "jonathan.ribas@fraudbuster.mobi" <jonathan.ribas@fraudbuster.mobi>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] Issue with i40e on X710: rte_eth_dev_count returns 0, i40e_aq_get_phy_capabilities returns I40E_ERR_UNKNOWN_PHY
Date: Mon, 17 Jul 2017 10:58:41 +0200 [thread overview]
Message-ID: <440b7944-cfa5-2fe8-47a9-b162c17373c8@fraudbuster.mobi> (raw)
In-Reply-To: <20170712080726.605cde41@xeon-e3>
On 12/07/2017 17:07, Stephen Hemminger wrote:
> On Wed, 12 Jul 2017 15:50:58 +0200
> "jonathan.ribas@fraudbuster.mobi" <jonathan.ribas@fraudbuster.mobi> wrote:
>
>> Hi all,
>>
>> We got a bunch of X710 NIC and cant use them with our custom app.
>> As the topic says, rte_eth_dev_count returns 0. And after a quick
>> investigation with testpmd, we saw that i40e_aq_get_phy_capabilities
>> returns 'I40E_ERR_UNKNOWN_PHY'.
>
> With I40E always make sure and update firmware as first step.
> Last I checked, some Intel NIC's do not support 3rd party SFP modules.
Hi Stephen,
We try to update the firmware, and get some errors:
> Num Description Ver. DevId S:B Status
> === ======================================== ===== ===== ====== ===============
> 01) Intel(R) Ethernet Converged Network 5.05 1572 00:006 Access error
> Adapter X710-2
> 02) Intel(R) Ethernet Converged Network 5.05 1572 00:129 Access error
> Adapter X710-2
> 03) Intel(R) Ethernet Converged Network 5.05 1572 00:130 Access error
> Adapter X710-2
> 04) Intel(R) Ethernet Converged Network 5.05 1572 00:131 Access error
> Adapter X710-2
> 05) Intel(R) Ethernet Converged Network 5.05 1572 00:132 Access error
> Adapter X710-2
But BTW, it seems that we have the last one already flashed (5.05).
And about the used SFP, we do not use third party but the official
Intel FTLX1471D3BCV-IT.
Any other idea? :/
BR,
--
Jonathan.
prev parent reply other threads:[~2017-07-17 8:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-12 13:50 jonathan.ribas
2017-07-12 15:07 ` Stephen Hemminger
2017-07-17 8:58 ` jonathan.ribas [this message]
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=440b7944-cfa5-2fe8-47a9-b162c17373c8@fraudbuster.mobi \
--to=jonathan.ribas@fraudbuster.mobi \
--cc=stephen@networkplumber.org \
--cc=users@dpdk.org \
/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).