On Saturday, 22 May 2021 00:46:55 CET Vagrant Cascadian wrote: > Package: src:linux > Version: 5.10.28-1 > File: /boot/vmlinuz-5.10.0-6-armmp-lpae > Control: block 986767 by -1 > > The ethernet bridge fails to work on 5.10.x (also tried 5.10.38-1), > but works fine on 4.19.x from buster. (This was also reported in > https://bugs.debian.org/986767) > > I noticed these messages when booting up: > > [ 6.254047] bcm53xx stmmac-0:1e: failed to register switch: -517 > [ 6.339663] bcm53xx stmmac-0:1e: failed to register switch: -517
The best way to determine what caused the change from working to not working is `git bisect`: https://wiki.debian.org/DebianKernel/GitBisect It's probably possible to speed that process up by narrowing the range to search. Usually the quickest way is to use snapshot.debian.org and use that to retrieve kernels between 4.19 and 5.10 and test with that. I've also made some observations which could also help in narrowing things down. Kernel 5.10 has CONFIG_NET_DSA_TAG_BRCM_COMMON=m while it's absent in 4.19. That setting determines whether `tag_bcrm` gets build. Bug #986767 also seems to indicate that that is a relevant change. It may be that lamobo-r1 needs additional kernel options enabled. It appears that the networking code made a significant change between 4.19 and 5.10 and it _could_ be DSA related. I know OpenWrt is in the process of switching networking to DSA. https://openwrt.org/toh/lamobo/bananapi_r1?s[]=lamobo&s[]=r1 indicates that the device is supported by OpenWrt version 22.03.2. It's probably worth trying their image and see whether it works properly. And then note which kernel they're using. And possibly search and/or ask for help on their forum. https://github.com/openwrt/openwrt/issues/7817 is still open and is titled "sunxi / lamobo-r1: switch not working with kernel 5.4", so their issue tracker may also provide more info/hints. HTH
signature.asc
Description: This is a digitally signed message part.
