From: amit shukla <amitshukla19@gmail.com>
To: dev@dpdk.org
Cc: beilei.xing@intel.com, qi.z.zhang@intel.com
Subject: Re: [dpdk-dev] Intel X710, DPDK with SFP - FTLX8574D3BCV-IT link down
Date: Tue, 19 Nov 2019 14:03:35 +0530 [thread overview]
Message-ID: <CAJ4PSvRbn0qN9zp1EEjb+L55P5a4HXf+ioUm3b2zjKcfecK7fA@mail.gmail.com> (raw)
In-Reply-To: <CAJ4PSvQiG8eEt0J+e34_WwKMqqFSy2cTk4SKG_MryB960PTyhA@mail.gmail.com>
Adding Beilei Xing and Qi Zhang
Thanks and Regards,
Amit
On Mon, Nov 18, 2019 at 2:39 PM amit shukla <amitshukla19@gmail.com> wrote:
> Hello,
>
> Using a X710 based NIC with Intel SFP - FTLX8574D3BCV-IT on a bare-metal
> setup, I came across the following issue on the i40e PMD:
>
> When Intel SFP - FTLX8574D3BCV-IT is used, link does not come up on
> executing link down and up commands in quick succession. It shows
> "NO-CARRIER" in ip link show.
>
> #ip link set dev eth0 down; ip link set dev eth0 up
> #
> # ip link show dev eth0
> 304: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast
> state DOWN mode DEFAULT group default qlen 1000
> link/ether xx:xx:xx:xx:xx:xx brd ff:ff:ff:ff:ff:ff
>
> On the 1st command, ip link set dev eth0 down,
> i40e_aq_get_phy_capabilities returns success but for next command (ip link
> set dev eth0 up) it returns I40E_ERR_UNKNOWN_PHY (-7).
>
> If link down and up commands are executed with a sleep of 1 second
> in-between them, then issue is not observed.
>
> Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz
> DPDK - 17.05
> NIC firmware-version: 4.53 0x80001e5b 17.0.12
> 05:00.0 Ethernet controller: Intel Corporation Ethernet Controller X710
> for 10GbE SFP+ (rev 02)
> Subsystem: Intel Corporation Ethernet 10G 2P X710 Adapter
>
> Thanks and Regards,
> Amit Shukla
>
next prev parent reply other threads:[~2019-11-19 8:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-18 9:09 amit shukla
2019-11-19 8:33 ` amit shukla [this message]
2019-11-25 11:47 ` amit shukla
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=CAJ4PSvRbn0qN9zp1EEjb+L55P5a4HXf+ioUm3b2zjKcfecK7fA@mail.gmail.com \
--to=amitshukla19@gmail.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--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).