ath79-generic: Work around boot hang on Unifi AC-Mesh
It looks like boot hangs on an AC-Mesh for unknown reasons. The last message seen on the console is: [ 0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes, linear) But interestingly, it seems like enabling AIO somehow works around this problem. Changing any off the following options seem to have the same effect at the moment for Linux 5.10.160+5.10.161 # CONFIG_KERNEL_AIO is not set # CONFIG_KERNEL_CGROUPS is not set # CONFIG_KERNEL_FANOTIFY is not set # CONFIG_KERNEL_FHANDLE is not set # CONFIG_KERNEL_IO_URING is not set # CONFIG_KERNEL_IPV6_MROUTE is not set # CONFIG_KERNEL_IPV6_SEG6_LWTUNNEL is not set # CONFIG_KERNEL_IP_MROUTE is not set CONFIG_KERNEL_PROC_STRIPPED=y Just enable CONFIG_AIO until the actual problem was fixed. Link: https://github.com/freifunk-gluon/gluon/issues/2784
This commit is contained in:
parent
670da836c7
commit
536c771f3f
@ -1,3 +1,7 @@
|
|||||||
|
-- modify kernel builds slightly to work around a boot hang on various device
|
||||||
|
-- based on the QCA9563 SoC - especially the Unifi AC-* devices
|
||||||
|
config('KERNEL_AIO', true)
|
||||||
|
|
||||||
-- enforce mainline ath10k kmod/firmware over openwrt default ath10k-ct usage
|
-- enforce mainline ath10k kmod/firmware over openwrt default ath10k-ct usage
|
||||||
-- ath10k-ct is unstable/broken with 11s meshing, works only wave2 chipsets
|
-- ath10k-ct is unstable/broken with 11s meshing, works only wave2 chipsets
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user