On Fri, Dec 6, 2024 at 10:44 PM KeithG <ys3al35l@xxxxxxxxx> wrote:
>
> On Fri, Dec 6, 2024 at 8:17 AM Arend Van Spriel
> <arend.vanspriel@xxxxxxxxxxxx> wrote:
> >
> > On December 6, 2024 2:29:06 PM KeithG <ys3al35l@xxxxxxxxx> wrote:
> >
> > > I built the kernel and got this:
> > > root@jackrune(rw):~# uname -a
> > > Linux jackrune 6.6.63-v8+ #3 SMP PREEMPT Tue Dec 3 10:09:16 CST 2024
> > > aarch64 GNU/Linux
> > >
> > > I must've done something wrong, though, as I get this:
> > > Dec 06 07:08:10 jackrune kernel: ------------[ cut here ]------------
> > > Dec 06 07:08:10 jackrune kernel: WARNING: CPU: 0 PID: 42 at
> > > net/wireless/nl80211.c:3822 nl80211_send_chandef+0x188/0x1a0
> > > [cfg80211]
> >
> > The warning originates from here:
> >
> > int nl80211_send_chandef(struct sk_buff *msg, const struct
> > cfg80211_chan_def *chandef)
> > {
> > if (WARN_ON(!cfg80211_chandef_valid(chandef)))
> > return -EINVAL;
> >
> > Let me know if next round goes better/same/worse.
> >
> > Regards,
> > Arend
> >
> >
> I re-built the kernel clean (w/o the patch) and I get the fail message:
> Dec 06 22:38:24 jackrune kernel: brcmfmac: brcmf_set_channel: set
> chanspec 0x100c fail, reason -52
> Dec 06 22:38:24 jackrune kernel: brcmfmac: brcmf_set_channel: set
> chanspec 0x100d fail, reason -52
> Dec 06 22:38:24 jackrune kernel: brcmfmac: brcmf_set_channel: set
> chanspec 0x100e fail, reason -52
> Dec 06 22:38:24 jackrune kernel: brcmfmac: brcmf_set_channel: set
> chanspec 0xd022 fail, reason -52
> Dec 06 22:38:24 jackrune kernel: brcmfmac: brcmf_set_channel: set
> chanspec 0xd026 fail, reason -52
> Dec 06 22:38:24 jackrune kernel: brcmfmac: brcmf_set_channel: set
> chanspec 0xd02a fail, reason -52
> Dec 06 22:38:24 jackrune kernel: brcmfmac: brcmf_set_channel: set
> chanspec 0xd02e fail, reason -52
> When I re-build with the patch, I get the kernel panic
> Is there a revised patch?
> Keith
With the newest brcmfmax firmware and teh kernel patch to make WPA3
work on the Pis, I get lost of this in the journal:
Dec 30 23:20:25 runeaudio kernel: brcmfmac: brcmf_set_channel: set
chanspec 0xd022 fail, reason -52
Dec 30 23:20:25 runeaudio kernel: brcmfmac: brcmf_set_channel: set
chanspec 0xd026 fail, reason -52
Dec 30 23:20:25 runeaudio kernel: brcmfmac: brcmf_set_channel: set
chanspec 0xd02a fail, reason -52
Dec 30 23:20:25 runeaudio kernel: brcmfmac: brcmf_set_channel: set
chanspec 0xd02e fail, reason -52
Dec 30 23:20:26 runeaudio kernel: brcmfmac: brcmf_set_channel: set
chanspec 0xd034 fail, reason -52
Dec 30 23:20:26 runeaudio kernel: brcmfmac: brcmf_set_channel: set
chanspec 0xd038 fail, reason -52
Dec 30 23:20:26 runeaudio kernel: brcmfmac: brcmf_set_channel: set
chanspec 0xd03c fail, reason -52
Dec 30 23:20:26 runeaudio kernel: brcmfmac: brcmf_set_channel: set
chanspec 0xd040 fail, reason -52
Dec 30 23:20:26 runeaudio kernel: brcmfmac: brcmf_set_channel: set
chanspec 0xd064 fail, reason -52
Dec 30 23:20:26 runeaudio kernel: brcmfmac: brcmf_set_channel: set
chanspec 0xd068 fail, reason -52
Dec 30 23:20:26 runeaudio kernel: brcmfmac: brcmf_set_channel: set
chanspec 0xd06c fail, reason -52
Dec 30 23:20:26 runeaudio kernel: brcmfmac: brcmf_set_channel: set
chanspec 0xd070 fail, reason -52
Dec 30 23:20:26 runeaudio kernel: brcmfmac: brcmf_set_channel: set
chanspec 0xd074 fail, reason -52
Dec 30 23:20:26 runeaudio kernel: brcmfmac: brcmf_set_channel: set
chanspec 0xd078 fail, reason -52
Dec 30 23:20:26 runeaudio kernel: brcmfmac: brcmf_set_channel: set
chanspec 0xd07c fail, reason -52
Dec 30 23:20:26 runeaudio kernel: brcmfmac: brcmf_set_channel: set
chanspec 0xd080 fail, reason -52
Dec 30 23:20:26 runeaudio kernel: brcmfmac: brcmf_set_channel: set
chanspec 0xd084 fail, reason -52
Dec 30 23:20:26 runeaudio kernel: brcmfmac: brcmf_set_channel: set
chanspec 0xd088 fail, reason -52
Dec 30 23:20:26 runeaudio kernel: brcmfmac: brcmf_set_channel: set
chanspec 0xd08c fail, reason -52
Dec 30 23:20:26 runeaudio kernel: brcmfmac: brcmf_set_channel: set
chanspec 0xd090 fail, reason -52
I tried the line in /etc/modprobe.d/brcmfmac.conf
brcmfmac feature_disable=0x200000
but do not know what to do with the rest of these. The messages repeat
over and over and fill the log.
it does not seem to affect the function of the wlan as I can still
connect to APs
