#19316: ath10k_pci 0000:01:00.0: failed to process fft report: -22
----------------------+------------------------
Reporter: kevindb | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone:
Component: kernel | Version: Trunk
Resolution: | Keywords: ath10k fft
----------------------+------------------------
Comment (by el_goretto):
Replying to [comment:6 michal.kazior@…]:
> Replying to [comment:4 el_goretto]:
> > Yes, that's why the AP is not immediatly picking a channel in "auto"
mode, I understand that. But the channel switch does not happen to be
going through the usual "auto" channel pick as it always picks 36. Wiki
says userland tool should be notified and going against a whole channel
selection process. That's clearly not the case.
>
> This is technically not possible because ACS takes time while DFS and
CSA must be respected immediately.
>
> The fact that it always chooses 36 means you don't have channel 149 (and
following) available. DFS/CSA picks a random channel definition from list
of available non-DFS channels. This is per design and is not inherent to
ath10k but to hostapd.
>
Thank you very much for taking the time to explain all this.
Would be awesome to have this mentionned on the DFS section in OpenWRT
Wiki for people (like me ;)) not knowing much about DFS & co
mecanisms/implementation.
--
Ticket URL: <https://dev.openwrt.org/ticket/19316#comment:7>
OpenWrt <http://openwrt.org>
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
[email protected]
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-tickets
