Re: LAN bridge is not working with 5.15.80 [Was: Re: [PATCH v2] mvebu: switch default kernel to 5.15]

2022-12-03 Thread Bjørn Mork
"Arnd Bergmann" writes: > On Sat, Dec 3, 2022, at 18:02, Bjørn Mork wrote: > >> Yes, I realize that ALL_KMODS only changes a small subset of symbols >> related to kmod packages. And I'm pretty sure HSR isn't part of that >> set. But I don't think that changes anything. This is a bug waiting to

Re: LAN bridge is not working with 5.15.80 [Was: Re: [PATCH v2] mvebu: switch default kernel to 5.15]

2022-12-03 Thread Arnd Bergmann
On Sat, Dec 3, 2022, at 18:02, Bjørn Mork wrote: > Petr Štetiar writes: > >> No, lets take a look at that PTP_1588_CLOCK_OPTIONAL: >> >> config PTP_1588_CLOCK_OPTIONAL >> tristate >> default y if PTP_1588_CLOCK=n >> default PTP_1588_CLOCK >>

Re: LAN bridge is not working with 5.15.80 [Was: Re: [PATCH v2] mvebu: switch default kernel to 5.15]

2022-12-03 Thread Bjørn Mork
Petr Štetiar writes: > No, lets take a look at that PTP_1588_CLOCK_OPTIONAL: > > config PTP_1588_CLOCK_OPTIONAL > tristate > default y if PTP_1588_CLOCK=n > default PTP_1588_CLOCK > help > Drivers that can optionally us

Re: LAN bridge is not working with 5.15.80 [Was: Re: [PATCH v2] mvebu: switch default kernel to 5.15]

2022-12-03 Thread Petr Štetiar
Bjørn Mork [2022-12-03 15:56:49]: > Petr Štetiar writes: > > > Indeed, it looks like a regression caused by upstream commit e5f31552674e > > ("ethernet: fix PTP_1588_CLOCK dependencies") in conjuction with images > > produced by our buildbots, which use `CONFIG_ALL_KMODS=y` config setting, so >

Re: LAN bridge is not working with 5.15.80 [Was: Re: [PATCH v2] mvebu: switch default kernel to 5.15]

2022-12-03 Thread Bjørn Mork
Petr Štetiar writes: > Indeed, it looks like a regression caused by upstream commit e5f31552674e > ("ethernet: fix PTP_1588_CLOCK dependencies") in conjuction with images > produced by our buildbots, which use `CONFIG_ALL_KMODS=y` config setting, so > it likely makes `PTP_1588_CLOCK=m` and thus `

Re: LAN bridge is not working with 5.15.80 [Was: Re: [PATCH v2] mvebu: switch default kernel to 5.15]

2022-12-03 Thread Petr Štetiar
Bjørn Mork [2022-12-03 15:01:57]: [adding Arnd to the Cc: loop] > Petr Štetiar writes: > > > `CONFIG_NET_DSA_MV88E6XXX=m` so it might be related to initramfs? > > Isn't that a bit strange? I believe it should be built-in. Indeed, it looks like a regression caused by upstream commit e5f31552

Re: LAN bridge is not working with 5.15.80 [Was: Re: [PATCH v2] mvebu: switch default kernel to 5.15]

2022-12-03 Thread Bjørn Mork
Petr Štetiar writes: > `CONFIG_NET_DSA_MV88E6XXX=m` so it might be related to initramfs? Isn't that a bit strange? I believe it should be built-in. Bjørn ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailm

Re: LAN bridge is not working with 5.15.80 [Was: Re: [PATCH v2] mvebu: switch default kernel to 5.15]

2022-12-03 Thread Petr Štetiar
Josef Schlehofer [2022-12-03 13:01:48]: > AFAIK There is a package kmod-ikconfig, which can be installed on the device > to check if the specific kernel option is enabled or not, which would answer > my question. ;-) ah, wasnt aware about that, thanks, so there it says `CONFIG_NET_DSA_MV88E6XXX=

Re: LAN bridge is not working with 5.15.80 [Was: Re: [PATCH v2] mvebu: switch default kernel to 5.15]

2022-12-03 Thread Stefan Kalscheuer via openwrt-devel
The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- Hi, I do run a Turris Omnia with

Re: LAN bridge is not working with 5.15.80 [Was: Re: [PATCH v2] mvebu: switch default kernel to 5.15]

2022-12-03 Thread Josef Schlehofer
On 03. 12. 22 12:56, Petr Štetiar wrote: Josef Schlehofer [2022-12-03 12:20:54]: Hi, the output from ``zcat /proc/config.gz | grep CONFIG_NET_DSA_MV88E6XXX``? we don't ship config in kernels: target/linux/generic/config-5.15:# CONFIG_IKCONFIG_PROC is not set AFAIK There is a package kmod

Re: LAN bridge is not working with 5.15.80 [Was: Re: [PATCH v2] mvebu: switch default kernel to 5.15]

2022-12-03 Thread Petr Štetiar
Stijn Segers [2022-12-03 12:39:23]: Hi, > That was taken from Rui's commit adding 5.15 as a testing kernel for mvebu. well, "Run-tested on the following subtargets:" usually means, that this specific patch was tested on that target. So it is little bit misleading. Cheers, Petr __

Re: LAN bridge is not working with 5.15.80 [Was: Re: [PATCH v2] mvebu: switch default kernel to 5.15]

2022-12-03 Thread Petr Štetiar
Josef Schlehofer [2022-12-03 12:20:54]: Hi, > the output from ``zcat /proc/config.gz | grep CONFIG_NET_DSA_MV88E6XXX``? we don't ship config in kernels: target/linux/generic/config-5.15:# CONFIG_IKCONFIG_PROC is not set > Even though, in the config [1], it seems that it should be enabled, it

Re: LAN bridge is not working with 5.15.80 [Was: Re: [PATCH v2] mvebu: switch default kernel to 5.15]

2022-12-03 Thread Stijn Segers
Hi Petr, Op zaterdag 3 december 2022 om 11:43:32 +01:00:00 schreef Petr Štetiar : Stijn Segers [2022-12-02 13:36:20]: Hi, * cortexa9 (Turris Omnia - 03f41b1eb2f15ab06d5800274be6a67c64e2a629) that is interesting, is the latest snapshot working for you? That was taken from Rui's commit

Re: LAN bridge is not working with 5.15.80 [Was: Re: [PATCH v2] mvebu: switch default kernel to 5.15]

2022-12-03 Thread Josef Schlehofer
Hi Petr, This seems to be the issue which I experienced recently, as I could not find anything related to the switch in your dmesg. Could you please share with me the output from ``zcat /proc/config.gz | grep CONFIG_NET_DSA_MV88E6XXX``? Even though, in the config [1], it seems that it should

LAN bridge is not working with 5.15.80 [Was: Re: [PATCH v2] mvebu: switch default kernel to 5.15]

2022-12-03 Thread Petr Štetiar
Stijn Segers [2022-12-02 13:36:20]: Hi, > * cortexa9 (Turris Omnia - 03f41b1eb2f15ab06d5800274be6a67c64e2a629) that is interesting, is the latest snapshot working for you? I got notified this morning, that Turris Omnia CI job fails[1] as the CI DUT bringup machinery is unable to confirm[2], th