From: Sven Schuchmann <schuchmann@schleissheimer.de>
To: Andrew Lunn <andrew@lunn.ch>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: AW: assert in phylink.c with lan7801 and dp83tc811 since kernel 6.18
Date: Wed, 6 May 2026 12:30:33 +0000 [thread overview]
Message-ID: <BEZP281MB224573FE237813F5DE192A95D93F2@BEZP281MB2245.DEUP281.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <57fb63c2-7a05-4bbe-ba2d-fc61ce1e3ba1@lunn.ch>
Hi Andrew,
I came up with this:
diff --git a/drivers/net/usb/lan78xx.c b/drivers/net/usb/lan78xx.c
index 261af300ab00..734cb62a1043 100644
--- a/drivers/net/usb/lan78xx.c
+++ b/drivers/net/usb/lan78xx.c
@@ -2862,7 +2862,9 @@ static int lan78xx_phylink_setup(struct lan78xx_net *dev)
static void lan78xx_phy_uninit(struct lan78xx_net *dev)
{
if (dev->phylink) {
+ rtnl_lock();
phylink_disconnect_phy(dev->phylink);
+ rtnl_unlock();
phylink_destroy(dev->phylink);
dev->phylink = NULL;
}
and it seems to prevent the cash. What do you think?
Reards,
Sven
Von: Andrew Lunn <andrew@lunn.ch>
Gesendet: Dienstag, 05. Mai 2026 15:13
An: Sven Schuchmann <schuchmann@schleissheimer.de>
Cc: netdev@vger.kernel.org <netdev@vger.kernel.org>
Betreff: Re: assert in phylink.c with lan7801 and dp83tc811 since kernel 6.18
On Tue, May 05, 2026 at 09:53:06AM +0000, Sven Schuchmann wrote:
> Hello,
> I have a raspberrypi and switched from kernel 6.12 to 6.18 and now I have a crash in phylink.c.
Please could you try 7.0.3, or better still, 7.1-rcX. We need to
determine if the problem has already been fixed and just needs
backporting, or is it a new problem.
> I am using a MAC:lan7801 and PHY:dp83tc811 and now it crashes like this:
>
> [ 3.019174] usb 1-1.3: New USB device found, idVendor=0424, idProduct=7801, bcdDevice= 3.00
> [ 3.021152] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> [ 3.023192] usb 1-1.3: Product: LAN7801
> [ 3.025019] usb 1-1.3: Manufacturer: Microchip
> [ 3.026772] usb 1-1.3: SerialNumber: 00800F780100
> [ 3.078542] lan78xx 1-1.3:1.0 (unnamed net_device) (uninitialized): int urb period 64
> [ 3.091434] lan78xx 1-1.3:1.0 (unnamed net_device) (uninitialized): validation of rgmii-id with support 0000000,00000000,00000000,00006280 and advertis ement 0000000,00000000,00000000,00006280 failed: -EINVAL
This appears to be the real problem.
> [ 3.098928] lan78xx 1-1.3:1.0 (unnamed net_device) (uninitialized): can't attach PHY to usb-001:004, error -EINVAL
> [ 3.101094] ------------[ cut here ]------------
> [ 3.103163] RTNL: assertion failed at drivers/net/phy/phylink.c (2337)
and this is a knock on problem, which normally you don't see.
Please could you make line 1 of drivers/net/phy/phylink.c.
#define DEBUG 1
That will give us additional debug info.
Andrew
next prev parent reply other threads:[~2026-05-06 12:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-05 9:53 assert in phylink.c with lan7801 and dp83tc811 since kernel 6.18 Sven Schuchmann
2026-05-05 13:13 ` Andrew Lunn
2026-05-06 11:10 ` AW: " Sven Schuchmann
2026-05-06 12:39 ` Andrew Lunn
2026-05-06 13:04 ` Maxime Chevallier
2026-05-06 13:18 ` Andrew Lunn
2026-05-06 16:00 ` AW: " Sven Schuchmann
2026-05-06 16:40 ` Andrew Lunn
2026-05-07 6:52 ` AW: " Sven Schuchmann
2026-05-07 12:49 ` Andrew Lunn
2026-05-06 13:15 ` Andrew Lunn
2026-05-06 14:36 ` AW: " Sven Schuchmann
2026-05-06 12:30 ` Sven Schuchmann [this message]
2026-05-06 12:52 ` Andrew Lunn
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=BEZP281MB224573FE237813F5DE192A95D93F2@BEZP281MB2245.DEUP281.PROD.OUTLOOK.COM \
--to=schuchmann@schleissheimer.de \
--cc=andrew@lunn.ch \
--cc=netdev@vger.kernel.org \
/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