Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #71725 > unrolled thread

Bug#988966: /boot/vmlinuz-5.10.0-6-armmp-lpae: lamobo-r1 ethernet/bridge failure

Back to article view | Back to linux.debian.kernel

Contents

  Bug#988966: /boot/vmlinuz-5.10.0-6-armmp-lpae: lamobo-r1 ethernet/bridge failure Vagrant Cascadian <vagrant@debian.org> - 2021-05-22 01:00 +0200
    Processed: /boot/vmlinuz-5.10.0-6-armmp-lpae: lamobo-r1  ethernet/bridge failure "Debian Bug Tracking System" <owner@bugs.debian.org> - 2021-05-22 01:00 +0200
    Bug#988966: lamobo-r1 ethernet/bridge failure: Bug still exist in Daily images (2022-12-15) Bernhard <bernhard.woerner@posteo.de> - 2022-12-15 10:20 +0100
      Bug#988966: lamobo-r1 ethernet/bridge failure: Bug still exist in Daily images (2022-12-15) Diederik de Haas <didi.debian@cknow.org> - 2022-12-15 11:40 +0100
    Processed: Re: Bug#988966: lamobo-r1 ethernet/bridge failure: Bug  still exist in Daily images (2022-12-15) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2022-12-15 11:40 +0100
    Bug#988966: /boot/vmlinuz-5.10.0-6-armmp-lpae: lamobo-r1 ethernet/bridge failure Diederik de Haas <didi.debian@cknow.org> - 2022-12-15 13:10 +0100
    Bug#988966: /boot/vmlinuz-5.10.0-6-armmp-lpae: lamobo-r1 ethernet/bridge failure "Andrey Jr. Melnikov" <temnota.am@gmail.com> - 2022-12-15 20:00 +0100

#71725 — Bug#988966: /boot/vmlinuz-5.10.0-6-armmp-lpae: lamobo-r1 ethernet/bridge failure

Package: src:linux
Version: 5.10.28-1
Severity: normal
File: /boot/vmlinuz-5.10.0-6-armmp-lpae
X-Debbugs-Cc: vagrant@debian.org
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



-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
Hardware	: Allwinner sun7i (A20) Family
Revision	: 0000
Device Tree model: Lamobo R1

** Network interface configuration:
*** /etc/network/interfaces:

source /etc/network/interfaces.d/*

auto lo
iface lo inet loopback

allow-hotplug eth0
iface eth0 inet dhcp

** PCI devices:

** USB devices:
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


-- System Information:
Debian Release: 11.0
  APT prefers testing-security
  APT policy: (500, 'testing-security'), (500, 'stable-updates'), (500, 'testing'), (500, 'stable'), (1, 'experimental'), (1, 'unstable')
Architecture: armhf (armv7l)

Kernel: Linux 5.10.0-7-armmp-lpae (SMP w/2 CPU threads)
Kernel taint flags: TAINT_CRAP, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages linux-image-5.10.0-6-armmp-lpae depends on:
ii  initramfs-tools [linux-initramfs-tool]  0.140
ii  kmod                                    28-1
ii  linux-base                              4.6

Versions of packages linux-image-5.10.0-6-armmp-lpae recommends:
ii  apparmor             2.13.6-10
ii  firmware-linux-free  20200122-1

Versions of packages linux-image-5.10.0-6-armmp-lpae suggests:
pn  debian-kernel-handbook  <none>
pn  linux-doc-5.10          <none>

Versions of packages linux-image-5.10.0-6-armmp-lpae is related to:
pn  firmware-amd-graphics     <none>
pn  firmware-atheros          <none>
pn  firmware-bnx2             <none>
pn  firmware-bnx2x            <none>
pn  firmware-brcm80211        <none>
pn  firmware-cavium           <none>
pn  firmware-intel-sound      <none>
pn  firmware-intelwimax       <none>
pn  firmware-ipw2x00          <none>
pn  firmware-ivtv             <none>
pn  firmware-iwlwifi          <none>
pn  firmware-libertas         <none>
pn  firmware-linux-nonfree    <none>
pn  firmware-misc-nonfree     <none>
pn  firmware-myricom          <none>
pn  firmware-netxen           <none>
pn  firmware-qlogic           <none>
pn  firmware-realtek          <none>
pn  firmware-samsung          <none>
pn  firmware-siano            <none>
pn  firmware-ti-connectivity  <none>
pn  xen-hypervisor            <none>

-- no debconf information

[toc] | [next] | [standalone]

#71726 — Processed: /boot/vmlinuz-5.10.0-6-armmp-lpae: lamobo-r1 ethernet/bridge failure

Processing control commands:

> block 986767 by -1
Bug #986767 [installation-reports] installation-reports: Bullseye installation on Lamobo-R1
986767 was not blocked by any bugs.
986767 was not blocking any bugs.
Added blocking bug(s) of 986767: 988966

-- 
986767: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986767
988966: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988966
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#77614 — Bug#988966: lamobo-r1 ethernet/bridge failure: Bug still exist in Daily images (2022-12-15)

[Multipart message — attachments visible in raw view] — view raw

Hello Vagrant

Only for your information:

This bug still exist in Daily image from today (2022-12-15).
There is still no network available at Lamobo R1 and the error is:
>> bcm53xx: failed to register switch: -517 <<

Best regards
Bernhard

[toc] | [prev] | [next] | [standalone]

#77617 — Bug#988966: lamobo-r1 ethernet/bridge failure: Bug still exist in Daily images (2022-12-15)

[Multipart message — attachments visible in raw view] — view raw

Control: found -1 6.0.12-1

On Thursday, 15 December 2022 10:09:27 CET Bernhard wrote:
> This bug still exist in Daily image from today (2022-12-15).

That's using the 6.0.0-6-armmp kernel.

[toc] | [prev] | [next] | [standalone]

#77616 — Processed: Re: Bug#988966: lamobo-r1 ethernet/bridge failure: Bug still exist in Daily images (2022-12-15)

Processing control commands:

> found -1 6.0.12-1
Bug #988966 [src:linux] /boot/vmlinuz-5.10.0-6-armmp-lpae: lamobo-r1 ethernet/bridge failure
Marked as found in versions linux/6.0.12-1.

-- 
988966: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988966
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#77621

[Multipart message — attachments visible in raw view] — view raw

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

[toc] | [prev] | [next] | [standalone]

#77623

Source: linux
Followup-For: Bug #988966
X-Debbugs-Cc: temnota.am@gmail.com


Hmm. it's woking as intented with kernel from unstable:

# dmesg | grep -E '(dwmac|bcm5|model)'
[    0.000000] OF: fdt: Machine model: Lamobo R1.1
[   11.746088] sun7i-dwmac 1c50000.ethernet: IRQ eth_wake_irq not found
[   11.755334] sun7i-dwmac 1c50000.ethernet: IRQ eth_lpi not found
[   11.785153] sun7i-dwmac 1c50000.ethernet: PTP uses main clock
[   11.805181] sun7i-dwmac 1c50000.ethernet: Version ID not available
[   11.811698] sun7i-dwmac 1c50000.ethernet: 	DWMAC1000
[   11.816825] sun7i-dwmac 1c50000.ethernet: No HW DMA feature register supported
[   11.824154] sun7i-dwmac 1c50000.ethernet: TX Checksum insertion supported
[   11.831067] sun7i-dwmac 1c50000.ethernet: Normal descriptors
[   11.836812] sun7i-dwmac 1c50000.ethernet: Ring mode enabled
[   12.812030] bcm53xx stmmac-0:1e: found switch: BCM53125, rev 4
[   13.149519] bcm53xx stmmac-0:1e: Using legacy PHYLIB callbacks. Please migrate to PHYLINK!
[   13.181089] bcm53xx stmmac-0:1e: Configured port 8 for rgmii-txid
[   13.199161] bcm53xx stmmac-0:1e lan2 (uninitialized): PHY [dsa-0.0:00] driver [Broadcom BCM53125] (irq=POLL)
[   13.219947] bcm53xx stmmac-0:1e lan3 (uninitialized): PHY [dsa-0.0:01] driver [Broadcom BCM53125] (irq=POLL)
[   13.241375] bcm53xx stmmac-0:1e lan4 (uninitialized): PHY [dsa-0.0:02] driver [Broadcom BCM53125] (irq=POLL)
[   13.262036] bcm53xx stmmac-0:1e wan (uninitialized): PHY [dsa-0.0:03] driver [Broadcom BCM53125] (irq=POLL)
[   13.278601] bcm53xx stmmac-0:1e lan1 (uninitialized): PHY [dsa-0.0:04] driver [Broadcom BCM53125] (irq=POLL)
[   21.348699] sun7i-dwmac 1c50000.ethernet eth0: Register MEM_TYPE_PAGE_POOL RxQ-0
[   21.358952] sun7i-dwmac 1c50000.ethernet eth0: No Safety Features support found
[   21.366375] sun7i-dwmac 1c50000.ethernet eth0: RX IPC Checksum Offload disabled
[   21.373731] sun7i-dwmac 1c50000.ethernet eth0: No MAC Management Counters available
[   21.381427] sun7i-dwmac 1c50000.ethernet eth0: PTP not supported by HW
[   21.391146] sun7i-dwmac 1c50000.ethernet eth0: configuring for fixed/rgmii link mode
[   21.401844] sun7i-dwmac 1c50000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
[   21.428685] bcm53xx stmmac-0:1e lan1: configuring for phy/gmii link mode
[   21.437145] bcm53xx stmmac-0:1e lan1: Link is Up - 1Gbps/Full - flow control off
[   21.520381] bcm53xx stmmac-0:1e lan2: configuring for phy/gmii link mode
[   21.632977] bcm53xx stmmac-0:1e lan3: configuring for phy/gmii link mode
[   21.748557] bcm53xx stmmac-0:1e lan4: configuring for phy/gmii link mode
[   21.758708] bcm53xx stmmac-0:1e lan4: Link is Up - 100Mbps/Full - flow control off
[   27.067850] bcm53xx stmmac-0:1e wan: configuring for phy/gmii link mode
[   27.076441] bcm53xx stmmac-0:1e wan: Link is Up - 100Mbps/Full - flow control off

# bridge link
3: lan2@eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 master br-lan state disabled priority 32 cost 100 
4: lan3@eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 master br-lan state disabled priority 32 cost 100 
5: lan4@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 master br-lan state forwarding priority 32 cost 19 
7: lan1@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 master br-lan state forwarding priority 32 cost 4 

But installer stupidity "enable only one interface" prevent use any port on bcm53xx
switch - master port eth0 MUST BE ACTIVE.

-- System Information:
Debian Release: 11.5
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable'), (400, 'unstable'), (1, 'experimental')
Architecture: armhf (armv7l)

Kernel: Linux 6.0.0-4-armmp-lpae (SMP w/2 CPU threads)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web