Closed kamarya closed 5 years ago
This is interesting: you seem to have hit issue #1988 in a new way, and I REALLY want to get that one closed.
It might be safe to close this as a duplicate of that one, since I am fairly sure that the wifi issue is not related to your broken 64bit dma
Any idea about why the kernel freezes ? and about hostapd
timeout panic message repeating after the freeze?
I am not sure where these come from.
kamarya: The DMA fails 14 seconds after the wifi "cfg80211_connect_result" issue in the above logs, but you suggest that these Warnings happen more often than the "Hung Task." - The "swiotlb buffer is full" message is the one you should focus on, and check in your dmesg that the DMA is being set up properly.
I have built again the kernel with the latest SHA1 9798c94b34db4a32707f7f501616dbcbd088a696 on Aug 21 2019. Broadcom WiFi in AP mode stops working after a while due to the same issue.
https://github.com/raspberrypi/linux/pull/3164 is not merged yet. Can you manually apply https://github.com/raspberrypi/linux/pull/3164/commits/9dfbe9f500e85d2f751a240f6144785f237d795a and https://github.com/raspberrypi/linux/pull/3164/commits/1395119b339e946fb87f4ff9da2c85c15947734d to give it another try?
@yaroslavros after applying the proposed patch in #3164 on top of 9798c94 the issue has not been reproduced yet. The fix looks promising and I will keep testing it.
We should be able to close this issue now that the DMA leaks PR was merged.
System Raspberry Pi 4 B Linux Kernel Branch: 4.19.y Linux Kernel Version: 4.19.58 SHA1 : d5dc848c982dff2e020f294e384447efe6ea6617 Distribution: Yocto Poky (meta-raspberrypi)
Context of the issue
Running hostapd on the on-board WiFi interface as an access point. The AP works fine in the beginning and the traffic passes through. However after a few minutes RPi freezes and I get kernel panics about hostapd (see logs). Before having the panic about hostapd I get these interesting lines:
I also get kernel messages at the boot time complaining about cfg80211 (line 752 in sme.c) This might be related to the fix of @agherzan (see SHA1 above) and it might still need more fixes. I have not tested this with other versions.
Kernel logs
Warning at the boot pointing to
net/wireless/sme.c:752 __cfg80211_connect_result
The same issue with version 4.19.60 (SHA1 20565c94ca877a099a3c9c5fa39a0380f3d16491) and the warning message at the boot.