DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Dey, Souvik" <sodey@rbbn.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "xiaolong.ye@intel.com" <xiaolong.ye@intel.com>,
	"xiao.zhang@intel.com" <xiao.zhang@intel.com>,
	"users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-dev] Issue with X550 link status
Date: Wed, 4 Mar 2020 13:16:47 -0500
Message-ID: <DM6PR03MB477756EB043F91666CE811A5CDE50@DM6PR03MB4777.namprd03.prod.outlook.com> (raw)

Hi All,
              After upgrading to DPDK 18.11.6 LTS release from 18.11.2 the link_update call for link status update is not working for  X550 NICs SR-IOV enabled. On debugging it looks like the change introduced as a part of this patch is causing the issue.

https://patches.dpdk.org/patch/62140/

@@ -4135,6 +4138,10 @@  ixgbe_dev_link_update_share(struct rte_eth_dev *dev,
              return rte_eth_linkstatus_set(dev, &link);
       }
+       esdp_reg = IXGBE_READ_REG(hw, IXGBE_ESDP);
+       if ((esdp_reg & IXGBE_ESDP_SDP3))
+              link_up = 0;
+
       if (link_up == 0) {
              if (ixgbe_get_media_type(hw) == ixgbe_media_type_fiber) {
                      intr->flags |= IXGBE_FLAG_NEED_LINK_CONFIG;


I can see that the esdp_req is coming as 3735928495(0xDEADBEAF) and due to which the link_up is set to 0 even when ixgbevf_check_link returned link_up as 1. Along with this patch I also see a path_fullchk patch introduced , does that play any role in this ?
Can someone please let me know if the patch has got some issues or it is behaving correctly and the link_status is failing for valid reason. As mentioned earlier the same HW with same NIC acting in SR-IOV works fine with 18.11.2 DPDK . I am blocked at a customer bug dew to this and any urgent help will be much appreciated.

--
Regards,
Souvik


-----------------------------------------------------------------------------------------------------------------------
Notice: This e-mail together with any attachments may contain information of Ribbon Communications Inc. that
is confidential and/or proprietary for the sole use of the intended recipient.  Any review, disclosure, reliance or
distribution by others or forwarding without express permission is strictly prohibited.  If you are not the intended
recipient, please notify the sender immediately and then delete all copies, including any attachments.
-----------------------------------------------------------------------------------------------------------------------

             reply	other threads:[~2020-03-04 18:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-04 18:16 Dey, Souvik [this message]
2020-03-04 21:08 ` Dey, Souvik
2020-03-04 21:22   ` Dey, Souvik
2020-03-06  1:26     ` Zhang, Xiao
2020-03-09 17:32     ` Kevin Traynor

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=DM6PR03MB477756EB043F91666CE811A5CDE50@DM6PR03MB4777.namprd03.prod.outlook.com \
    --to=sodey@rbbn.com \
    --cc=dev@dpdk.org \
    --cc=users@dpdk.org \
    --cc=xiao.zhang@intel.com \
    --cc=xiaolong.ye@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

DPDK patches and discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/dev/0 dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dev dev/ https://inbox.dpdk.org/dev \
		dev@dpdk.org
	public-inbox-index dev

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.dev


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git