WARNING: CPU: 2 PID: 1922 at net/wireless/sme.c:752 __cfg80211_connect_result+0x3c0/0x410 [cfg80211]

[HinTak]

This seems to need looking at, from dmesg:

Oct 30 13:38:17 pirecorder kernel: [1399728.779188] brcmfmac: brcmf_update_bss_info: wl dtim_assoc failed (-52)
Oct 30 13:38:17 pirecorder kernel: [1399728.779448] ------------[ cut here ]------------
Oct 30 13:38:17 pirecorder kernel: [1399728.779724] WARNING: CPU: 2 PID: 1922 at net/wireless/sme.c:752 __cfg80211_connect_result+0x3c0/0x410 [cfg80211]
Oct 30 13:38:17 pirecorder kernel: [1399728.779731] Modules linked in: fuse binfmt_misc bnep hci_uart btbcm serdev bluetooth ecdh_generic spidev spi_bcm2835 i2c_dev 8021q garp stp llc evdev brcmfmac
 brcmutil sha256_generic cfg80211 rfkill raspberrypi_hwmon hwmon bcm2835_codec(C) bcm2835_v4l2(C) snd_bcm2835(C) v4l2_mem2mem bcm2835_mmal_vchiq(C) v4l2_common videobuf2_dma_contig videobuf2_vmalloc
 videobuf2_memops videobuf2_v4l2 videobuf2_common i2c_bcm2835 videodev snd_soc_bcm2835_i2s media vc_sm_cma(C) uio_pdrv_genirq uio fixed snd_soc_wm8960(O) snd_soc_ac108(O) snd_soc_seeed_voicecard(O) 
snd_soc_simple_card_utils snd_soc_core snd_compress snd_pcm_dmaengine snd_pcm snd_timer snd ip_tables x_tables ipv6
Oct 30 13:38:17 pirecorder kernel: [1399728.780035] CPU: 2 PID: 1922 Comm: kworker/u8:0 Tainted: G        WC O      4.19.75-v7+ #1270
Oct 30 13:38:17 pirecorder kernel: [1399728.780040] Hardware name: BCM2835
Oct 30 13:38:17 pirecorder kernel: [1399728.780250] Workqueue: cfg80211 cfg80211_event_work [cfg80211]
Oct 30 13:38:17 pirecorder kernel: [1399728.780286] [<80111fcc>] (unwind_backtrace) from [<8010d544>] (show_stack+0x20/0x24)
Oct 30 13:38:17 pirecorder kernel: [1399728.780304] [<8010d544>] (show_stack) from [<80819bc0>] (dump_stack+0xd4/0x118)
Oct 30 13:38:17 pirecorder kernel: [1399728.780323] [<80819bc0>] (dump_stack) from [<80120a88>] (__warn+0x104/0x11c)
Oct 30 13:38:17 pirecorder kernel: [1399728.780340] [<80120a88>] (__warn) from [<80120bd8>] (warn_slowpath_null+0x50/0x58)
Oct 30 13:38:17 pirecorder kernel: [1399728.780543] [<80120bd8>] (warn_slowpath_null) from [<7f3c174c>] (__cfg80211_connect_result+0x3c0/0x410 [cfg80211])
Oct 30 13:38:17 pirecorder kernel: [1399728.780935] [<7f3c174c>] (__cfg80211_connect_result [cfg80211]) from [<7f3913ec>] (cfg80211_process_wdev_events+0x104/0x160 [cfg80211])
Oct 30 13:38:17 pirecorder kernel: [1399728.781322] [<7f3913ec>] (cfg80211_process_wdev_events [cfg80211]) from [<7f391488>] (cfg80211_process_rdev_events+0x40/0x98 [cfg80211])
Oct 30 13:38:17 pirecorder kernel: [1399728.781706] [<7f391488>] (cfg80211_process_rdev_events [cfg80211]) from [<7f38b2d4>] (cfg80211_event_work+0x24/0x2c [cfg80211])
Oct 30 13:38:17 pirecorder kernel: [1399728.781908] [<7f38b2d4>] (cfg80211_event_work [cfg80211]) from [<8013bf64>] (process_one_work+0x170/0x458)
Oct 30 13:38:17 pirecorder kernel: [1399728.781925] [<8013bf64>] (process_one_work) from [<8013c2a8>] (worker_thread+0x5c/0x5a4)
Oct 30 13:38:17 pirecorder kernel: [1399728.781942] [<8013c2a8>] (worker_thread) from [<80142594>] (kthread+0x138/0x168)
Oct 30 13:38:17 pirecorder kernel: [1399728.781959] [<80142594>] (kthread) from [<801010ac>] (ret_from_fork+0x14/0x28)
Oct 30 13:38:17 pirecorder kernel: [1399728.781967] Exception stack(0x98cadfb0 to 0x98cadff8)
Oct 30 13:38:17 pirecorder kernel: [1399728.781977] dfa0:                                     00000000 00000000 00000000 00000000
Oct 30 13:38:17 pirecorder kernel: [1399728.781988] dfc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Oct 30 13:38:17 pirecorder kernel: [1399728.781999] dfe0: 00000000 00000000 00000000 00000000 00000013 00000000
Oct 30 13:38:17 pirecorder kernel: [1399728.782007] ---[ end trace d8e9be4c61d2c574 ]---

[pelwell]

Please give us the usual information:

1. What model of Pi are you using?
2. Which OS/distribution?
3. What was the Pi doing when the problem occurred?
4. How frequently do you see the problem?
5. Can you reproduce it at will, and if so, how?

[HinTak]

I have got a pile of these, seem to start withbrcmfmac: brcmf_update_bss_info: wl dtim_assoc failed (-52) .

1. OF: fdt: Machine model: Raspberry Pi 3 Model B Rev 1.2
2. Raspbian GNU/Linux 10 (buster)
3. Every one of them seems to be led by brcmfmac: brcmf_update_bss_info: wl dtim_assoc failed (-52), according to grep -A 1 bss kern.log*

kern.log:Oct 30 11:45:58 pirecorder kernel: [1392990.038059] brcmfmac: brcmf_update_bss_info: wl dtim_assoc failed (-52)
kern.log-Oct 30 11:45:58 pirecorder kernel: [1392990.038315] ------------[ cut here ]------------
--
kern.log:Oct 30 12:13:51 pirecorder kernel: [1394662.976791] brcmfmac: brcmf_update_bss_info: wl dtim_assoc failed (-52)
kern.log-Oct 30 12:13:51 pirecorder kernel: [1394662.976899] ------------[ cut here ]------------
--
kern.log:Oct 30 12:47:55 pirecorder kernel: [1396707.366019] brcmfmac: brcmf_update_bss_info: wl dtim_assoc failed (-52)
kern.log-Oct 30 12:47:55 pirecorder kernel: [1396707.366277] ------------[ cut here ]------------
--
kern.log:Oct 30 12:58:30 pirecorder kernel: [1397341.528189] brcmfmac: brcmf_update_bss_info: wl dtim_assoc failed (-52)
kern.log-Oct 30 12:58:30 pirecorder kernel: [1397341.528296] ------------[ cut here ]------------
--
kern.log:Oct 30 13:11:52 pirecorder kernel: [1398143.800567] brcmfmac: brcmf_update_bss_info: wl dtim_assoc failed (-52)
kern.log-Oct 30 13:11:52 pirecorder kernel: [1398143.800671] ------------[ cut here ]------------
--
kern.log:Oct 30 13:38:17 pirecorder kernel: [1399728.779188] brcmfmac: brcmf_update_bss_info: wl dtim_assoc failed (-52)
kern.log-Oct 30 13:38:17 pirecorder kernel: [1399728.779448] ------------[ cut here ]------------
--
kern.log:Oct 30 13:51:24 pirecorder kernel: [1400516.057684] brcmfmac: brcmf_update_bss_info: wl dtim_assoc failed (-52)
kern.log-Oct 30 13:51:24 pirecorder kernel: [1400516.057940] ------------[ cut here ]------------
--
kern.log:Oct 30 16:24:08 pirecorder kernel: [1409680.342042] brcmfmac: brcmf_update_bss_info: wl dtim_assoc failed (-52)
kern.log-Oct 30 16:24:08 pirecorder kernel: [1409680.342552] ------------[ cut here ]------------

4. As above. The Pi was up for about 2 weeks continuously, that happened towards the end of the 2 week period. (I needed to reboot for an unrelated reason).

5. No; saw it intermittently; I'll write again if I see them again.

[lategoodbye]

Please provide more information about your Wifi configuration (AP, STA, Adhoc, ...).

[HinTak]

When the message happened, the device was running in STA mode, via something like this:

wpa_passphrase AP_Name password > /tmp/wpa.conf
sudo wpa_supplicant -B  -c /tmp/wpa.conf -i wlan0
sudo dhclient wlan0

[scyto]

I am also getting regular "0x3c0/0x410 [cfg80211]" erros after my pi4 has been running for a while - i.e. i am not doing anything when it stops working, it is in dead of night. messages.log shows multiple, usually causing the pi to dissapear - my APs think that the pi is continuing to attempts to connect (i can see the attempts in a event UI)

Pi4
using WLAN0
rasbian latest from site.
i can't make it happen - just does happen

Nov 10 03:03:54 genmon kernel: [125997.788087] ------------[ cut here ]------------
Nov 10 03:03:54 genmon kernel: [125997.788183] WARNING: CPU: 0 PID: 6804 at net/wireless/sme.c:752 __cfg80211_connect_result+0x3c0/0x410 [cfg80211]
Nov 10 03:03:54 genmon kernel: [125997.788187] Modules linked in: 8021q garp stp llc rtc_ds1307 brcmfmac brcmutil sha256_generic cfg80211 raspberrypi_hwmon hwmon rfkill snd_bcm2835(C) snd_pcm snd_timer snd bcm2835_codec(C) v4l2_mem2mem bcm2835_v4l2(C) bcm2835_mmal_vchiq(C) i2c_bcm2835 videobuf2_dma_contig v4l2_common videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev media vc_sm_cma(C) rpivid_mem uio_pdrv_genirq fixed uio i2c_dev ip_tables x_tables ipv6
Nov 10 03:03:54 genmon kernel: [125997.788333] CPU: 0 PID: 6804 Comm: kworker/u8:2 Tainted: G        WC        4.19.75-v7l+ #1270
Nov 10 03:03:54 genmon kernel: [125997.788336] Hardware name: BCM2835
Nov 10 03:03:54 genmon kernel: [125997.788389] Workqueue: cfg80211 cfg80211_event_work [cfg80211]
Nov 10 03:03:54 genmon kernel: [125997.788410] [<c0212d10>] (unwind_backtrace) from [<c020d530>] (show_stack+0x20/0x24)
Nov 10 03:03:54 genmon kernel: [125997.788418] [<c020d530>] (show_stack) from [<c097fb20>] (dump_stack+0xd4/0x118)
Nov 10 03:03:54 genmon kernel: [125997.788426] [<c097fb20>] (dump_stack) from [<c0222330>] (__warn+0x104/0x11c)
Nov 10 03:03:54 genmon kernel: [125997.788434] [<c0222330>] (__warn) from [<c0222480>] (warn_slowpath_null+0x50/0x58)
Nov 10 03:03:54 genmon kernel: [125997.788489] [<c0222480>] (warn_slowpath_null) from [<bf41f6fc>] (__cfg80211_connect_result+0x3c0/0x410 [cfg80211])
Nov 10 03:03:54 genmon kernel: [125997.788593] [<bf41f6fc>] (__cfg80211_connect_result [cfg80211]) from [<bf3ef39c>] (cfg80211_process_wdev_events+0x104/0x160 [cfg80211])
Nov 10 03:03:54 genmon kernel: [125997.788694] [<bf3ef39c>] (cfg80211_process_wdev_events [cfg80211]) from [<bf3ef438>] (cfg80211_process_rdev_events+0x40/0x98 [cfg80211])
Nov 10 03:03:54 genmon kernel: [125997.788792] [<bf3ef438>] (cfg80211_process_rdev_events [cfg80211]) from [<bf3e92d4>] (cfg80211_event_work+0x24/0x2c [cfg80211])
Nov 10 03:03:54 genmon kernel: [125997.788846] [<bf3e92d4>] (cfg80211_event_work [cfg80211]) from [<c023db40>] (process_one_work+0x170/0x458)
Nov 10 03:03:54 genmon kernel: [125997.788854] [<c023db40>] (process_one_work) from [<c023de84>] (worker_thread+0x5c/0x5a4)
Nov 10 03:03:54 genmon kernel: [125997.788860] [<c023de84>] (worker_thread) from [<c0244170>] (kthread+0x138/0x168)
Nov 10 03:03:54 genmon kernel: [125997.788866] [<c0244170>] (kthread) from [<c02010ac>] (ret_from_fork+0x14/0x28)
Nov 10 03:03:54 genmon kernel: [125997.788870] Exception stack(0xeb15bfb0 to 0xeb15bff8)
Nov 10 03:03:54 genmon kernel: [125997.788874] bfa0:                                     00000000 00000000 00000000 00000000
Nov 10 03:03:54 genmon kernel: [125997.788879] bfc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Nov 10 03:03:54 genmon kernel: [125997.788883] bfe0: 00000000 00000000 00000000 00000000 00000013 00000000
Nov 10 03:03:54 genmon kernel: [125997.788893] ---[ end trace 77c2645e50b9a632 ]---

[scyto]

FYI all my AP equipment is ubiquiti unifi APs of various types fwiw

I note that the Exception stack is identical for both of us with the 0x13 code in the 17th byte)

[scyto]

I have tried different APs and i tried turning off unscheduled power delivery and the feature that encourages devices to connect on 5ghz, that didn't help.

-edit- Turns out uspd was still on, trying again to disable it and disable all other new features.

Is there a way to force the pi4 to only connect on 2.4ghz?

Same result here.
Tried with kernel 4.14 & 4.19.

[scyto]

I have moved my pie onto a separate 2.4ghz SSID operating in 802.11b legacy mode.
Still happening. only time it doesn't drop off the network after an hours is when it is located in the house and connected to my 5ghz SSID.

I only have two settings left to test:

1. disable GTK re-keying
2. disable CCMP (aka switch back to TKIP

I have a 100ft outdoor rate cable coming this week so i can attach in situ and trying doing the trace on the wifi.

[scyto]

@doganmurat what AP WiFi equipment are you using?

I am using a custom built Linux.
Kernel version 4.4.112.

I don’t think it is AP related. It is same as for different APs.
In my case message appears when connecting an AP and when I unplugged device.

Except that it functions normally.

[pelwell]

Interestingly, I've just seen this on 5.4-rc7 on a Pi 4, but so far only once. There were no other obvious symptoms, just an unexpected warning.

[scyto]

Thanks for info, for me when this happens all traffic stops flowing to the pi - whats interesting is it is still associating, i can see it move between APs. I have a long outdoor rated Ethernet cable coming i will use to attach to the device and see if i can get a trace of the issue.

[scyto]

@pelwell ok, ethernet cable attached and i set
root@genmon:~# echo 1 >/sys/kernel/debug/tracing/events/cfg80211/enable
anything else i need to do?

(unfortunately while plugging in the cable i knocked out the power so will need to wait 24 to 48 hours for the repro to happen)