From: Maxime Chevallier <maxime.chevallier@bootlin.com>
To: Andrew Lunn <andrew@lunn.ch>,
Sven Schuchmann <schuchmann@schleissheimer.de>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: assert in phylink.c with lan7801 and dp83tc811 since kernel 6.18
Date: Wed, 6 May 2026 15:04:42 +0200 [thread overview]
Message-ID: <f9b8840d-94ba-4bde-9ace-fb81eb733ff9@bootlin.com> (raw)
In-Reply-To: <7778cd41-cf36-4524-a347-408a8fb0bde0@lunn.ch>
On 06/05/2026 14:39, Andrew Lunn wrote:
>> So for me it somewhere happens in phylink_validate_mac_and_pcs()
>
> I was expecting to see more debug output, but reading the code, i was
> also thinking we need to look at phylink_validate_mac_and_pcs().
>
> You are going in the correct direction putting lots of printk() in the
> code. We need to find where it returns EINVAL:
[...]
>
> In the end, we are probably going to find that what the MAC says its
> capabilities are don't match what the PCS says it can do.
>
> Thinking about that, it says phy mode RGMII. You generally don't use a
> PCS with RGMII, so that is suspicious.
>
Another thing to consider is that in this case, we're attaching to a
dp83tc811, so a 100BaseT1 PHY. Does the PHY driver correctly populates
the supported features ?
Could be that we're getting an empty-ish phydev->supported after reading
the abilities, as this is not a typical BaseT PHY
Maxime
next prev parent reply other threads:[~2026-05-06 13:04 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 [this message]
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=f9b8840d-94ba-4bde-9ace-fb81eb733ff9@bootlin.com \
--to=maxime.chevallier@bootlin.com \
--cc=andrew@lunn.ch \
--cc=netdev@vger.kernel.org \
--cc=schuchmann@schleissheimer.de \
/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