From: Thorsten Leemhuis <regressions@leemhuis.info>
To: "regressions@lists.linux.dev" <regressions@lists.linux.dev>
Cc: LKML <linux-kernel@vger.kernel.org>, netdev <netdev@vger.kernel.org>
Subject: Re: Bug 216320 - KSZ8794 operation broken #forregzbot
Date: Tue, 23 Aug 2022 18:47:24 +0200 [thread overview]
Message-ID: <7c41dd25-8bfa-c7b0-a430-1b115e8ee375@leemhuis.info> (raw)
In-Reply-To: <967ef480-2fac-9724-61c7-2d5e69c26ec3@leemhuis.info>
TWIMC: this mail is primarily send for documentation purposes and for
regzbot, my Linux kernel regression tracking bot. These mails usually
contain '#forregzbot' in the subject, to make them easy to spot and filter.
On 17.08.22 15:36, Thorsten Leemhuis wrote:
> Hi, this is your Linux kernel regression tracker.
>
> I noticed a regression report in bugzilla.kernel.org that afaics nobody
> acted upon since it was reported. That's why I decided to forward it by
> mail to those that afaics should handle this.
>
> To quote from https://bugzilla.kernel.org/show_bug.cgi?id=216320 :
>
>> After upgrading a Yocto build system from kernel 5.4 to 5.15, I found KSZ8794 switch operation was no longer functional. I got errors such as:
>>
>> Aug 1 22:23:17 tv999996 kern.err kernel: [ 10.770912] ksz8795-switch spi2.0: Unsupported interface: gmii, port: 0
>> Aug 1 22:23:17 tv999996 kern.warn kernel: [ 10.777562] ksz8795-switch spi2.0 wan (uninitialized): validation of gmii with support 0000000,00000000,000062cf and advertisement 0000000,00000000,000062cf failed: -22
>> Aug 1 22:23:17 tv999996 kern.err kernel: [ 10.792874] ksz8795-switch spi2.0 wan (uninitialized): failed to connect to PHY: -EINVAL
>> Aug 1 22:23:17 tv999996 kern.err kernel: [ 10.800978] ksz8795-switch spi2.0 wan (uninitialized): error -22 setting up PHY for tree 0, switch 0, port 0
>> Aug 1 22:23:17 tv999996 kern.err kernel: [ 10.829188] ksz8795-switch spi2.0: Unsupported interface: gmii, port: 1
>> Aug 1 22:23:17 tv999996 kern.warn kernel: [ 10.835821] ksz8795-switch spi2.0 lan2 (uninitialized): validation of gmii with support 0000000,00000000,000062cf and advertisement 0000000,00000000,000062cf failed: -22
>> Aug 1 22:23:17 tv999996 kern.err kernel: [ 10.851156] ksz8795-switch spi2.0 lan2 (uninitialized): failed to connect to PHY: -EINVAL
>> Aug 1 22:23:17 tv999996 kern.err kernel: [ 10.859358] ksz8795-switch spi2.0 lan2 (uninitialized): error -22 setting up PHY for tree 0, switch 0, port 1
>> Aug 1 22:23:17 tv999996 kern.err kernel: [ 10.892821] ksz8795-switch spi2.0: Unsupported interface: gmii, port: 2
>> Aug 1 22:23:17 tv999996 kern.warn kernel: [ 10.899466] ksz8795-switch spi2.0 lan1 (uninitialized): validation of gmii with support 0000000,00000000,000062cf and advertisement 0000000,00000000,000062cf failed: -22
>> Aug 1 22:23:17 tv999996 kern.err kernel: [ 10.914845] ksz8795-switch spi2.0 lan1 (uninitialized): failed to connect to PHY: -EINVAL
>> Aug 1 22:23:17 tv999996 kern.err kernel: [ 10.923052] ksz8795-switch spi2.0 lan1 (uninitialized): error -22 setting up PHY for tree 0, switch 0, port 2
>>
>> I found that if I reverted commit 2c709e0bdad4d996ec8925b9ee6d5b97458708f1, "net: dsa: microchip: ksz8795: add phylink support", then it worked properly again. The errors I saw were due to the checks in ksz8_validate() that were added in the above commit.
> Could somebody please take a look, especially if you're among the main
> recipients of this mail and not just CCed?
>
> Anyway, to ensure this is not forgotten I'll add it to the Linux kernel
> regression tracking bot:
>
> #regzbot introduced: 2c709e0bdad4d996ec8925b9ee6d5b97458708f1
> https://bugzilla.kernel.org/show_bug.cgi?id=216320
#regzbot fixed-by: 5fbb08eb7f945c7e88
prev parent reply other threads:[~2022-08-23 18:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-17 13:36 Bug 216320 - KSZ8794 operation broken Thorsten Leemhuis
2022-08-17 14:04 ` Vladimir Oltean
2022-08-17 17:12 ` Thorsten Leemhuis
2022-08-23 16:47 ` Thorsten Leemhuis [this message]
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=7c41dd25-8bfa-c7b0-a430-1b115e8ee375@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=linux-kernel@vger.kernel.org \
--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).