[Intel-wired-lan] ixgbe-x550 link detection after boot

Fujinaka, Todd todd.fujinaka at intel.com
Wed Jul 1 22:02:32 UTC 2020


That doesn’t sound right. Denverton is x553. But I don’t generally do SOC so let me try to get someone else to look at this.

Todd Fujinaka
Software Application Engineer
Data Center Group
Intel Corporation
todd.fujinaka at intel.com

From: Intel-wired-lan <intel-wired-lan-bounces at osuosl.org> On Behalf Of Paul Stewart
Sent: Wednesday, July 1, 2020 2:09 PM
To: intel-wired-lan at lists.osuosl.org
Subject: [Intel-wired-lan] ixgbe-x550 link detection after boot

Hi there.  I have a system with a Denverton based chipset which has a built-in 4 ports of 10GBE.  It's properly configured to enumerate as 8086:15c6 (IXGBE_DEV_ID_X550EM_A_SGMII).  It also successfully detects link to its backplane partner with the stock ixgbe driver, but only if that partner is up and running before the driver starts up.  If the Denverton chipset comes up first, nothing I've tried so far as succeeded in having the chipset detect link.  I've tried the normal "ifconfig down/up", "ethtool -A eth1 autoneg off" etc, but nothing so far seems to do as much as just rebooting the system.  Are there any hints as to how I can get this going?  I've also tried "hw->mac.ops.reset_hw(hw)" and calling "hw->mac.ops.setup_link()" again from the kernel and that surprisingly didn't work either, so I'm getting curious as to what can get the system to re-evaluate link state.  It's really true that the Links status register does not mark the link as up (as shown by ethtool -d).

If it's of any consequence the SGMII link partner is a Marvell 88E1512.  MDIO is not connected.  For its part, the Marvell part detects link from the Denverton whether or not that understanding is reciprocal.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osuosl.org/pipermail/intel-wired-lan/attachments/20200701/b00f9d92/attachment-0001.html>


More information about the Intel-wired-lan mailing list