New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FS#4122 - Enabling WiFi hangs the whole system (both RPi4 and NanoPi R1) #7069
Comments
bittorf: I can confirm this with r18017 on Raspberry Pi Zero W and Kernel 5.10.77, |
wulfy23: also hit this on r17900-e06aaba4e3 @ rpi4 note... the system is not hung... ( although it appears as such )... the terminal is just 'perma-stuck' you can open a new terminal... you can't kill the processes... |
arinc90: Even though the commit fixes the system hangup, SSIDs won't be advertised on my Asus RT-AC88U. Can anyone try this on trunk? |
piotrjurkiewicz: WiFi is still not working on rpi4.
|
piotrjurkiewicz:
Enabling WiFi with
wifi up
blocks all Netlink communication with kernel, effectively hanging the whole system.After issuing
wifi up
command, netifd calls mac80211.sh script, which in turn calliw phy phy0 set distance 0
.812 1 root S 1804 0% 0% /sbin/netifd
1650 812 root S 1972 0% 0% /bin/sh ./mac80211.sh mac80211 setup radio0 {"config":{"path":"platform/soc/fe300000.mmcnr/mmc_hos
1676 1650 root D 1068 0% 0% iw phy phy0 set distance 0
The
iw phy phy0 set distance 0
command gets stuck on disk (kernel) write, the wchan is:nl80211_parse_chandef
Any event or command happening afterwards (like DHCP association or
ip link
command) also get stuck on Netlink read/write, effectively hanging the whole system:1695 1679 root D 1236 0% 0% ip link
I observe the problem on both my machines, RaspberryPi 4 and sunxi friendlyarm_nanopi-r1. The problem is independent from the kernel version used (5.4 or 5.10), because it also happens with sunxi target compiled with KERNEL_PATCHVER:=5.4. I already used 5.10 on RPi4 without the problem around 43f0e38, so it was introduced after that commit.
The text was updated successfully, but these errors were encountered: