e9hack kirjoitti 26.9.2021 klo 15.48:
Am 26.09.2021 um 12:54 schrieb Hannu Nyman:
e9hack kirjoitti 26.9.2021 klo 10.02:
Am 24.09.2021 um 22:04 schrieb e9hack:
In the past (a few days ago), it was possible to disable or shut-down
wifi by introduce the command 'wifi down'. This doesn't work currently.
After some seconds, wifi is start again.
It may be related to a page fault of netifd. Netifd is restart afterwards:
[ 236.658379] do_page_fault(): sending SIGSEGV to netifd for invalid
write access to 77cdd048
[ 236.666942] epc = 77d7ded5 in libubox.so.20210819[77d78000+18000]
[ 236.673212] ra = 77d7dec9 in libubox.so.20210819[77d78000+18000]
This occurs after 'wifi down'.
Wifi coming up again happens also with R7800 (ipq806x, ath10k), master
build from two days ago.
System log shoes wifi goes down, then the whole network stack gets
restarted (?), and finally wifi comes back up.
OpenWrt SNAPSHOT, r17581-2c9a07ed28
-----------------------------------------------------
root@router1:~# wifi down; logread -f
Sun Sep 26 13:42:39 2021 daemon.notice hostapd: Remove interface 'wlan0'
Sun Sep 26 13:42:39 2021 daemon.notice hostapd: wlan0: interface state
ENABLED->DISABLED
Do you see a page fault from netifd in the log? If it does crash, it is
restarted by procd. This does restart the network stack.
I do not see any crash in the logs.
But I do see netifd PID first disappearing from the proccess list and then
re-appearing with a changed PID, so apparently netifd closes/crashes/whatever
and restarts:
root@router1:~# pgrep netifd
8773
root@router1:~# wifi down
root@router1:~# pgrep netifd
root@router1:~# pgrep netifd
root@router1:~# pgrep netifd
18139
_______________________________________________
openwrt-devel mailing list
[email protected]
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
