Your message dated Thu, 20 Feb 2025 12:56:30 +0100 (CET)
with message-id <20250220115630.899febe2...@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #954801,
regarding linux-image-5.4.0-4-amd64: Wireless can't follow some AP's frequency
changes in 5 GHz band.
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 ow...@bugs.debian.org
immediately.)
--
954801: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954801
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 5.4.19-1
Severity: normal
Dear Maintainer,
I'm experiencing too frecuent WiFi disconnects because the kernel
can't follow or does not understand some AP's frequency changes in the
5 GHz band because of DFS.
For example:
Mar 23 13:54:13 waterhole wpa_supplicant[557]: wlx8c882bxxxxxx:
CTRL-EVENT-STARTED-CHANNEL-SWITCH freq=5260 ht_enabled=1 ch_offset=1
ch_width=80 MHz cf1=5290 cf2=0
Mar 23 13:54:14 waterhole kernel: [ 8890.628927] wlx8c882bxxxxxx: AP
a0:64:8f:xx:xx:xx tries to chanswitch to same channel, ignore
Mar 23 13:54:14 waterhole kernel: [ 8890.628932] wlx8c882bxxxxxx: AP
VHT information is invalid, disable VHT
Mar 23 13:54:14 waterhole kernel: [ 8890.628937] wlx8c882bxxxxxx: AP
a0:64:8f:xx:xx:xx changed bandwidth, new config is 5260 MHz, width 2
(5270/0 MHz)
Mar 23 13:54:14 waterhole kernel: [ 8890.628939] wlx8c882bxxxxxx: AP
a0:64:8f:xx:xx:xx changed bandwidth in a way we can't support -
disconnect
Mar 23 13:54:14 waterhole kernel: [ 8890.628941] wlx8c882bxxxxxx:
failed to follow AP a0:64:8f:xx:xx:xx bandwidth change, disconnect
Mar 23 13:54:14 waterhole wpa_supplicant[557]: wlx8c882bxxxxxx:
CTRL-EVENT-CHANNEL-SWITCH freq=5260 ht_enabled=1 ch_offset=1
ch_width=80 MHz cf1=5290 cf2=0
Mar 23 13:54:14 waterhole wpa_supplicant[557]: wlx8c882bxxxxxx:
CTRL-EVENT-DISCONNECTED bssid=a0:64:8f:xx:xx:xx reason=3
locally_generated=1
Mar 23 13:54:14 waterhole NetworkManager[537]: <warn>
[1584968054.8423] sup-iface[0x557d8e27e110,wlx8c882bxxxxxx]:
connection disconnected (reason -3)
Mar 23 13:54:14 waterhole NetworkManager[537]: <info>
[1584968054.8484] device (wlx8c882bxxxxxx): supplicant interface
state: completed -> disconnected
Mar 23 13:54:14 waterhole NetworkManager[537]: <info>
[1584968054.9478] device (wlx8c882bxxxxxx): supplicant interface
state: disconnected -> scanning
Frequency changes to a totally different channel seems to work just
fine, but this kind of changes "to the same channel" produces a
disconnect. My Debian workstation seems to be the only device
disconnected with these frequency changes, other devices like phones,
tablets, or chromecast, connected to the same AP in the 5 GHz band
does not get disconnected.
I'm using a dual band MT7612U 802.11ac wireless stick, but I confirmed
the same problem with a dual band RT3572 802.11n wireless stick.
-- Package-specific info:
** Version:
Linux version 5.4.0-4-amd64 (debian-kernel@lists.debian.org) (gcc
version 9.2.1 20200203 (Debian 9.2.1-28)) #1 SMP Debian 5.4.19-1
(2020-02-13)
** Command line:
BOOT_IMAGE=/boot/vmlinuz-5.4.0-4-amd64
root=UUID=ead92695-df4d-4d3a-bcef-821e9595c77b ro quiet
** Network status:
*** IP interfaces and addresses:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: wlx8c882bxxxxxx: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc
noqueue state UP group default qlen 1000
link/ether 8c:88:2b:00:09:64 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.2/24 brd 192.168.1.255 scope global dynamic
noprefixroute wlx8c882bxxxxxx
valid_lft 40493sec preferred_lft 40493sec
inet6 fe80::f538:4992:786:9449/64 scope link noprefixroute
valid_lft forever preferred_lft forever
*** Device statistics:
Inter-| Receive | Transmit
face |bytes packets errs drop fifo frame compressed
multicast|bytes packets errs drop fifo colls carrier compressed
wlx8c882bxxxxxx: 2052858850 1592590 0 23 0 0 0
0 51767728 375986 0 0 0 0 0 0
lo: 556 12 0 0 0 0 0 0
556 12 0 0 0 0 0 0
** USB devices:
Bus 002 Device 002: ID 0e8d:7612 MediaTek Inc. Wireless
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
--- 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 ---