[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#988966: marked as done (/boot/vmlinuz-5.10.0-6-armmp-lpae: lamobo-r1 ethernet/bridge failure)



Your message dated Sat, 22 Mar 2025 14:22:50 +0100 (CET)
with message-id <20250322132250.449EDBE2DE0@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #988966,
regarding /boot/vmlinuz-5.10.0-6-armmp-lpae: lamobo-r1 ethernet/bridge failure
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
988966: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988966
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
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

--- End Message ---
--- Begin Message ---
Hi

This bug was filed for a very old kernel or the bug is old itself without
resolution. We are sorry we were not able to timely deal with this issue.
There are many open bugs for the src:linux package and thus we are closing
older bugs were they look sensible to be closed. For an overview see:
https://bugs.debian.org/src:linux .

If you can reproduce your issue with

- the current version in unstable/testing
- the latest kernel from backports

please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.

Please try to provide as much fresh details including kernel logs where
relevant. In particular were an issue is coupled with specific hardware we
might ask you to do additional debuging on your side as the owner of the
hardware.

Regards,
Salvatore

--- End Message ---

Reply to: