The X550 NIC is of the below device id.
[root@stdell10 ~]# lspci -nnn | grep -i ether
19:00.0 Ethernet controller [0200]: Intel Corporation Ethernet Controller 10G 
X550T [8086:1563] (rev 01)
19:00.1 Ethernet controller [0200]: Intel Corporation Ethernet Controller 10G 
X550T [8086:1563] (rev 01)
19:10.0 Ethernet controller [0200]: Intel Corporation X550 Virtual Function 
[8086:1565]
19:10.1 Ethernet controller [0200]: Intel Corporation X550 Virtual Function 
[8086:1565]
19:10.2 Ethernet controller [0200]: Intel Corporation X550 Virtual Function 
[8086:1565]
19:10.3 Ethernet controller [0200]: Intel Corporation X550 Virtual Function 
[8086:1565]

So the mac_type is ixgbe_mac_X550_vf  in the below case.

--
Regards,
Souvik

From: Dey, Souvik
Sent: Wednesday, March 4, 2020 1:17 PM
To: dev@dpdk.org
Cc: xiaolong...@intel.com; xiao.zh...@intel.com; us...@dpdk.org
Subject: Issue with X550 link status

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 via email to