Arend Van Spriel <arend.vanspriel@xxxxxxxxxxxx> writes: > On January 13, 2023 2:35:58 PM Kalle Valo <kvalo@xxxxxxxxxx> wrote: > >> Johannes Berg <johannes@xxxxxxxxxxxxxxxx> writes: >> >>>>> [ 104.897615] brcmfmac: cfg80211_set_channel: set chanspec 0x100e fail, >>>>> reason -52 >>> >>> [...] >>> >>>> >>>>> All of these 10 errors are repeated every 60 sec. >>>> >>>> Catching up after the holidays ;-) Above chanspec values are invalid. >>>> 0x100e = channel 14/bw 20MHz. The 'iw list' output shows all these >>>> channels are disabled. So who/what is trying to set these channels. >>>> Scanning sets the channel in firmware. Is this initiated from hostapd? >>> >>> Yeah, what userspace is running here? Looks like cfg80211_set_channel() >>> is only used for survey? >>> >>> Couple of observations on the side: >>> * might be nice to have some "brcm" indication in that name :P >> >> Indeed, having a function cfg80211_set_channel() in brcmfmac/cfg80211.c >> is VERY misleading. I first though that is a cfg80211 function and >> didn't understand Johannes' comment until I started grepping :) Can >> someone fix that, please? > > It is already on your queue for wireless-next. That was the 3rd patch > for which you sent yourself a reminder earlier this week. You > remember? ;-p Heh. No, I don't even try to remember all the patches, there's just too much of them :) But very good that the fix is in queue, thanks! -- https://patchwork.kernel.org/project/linux-wireless/list/ https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
