Do you know why the driver is poorly integrated with the PHY on these devices? There is an unmitigated thermal loss on X552; PHY gets too hot and connectivity drops, you usually have to cycle the system. It should be possible to reset the PHY and other Intel NICs implement this.
See: https://tinkertry.com/how-to-work-around-intermittent-intel-x557-network-outages-on-12-core-xeon-d On Tue, Jan 4, 2022 at 12:17 PM Fujinaka, Todd <todd.fujin...@intel.com> wrote: > > I had to ask for help on this as I don't keep up with SoC parts, but the > problem appears that we don't support the copper module. Until you reboot, > the part could be confused if you plug it in. > > This should all be in the readme: > > Devices based on the Intel(R) Ethernet Connection X552 and Intel(R) Ethernet > Connection X553 do not support the following features: > * Energy Efficient Ethernet (EEE) > * Intel PROSet for Windows Device Manager > * Intel ANS teams or VLANs (LBFO is supported) > * Data Center Bridging (DCB) > * IPSec Offloading > * MACSec Offloading > In addition, SFP+ devices based on the Intel(R) Ethernet Connection X552 and > Intel(R) Ethernet Connection X553 do not support the following features: > * Speed and duplex auto-negotiation. > * Wake on LAN > * 1000BASE-T SFP Modules > > > Todd Fujinaka > Software Application Engineer > Ethernet Products Group > Intel Corporation > todd.fujin...@intel.com > > -----Original Message----- > From: SPRTN <sp...@sprtndev.com> > Sent: Friday, December 31, 2021 12:51 AM > To: e1000-de...@lists.sf.net > Subject: [E1000-devel] Issue With IXGBE > > Support Team, > > I noticed a potential issue with the IXGBE 5.13.4. > > My hardware is a Supermicro A2SDI-TP8F, using it's two SFP+ ports that are > using Intel X553 drivers. I am using the Untangle OS 16.4.1, which is based > off of Ubuntu. > > When a Copper module is plugged into the SFP+ port the ethtool command shows, > FIBRE, however, when a Fiber/Optical Direct Attach Cable is used the ethtool > command shows Copper Direct Attach, and no connection is ever established. Is > it possible that there is an issue in the *.ko file? > > Appreciate your time and help. If there is any more information you need me > to send over, please let me know. > > Very Respectfully, > Kostas Diotis > _______________________________________________ > E1000-devel mailing list > E1000-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/e1000-devel > To learn more about Intel Ethernet, visit > https://forums.intel.com/s/topic/0TO0P00000018NbWAI/intel-ethernet > > > _______________________________________________ > E1000-devel mailing list > E1000-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/e1000-devel > To learn more about Intel Ethernet, visit > https://forums.intel.com/s/topic/0TO0P00000018NbWAI/intel-ethernet _______________________________________________ E1000-devel mailing list E1000-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/e1000-devel To learn more about Intel Ethernet, visit https://forums.intel.com/s/topic/0TO0P00000018NbWAI/intel-ethernet
