From: "Mathew McBride" <matt@traverse.com.au>
To: "Russell King (Oracle)" <linux@armlinux.org.uk>
Cc: netdev@vger.kernel.org, regressions@lists.linux.dev
Subject: Re: [REGRESSION] net: pcs-lynx: 10G SFP no longer links up
Date: Thu, 10 Jul 2025 15:29:01 +1000 [thread overview]
Message-ID: <2d709754-3d4a-4803-b86f-9efa2a6bf655@app.fastmail.com> (raw)
In-Reply-To: <f7eac1d6-34eb-4eba-937d-c6624f9a6826@app.fastmail.com>
Hi Russell,
On Wed, Apr 23, 2025, at 7:01 PM, Mathew McBride wrote:
>
[snip]
Just following up on this issue where directly connected SFP+ modules stopped linking up after the introduction of in-band capabilities.
The diff you provided below[1] resolved the issue.
Were you planning on submitting it as a patch? If not, I'd be happy to send it in.
Best Regards,
Matt
[1] https://lore.kernel.org/all/aAe94Tkf-IYjswfP@shell.armlinux.org.uk/
> Thanks Russell!
>
> The diff below does fix the problem, 10G SFP's now link up again.
>
> I should note that Alex Guzman was the one who originally reported the issue to me, he has also confirmed this diff resolves the issue.
> Link: https://forum.traverse.com.au/t/sfp-ports-stop-working-with-linux-6-14-in-arch-linux/1076/4
>
> > Please try the diff below:
> >
> > diff --git a/drivers/net/phy/phylink.c b/drivers/net/phy/phylink.c
> > index 1bdd5d8bb5b0..2147e2d3003a 100644
> > --- a/drivers/net/phy/phylink.c
> > +++ b/drivers/net/phy/phylink.c
> > @@ -3624,6 +3624,15 @@ static int phylink_sfp_config_optical(struct phylink *pl)
> > phylink_dbg(pl, "optical SFP: chosen %s interface\n",
> > phy_modes(interface));
> >
> > + /* GBASE-R interfaces with the exception of KR do not have autoneg at
> > + * the PCS. As the PCS is media facing, disable the Autoneg bit in the
> > + * advertisement.
> > + */
> > + if (interface == PHY_INTERFACE_MODE_5GBASER ||
> > + interface == PHY_INTERFACE_MODE_10GBASER ||
> > + interface == PHY_INTERFACE_MODE_25GBASER)
> > + __clear_bit(ETHTOOL_LINK_MODE_Autoneg_BIT, config.advertising);
> > +
> > if (!phylink_validate_pcs_inband_autoneg(pl, interface,
> > config.advertising)) {
> > phylink_err(pl, "autoneg setting not compatible with PCS");
> >
> > --
> > RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
> > FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
> >
>
next prev parent reply other threads:[~2025-07-10 5:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-05 9:42 [PATCH net-next 0/3] net: net: add negotiation of in-band capabilities (remainder) Russell King (Oracle)
2024-12-05 9:42 ` [PATCH net-next 1/3] net: pcs: pcs-lynx: implement pcs_inband_caps() method Russell King (Oracle)
2025-04-18 3:02 ` [REGRESSION] net: pcs-lynx: 10G SFP no longer links up Mathew McBride
2025-04-22 16:03 ` Russell King (Oracle)
2025-04-23 9:01 ` Mathew McBride
2025-07-10 5:29 ` Mathew McBride [this message]
2025-08-12 12:17 ` Thorsten Leemhuis
2025-08-12 16:42 ` Russell King (Oracle)
2025-08-15 10:18 ` Russell King (Oracle)
2025-08-18 9:59 ` Mathew McBride
2025-07-13 15:02 ` [PATCH net-next 1/3] net: pcs: pcs-lynx: implement pcs_inband_caps() method Josua Mayer
2024-12-05 9:42 ` [PATCH net-next 2/3] net: pcs: pcs-mtk-lynxi: " Russell King (Oracle)
2024-12-08 3:01 ` Daniel Golle
2024-12-08 9:13 ` Russell King (Oracle)
2025-01-02 12:26 ` Daniel Golle
2025-01-03 10:55 ` Russell King (Oracle)
2024-12-17 7:49 ` Eric Woudstra
2025-01-02 8:59 ` Russell King (Oracle)
2025-01-02 12:32 ` Daniel Golle
2024-12-05 9:42 ` [PATCH net-next 3/3] net: pcs: xpcs: " Russell King (Oracle)
2024-12-08 2:00 ` [PATCH net-next 0/3] net: net: add negotiation of in-band capabilities (remainder) patchwork-bot+netdevbpf
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=2d709754-3d4a-4803-b86f-9efa2a6bf655@app.fastmail.com \
--to=matt@traverse.com.au \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=regressions@lists.linux.dev \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).