From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by dpdk.org (Postfix, from userid 33) id A630C4CC3; Wed, 1 May 2019 08:54:06 +0200 (CEST) From: bugzilla@dpdk.org To: dev@dpdk.org Date: Wed, 01 May 2019 06:54:06 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: DPDK X-Bugzilla-Component: ethdev X-Bugzilla-Version: 17.11 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ido@cgstowernetworks.com X-Bugzilla-Status: CONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: dev@dpdk.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All MIME-Version: 1.0 Subject: [dpdk-dev] [Bug 263] ixgbe does not support 10GBASE-T copper SFP+ X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 May 2019 06:54:06 -0000 https://bugs.dpdk.org/show_bug.cgi?id=3D263 Bug ID: 263 Summary: ixgbe does not support 10GBASE-T copper SFP+ Product: DPDK Version: 17.11 Hardware: x86 OS: Linux Status: CONFIRMED Severity: normal Priority: Normal Component: ethdev Assignee: dev@dpdk.org Reporter: ido@cgstowernetworks.com Target Milestone: --- Tried couple of vendor's 10GBASE-T copper SFPs and they fail at init Transceiver example http://www.eoptolink.com/products/copper-10g-sfp root@AFS:/home/cgs# ./testpmd -c7 -n3 -w 0000:0a:00.0 -- -i EAL: Detected 28 lcore(s) EAL: Detected 2 NUMA nodes EAL: Multi-process socket /var/run/dpdk/rte/mp_socket EAL: No available hugepages reported in hugepages-1048576kB EAL: Probing VFIO support... EAL: PCI device 0000:0a:00.0 on NUMA socket 0 EAL: probe driver: 8086:10fb net_ixgbe eth_ixgbe_dev_init(): Unsupported SFP+ Module eth_ixgbe_dev_init(): Hardware Initialization Failure: -19 EAL: ethdev initialisation failedEAL: Requested device 0000:0a:00.0 cannot be used testpmd: No probed ethernet devices Tested in 2 different Intel controllers 82599ES and X552=20 cgs@AFS:~# lspci -s 0a:00.0 0a:00.0 Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection (rev 01) cgs@AFS:~$ lspci -s 04:00.0 04:00.0 Ethernet controller: Intel Corporation Ethernet Connection = X552 10 GbE SFP+ If the SFPs is inserted only *after* the dpdk app starts (after rte_eal_init and pci devices are probed) it will work!=20 as it is only identified and blocked as not supported in ixgbe_identify_sfp_module_generic Though the ixgbe_identify_sfp_module_generic function tries to be premissiv= e in case the allow_unsupported_sfp is set if (hw->allow_unsupported_sfp =3D=3D true) { EWARN(hw, "WARNING: Intel (R) Network Connect= ions are quality tested using Intel (R) Ethernet Optics. " "Using untested modules is not supported and may cause unstable operation or damage to the module or the adapter. " "Intel Corporation is not responsib= le for any harm caused by using untested modules.\n"); status =3D IXGBE_SUCCESS; } but this is too late as this SFP falls into earlier case in the function /* Verify supported 1G SFP modules */ if (comp_codes_10g =3D=3D 0 && !(hw->phy.sfp_type =3D=3D ixgbe_sfp_type_1g_cu_core1 || hw->phy.sfp_type =3D=3D ixgbe_sfp_type_1g_cu_core0 || hw->phy.sfp_type =3D=3D ixgbe_sfp_type_1g_lx_core0 || hw->phy.sfp_type =3D=3D ixgbe_sfp_type_1g_lx_core1 || hw->phy.sfp_type =3D=3D ixgbe_sfp_type_1g_sx_core0 || hw->phy.sfp_type =3D=3D ixgbe_sfp_type_1g_sx_core1)) { hw->phy.type =3D ixgbe_phy_sfp_unsupported; status =3D IXGBE_ERR_SFP_NOT_SUPPORTED; goto out; } The driver reads 0 from eeprom IXGBE_SFF_10GBE_COMP_CODES offset and comp_codes_10g=3D0=20 I guess because there's no 10GBASE-T code defined in SFF-8472 TABLE 5-3 TRANSCEIVER COMPLIANCE CODES [https://members.snia.org/document/dl/25916]=20 This same 10GBASE-T SFP does work in i40e controllers see more info and suggested patch in http://mails.dpdk.org/archives/dev/2019-April/131091.html --=20 You are receiving this mail because: You are the assignee for the bug.= From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id 5BAC6A0ACC for ; Wed, 1 May 2019 08:54:09 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id BB6D14CC3; Wed, 1 May 2019 08:54:07 +0200 (CEST) Received: by dpdk.org (Postfix, from userid 33) id A630C4CC3; Wed, 1 May 2019 08:54:06 +0200 (CEST) From: bugzilla@dpdk.org To: dev@dpdk.org Date: Wed, 01 May 2019 06:54:06 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: DPDK X-Bugzilla-Component: ethdev X-Bugzilla-Version: 17.11 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ido@cgstowernetworks.com X-Bugzilla-Status: CONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: dev@dpdk.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All MIME-Version: 1.0 Subject: [dpdk-dev] [Bug 263] ixgbe does not support 10GBASE-T copper SFP+ X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Message-ID: <20190501065406.5QcWajpcHhAihIyuZBIEMaiwZOINtkdqa_ghJ5Gzb9o@z> https://bugs.dpdk.org/show_bug.cgi?id=3D263 Bug ID: 263 Summary: ixgbe does not support 10GBASE-T copper SFP+ Product: DPDK Version: 17.11 Hardware: x86 OS: Linux Status: CONFIRMED Severity: normal Priority: Normal Component: ethdev Assignee: dev@dpdk.org Reporter: ido@cgstowernetworks.com Target Milestone: --- Tried couple of vendor's 10GBASE-T copper SFPs and they fail at init Transceiver example http://www.eoptolink.com/products/copper-10g-sfp root@AFS:/home/cgs# ./testpmd -c7 -n3 -w 0000:0a:00.0 -- -i EAL: Detected 28 lcore(s) EAL: Detected 2 NUMA nodes EAL: Multi-process socket /var/run/dpdk/rte/mp_socket EAL: No available hugepages reported in hugepages-1048576kB EAL: Probing VFIO support... EAL: PCI device 0000:0a:00.0 on NUMA socket 0 EAL: probe driver: 8086:10fb net_ixgbe eth_ixgbe_dev_init(): Unsupported SFP+ Module eth_ixgbe_dev_init(): Hardware Initialization Failure: -19 EAL: ethdev initialisation failedEAL: Requested device 0000:0a:00.0 cannot be used testpmd: No probed ethernet devices Tested in 2 different Intel controllers 82599ES and X552=20 cgs@AFS:~# lspci -s 0a:00.0 0a:00.0 Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection (rev 01) cgs@AFS:~$ lspci -s 04:00.0 04:00.0 Ethernet controller: Intel Corporation Ethernet Connection = X552 10 GbE SFP+ If the SFPs is inserted only *after* the dpdk app starts (after rte_eal_init and pci devices are probed) it will work!=20 as it is only identified and blocked as not supported in ixgbe_identify_sfp_module_generic Though the ixgbe_identify_sfp_module_generic function tries to be premissiv= e in case the allow_unsupported_sfp is set if (hw->allow_unsupported_sfp =3D=3D true) { EWARN(hw, "WARNING: Intel (R) Network Connect= ions are quality tested using Intel (R) Ethernet Optics. " "Using untested modules is not supported and may cause unstable operation or damage to the module or the adapter. " "Intel Corporation is not responsib= le for any harm caused by using untested modules.\n"); status =3D IXGBE_SUCCESS; } but this is too late as this SFP falls into earlier case in the function /* Verify supported 1G SFP modules */ if (comp_codes_10g =3D=3D 0 && !(hw->phy.sfp_type =3D=3D ixgbe_sfp_type_1g_cu_core1 || hw->phy.sfp_type =3D=3D ixgbe_sfp_type_1g_cu_core0 || hw->phy.sfp_type =3D=3D ixgbe_sfp_type_1g_lx_core0 || hw->phy.sfp_type =3D=3D ixgbe_sfp_type_1g_lx_core1 || hw->phy.sfp_type =3D=3D ixgbe_sfp_type_1g_sx_core0 || hw->phy.sfp_type =3D=3D ixgbe_sfp_type_1g_sx_core1)) { hw->phy.type =3D ixgbe_phy_sfp_unsupported; status =3D IXGBE_ERR_SFP_NOT_SUPPORTED; goto out; } The driver reads 0 from eeprom IXGBE_SFF_10GBE_COMP_CODES offset and comp_codes_10g=3D0=20 I guess because there's no 10GBASE-T code defined in SFF-8472 TABLE 5-3 TRANSCEIVER COMPLIANCE CODES [https://members.snia.org/document/dl/25916]=20 This same 10GBASE-T SFP does work in i40e controllers see more info and suggested patch in http://mails.dpdk.org/archives/dev/2019-April/131091.html --=20 You are receiving this mail because: You are the assignee for the bug.=