[FS#4114] R7800 radio0 (5ghz) is locked at 40 or 153 at 80mhz width

OpenWrt Bugs openwrt-bugs at lists.openwrt.org
Thu Oct 28 21:12:44 PDT 2021


THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

A new Flyspray task has been opened.  Details are below. 

User who did this - Anson Liu (ansonl) 

Attached to Project - OpenWrt/LEDE Project
Summary - R7800 radio0 (5ghz) is locked at 40 or 153 at 80mhz width
Task Type - Bug Report
Category - Base system
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Low
Priority - Very Low
Reported Version - Trunk
Due in Version - Undecided
Due Date - Undecided
Details -  - Device problem occurs on Netgear R7800
 - Software versions OpenWRT 21.02.1 r16325-88151b8303
 - Steps to reproduce

1. Set radio0 (5ghz) channel to any channel that is not 40 or 153 at 80mhz width.
2a. If the manual channel selection frequency is within the 80mhz width of channels 40 or 153, radio0 will broadcast a wifi network that is actually at 40 or 153 (according to the Channel Analyzer feature).
2b. If the manual channel selection frequency is outside the above limits, radio0 will be disabled. 
   
I am not sure if this is a hardware limitation of the R7800 or related to DFS but the tested channels should be outside the TDWR frequency range. 

dmesg log with a test of the channel set outside the 80mhz width of 40 and 153 (ex: 60, 116, 144) so the radio is disabled. Then the channel is set to 40/153 and it ends up working. 

[ 2897.661980] br-lan: port 3(wlan0) entered disabled state
[ 2897.664209] device wlan0 left promiscuous mode
[ 2897.666424] br-lan: port 3(wlan0) entered disabled state
[ 2903.621030] ath10k_pci 0000:01:00.0: 10.4 wmi init: vdevs: 16  peers: 48  tid: 96
[ 2903.621056] ath10k_pci 0000:01:00.0: msdu-desc: 2500  skid: 32
[ 2903.703062] ath10k_pci 0000:01:00.0: wmi print 'P 48/48 V 16 K 144 PH 176 T 186  msdu-desc: 2500  sw-crypt: 0 ct-sta: 0'
[ 2903.703912] ath10k_pci 0000:01:00.0: wmi print 'free: 84920 iram: 13156 sram: 11224'
[ 2904.090785] ath10k_pci 0000:01:00.0: rts threshold -1
[ 2904.091643] ath10k_pci 0000:01:00.0: Firmware lacks feature flag indicating a retry limit of > 2 is OK, requested limit: 4
[ 2910.104019] ath10k_pci 0000:01:00.0: 10.4 wmi init: vdevs: 16  peers: 48  tid: 96
[ 2910.104045] ath10k_pci 0000:01:00.0: msdu-desc: 2500  skid: 32
[ 2910.186082] ath10k_pci 0000:01:00.0: wmi print 'P 48/48 V 16 K 144 PH 176 T 186  msdu-desc: 2500  sw-crypt: 0 ct-sta: 0'
[ 2910.186928] ath10k_pci 0000:01:00.0: wmi print 'free: 84920 iram: 13156 sram: 11224'
[ 2910.573428] ath10k_pci 0000:01:00.0: rts threshold -1
[ 2910.573700] ath10k_pci 0000:01:00.0: Firmware lacks feature flag indicating a retry limit of > 2 is OK, requested limit: 4
[ 2910.579716] br-lan: port 3(wlan0) entered blocking state
[ 2910.588492] br-lan: port 3(wlan0) entered disabled state
[ 2910.594228] device wlan0 entered promiscuous mode
[ 2910.920831] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 2910.921053] br-lan: port 3(wlan0) entered blocking state
[ 2910.926269] br-lan: port 3(wlan0) entered forwarding state

 

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=4114

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.



More information about the openwrt-bugs mailing list