lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <7c41dd25-8bfa-c7b0-a430-1b115e8ee375@leemhuis.info> Date: Tue, 23 Aug 2022 18:47:24 +0200 From: Thorsten Leemhuis <regressions@...mhuis.info> To: "regressions@...ts.linux.dev" <regressions@...ts.linux.dev> Cc: LKML <linux-kernel@...r.kernel.org>, netdev <netdev@...r.kernel.org> Subject: Re: Bug 216320 - KSZ8794 operation broken #forregzbot 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
Powered by blists - more mailing lists