From: Sven Schuchmann <schuchmann@schleissheimer.de>
To: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: assert in phylink.c with lan7801 and dp83tc811 since kernel 6.18
Date: Tue, 5 May 2026 09:53:06 +0000 [thread overview]
Message-ID: <BEZP281MB224533D524B27CFC6E47B447D93E2@BEZP281MB2245.DEUP281.PROD.OUTLOOK.COM> (raw)
Hello,
I have a raspberrypi and switched from kernel 6.12 to 6.18 and now I have a crash in phylink.c.
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
[ 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)
[ 3.105386] WARNING: CPU: 2 PID: 28 at drivers/net/phy/phylink.c:2337 phylink_disconnect_phy+0xf0/0x100
[ 3.297049] Modules linked in: ipv6 libsha1
[ 3.302904] CPU: 2 UID: 0 PID: 28 Comm: kworker/2:0 Not tainted 6.18.26 #2 PREEMPT
[ 3.313657] Hardware name: Raspberry Pi Compute Module 4 Rev 1.1 (DT)
[ 3.321854] Workqueue: usb_hub_wq hub_event
[ 3.327898] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 3.336686] pc : phylink_disconnect_phy+0xf0/0x100
[ 3.343391] lr : phylink_disconnect_phy+0xf0/0x100
[ 3.350035] sp : ffffffc08011b500
[ 3.355285] x29: ffffffc08011b500 x28: ffffff8043918a00 x27: ffffff8043918aa0
[ 3.364170] x26: ffffffd86a3ee000 x25: ffffff8043918a40 x24: 0000000000000000
[ 3.373083] x23: 0000000000000010 x22: ffffff80448f6000 x21: 00000000ffffffea
[ 3.382070] x20: ffffff80448f5800 x19: ffffff8041e09600 x18: 0000000000000006
[ 3.390835] x17: 74612074276e6163 x16: 203a2964657a696c x15: ffffffc08011af10
[ 3.399551] x14: 0000000000000000 x13: ffffff8040868540 x12: ffffffc08011afe8
[ 3.407285] x11: 0000000000001e00 x10: ffffffd86a1aecf8 x9 : ffffffd868935570
[ 3.415974] x8 : 00000000ffffefff x7 : ffffffd86a1aecf8 x6 : 80000000fffff000
[ 3.424655] x5 : 000000000000013c x4 : 0000000000000000 x3 : 0000000000000000
[ 3.433329] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffffff8040838000
[ 3.441991] Call trace:
[ 3.445951] phylink_disconnect_phy+0xf0/0x100 (P)
[ 3.452249] lan78xx_probe+0xbcc/0xe18
[ 3.457460] usb_probe_interface+0xd8/0x2b8
[ 3.463100] really_probe+0xc4/0x2b0
[ 3.468141] __driver_probe_device+0x80/0x140
[ 3.473945] driver_probe_device+0xe0/0x170
[ 3.479559] __device_attach_driver+0xc0/0x148
[ 3.485426] bus_for_each_drv+0x90/0xf8
[ 3.490669] __device_attach+0xa8/0x1a0
[ 3.495914] device_initial_probe+0x1c/0x30
[ 3.501476] bus_probe_device+0xb4/0xc0
[ 3.506658] device_add+0x588/0x768
[ 3.511470] usb_set_configuration+0x4b4/0xaa0
[ 3.517231] usb_generic_driver_probe+0x68/0x98
[ 3.523074] usb_probe_device+0x44/0x128
[ 3.528243] really_probe+0xc4/0x2b0
[ 3.533015] __driver_probe_device+0x80/0x140
[ 3.538536] driver_probe_device+0xe0/0x170
[ 3.543874] __device_attach_driver+0xc0/0x148
[ 3.549475] bus_for_each_drv+0x90/0xf8
[ 3.554471] __device_attach+0xa8/0x1a0
[ 3.559458] device_initial_probe+0x1c/0x30
[ 3.564768] bus_probe_device+0xb4/0xc0
[ 3.569671] device_add+0x588/0x768
[ 3.574233] usb_new_device+0x400/0x4f0
[ 3.579126] hub_event+0xddc/0x1578
[ 3.583646] process_one_work+0x158/0x3b8
[ 3.588662] worker_thread+0x194/0x328
[ 3.593398] kthread+0x14c/0x210
[ 3.597604] ret_from_fork+0x10/0x20
[ 3.602138] ---[ end trace 0000000000000000 ]---
[ 3.617830] lan78xx 1-1.3:1.0: probe with driver lan78xx failed with error -22
it seems to happen over here:
/**
* phylink_disconnect_phy() - disconnect any PHY attached to the phylink
* instance.
* @pl: a pointer to a &struct phylink returned from phylink_create()
*
* Disconnect any current PHY from the phylink instance described by @pl.
*/
void phylink_disconnect_phy(struct phylink *pl)
{
struct phy_device *phy;
ASSERT_RTNL();
Maybe anyone can help me?
Regards,
Sven
next reply other threads:[~2026-05-05 9:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-05 9:53 Sven Schuchmann [this message]
2026-05-05 13:13 ` assert in phylink.c with lan7801 and dp83tc811 since kernel 6.18 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
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=BEZP281MB224533D524B27CFC6E47B447D93E2@BEZP281MB2245.DEUP281.PROD.OUTLOOK.COM \
--to=schuchmann@schleissheimer.de \
--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