Your message dated Thu, 20 Feb 2025 14:02:36 +0100 (CET)
with message-id <[email protected]>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #998173,
regarding linux-image-5.10.0-9-amd64: Permanent blinking of wireless led
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 [email protected]
immediately.)
--
998173: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998173
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: linux-image-5.10.0-9-amd64
Version: 5.10.70-1
Severity: normal
Dear Maintainer,
with the latest kernel version (change from *-8-amd64 to *-9-amd64 and higher),
I discovered an annoying issue.
This issue shows, that the wireless led is permanently blinking, but it should
only blink, when real traffic is
received.
Examination showed, that the permanent blinking is caused by the router (it is
a Fritz!Box), which is permanently
sending brodcast traffic. However, the indication of broadcast traffic with the
led was suppressed in kernels with version -8-amd64 and lower, and only "real"
traffic was indicated by the led.
Behaving this way, the led indication is very useful, as normal traffic will
let the led blink during traffic I know I had initiated (like calling a
website). Permanently blinking showed, something fishy is going on and I should
examine it: Is a download/update running? Is there a large mail coming? Does
someone have access to my system? Is there a bruteforce attack ongoing?
So, this function is really important for me, and I would like to have it back.
At the moment I am staying with kernel *-8-amd64. Please note, I saw this on
kali linux, too.
I believe, this issue is in the atheros module (I am using an AR542x Wireless
card), and the module is ath5.ko.
If this is really an issue in this module, please take a look at the ath9.ko
module, maybe the same issue appears there, too.
It would be very nice, if you could take a look at this. Please feel free, to
ask for more information.
Network dumps or whatever can be delivered, if needed.
Thank you very much for reading this and any help.
Best regards
Hans
-- System Information:
Debian Release: 11.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-8-amd64 (SMP w/2 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_CRAP, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages linux-image-5.10.0-9-amd64 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-9-amd64 recommends:
ii apparmor 2.13.6-10
ii firmware-linux-free 20200122-1
Versions of packages linux-image-5.10.0-9-amd64 suggests:
pn debian-kernel-handbook <none>
ii extlinux 3:6.04~git20190206.bf6db5b4+dfsg1-3+b1
ii grub-pc 2.04-20
pn linux-doc-5.10 <none>
--- End Message ---
--- Begin Message ---
Hi
This bug was filed for a very old kernel or the bug is old itself
without resolution.
If you can reproduce it 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.
Regards,
Salvatore
--- End Message ---
