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

[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 be enabled, it was actually not on the device itself.

[1] 
https://github.com/openwrt/openwrt/blob/master/target/linux/mvebu/config-5.15#L288


Looking forward to hearing from you,
Josef

On 03. 12. 22 11:43, Petr Štetiar wrote:
> Stijn Segers <foss at volatilesystems.org> [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], that DUT's LAN network is available
> after 60 seconds.
>
> That availability check is simply doing following for 60 seconds and then gives
> up:
>
>    $ ifstatus lan | jsonfilter -qe "@.up"
>
> It seems, that indeed `br-lan` is broken:
>
> 	root at OpenWrt:/# ifstatus lan
> 	{
> 		"up": false,
> 		"pending": false,
> 		"available": false,
> 		"autostart": true,
> 		"dynamic": false,
> 		"proto": "static",
> 		"device": "br-lan",
> 		"data": {
>
> 		},
> 		"errors": [
> 			{
> 				"subsystem": "interface",
> 				"code": "NO_DEVICE"
> 			}
> 		]
> 	}
>
> More details from the board:
>
> 	root at OpenWrt:/# ubus call system board
> 	{
> 		"kernel": "5.15.80",
> 		"hostname": "OpenWrt",
> 		"system": "ARMv7 Processor rev 1 (v7l)",
> 		"model": "Turris Omnia",
> 		"board_name": "cznic,turris-omnia",
> 		"rootfs_type": "initramfs",
> 		"release": {
> 			"distribution": "OpenWrt",
> 			"version": "SNAPSHOT",
> 			"revision": "r21380-5429411f73",
> 			"target": "mvebu/cortexa9",
> 			"description": "OpenWrt SNAPSHOT r21380-5429411f73"
> 		}
> 	}
>
> 	root at OpenWrt:/# cat /etc/config/network
>
> 	config interface 'loopback'
> 		option device 'lo'
> 		option proto 'static'
> 		option ipaddr '127.0.0.1'
> 		option netmask '255.0.0.0'
>
> 	config globals 'globals'
> 		option ula_prefix 'fdd1:d3b1:e703::/48'
>
> 	config device
> 		option name 'br-lan'
> 		option type 'bridge'
> 		list ports 'lan0'
> 		list ports 'lan1'
> 		list ports 'lan2'
> 		list ports 'lan3'
> 		list ports 'lan4'
>
> 	config interface 'lan'
> 		option device 'br-lan'
> 		option proto 'static'
> 		option ipaddr '192.168.1.1'
> 		option netmask '255.255.255.0'
> 		option ip6assign '60'
>
> 	config interface 'wan'
> 		option device 'eth2'
> 		option proto 'dhcp'
>
> 	config interface 'wan6'
> 		option device 'eth2'
> 		option proto 'dhcpv6'
>
> dmesg is visible in console_turris-omnia-initramfs.txt[2]. It seems really
> like 5.15 regression as:
>
>   21.02 snapshot (5.4.225) https://gitlab.com/ynezz/openwrt-device-runtime-testing/-/jobs/3418109997
>   22.03 snapshot (5.10.156) https://gitlab.com/ynezz/openwrt-device-runtime-testing/-/jobs/3418110000
>
> Passed the tests fine this morning. Re-run of the job failed as well, so it
> should be reproducible issue:
>
>   https://gitlab.com/ynezz/openwrt-device-runtime-testing/-/jobs/3418110003
>
>
> 1. https://gitlab.com/ynezz/openwrt-device-runtime-testing/-/jobs/3418152314
> 2. https://gitlab.com/ynezz/openwrt-device-runtime-testing/-/jobs/3418152314/artifacts/external_file/console_turris-omnia-initramfs.txt
>
>
> Cheers,
>
> Petr
>
> _______________________________________________
> openwrt-devel mailing list
> openwrt-devel at lists.openwrt.org
> https://lists.openwrt.org/mailman/listinfo/openwrt-devel