I've tried pressing in both Windows and Linux, but no go.
I'm not really sure what happened it was all fine when it booted to the uImage.itb and did all the steps; this happened after the reboot test with more than one uart chip, but it still couldn't interrupt,
Thank you for this context. I just recovered my device; I just entered the commands "blindly" by following the timing (someone said it takes 20 seconds for the u-boot menu to show up)
Note: Please read instructions before you attempt them, also, try to be as calm as you can because typing stuff blindly is not fun
The steps are below:
Connect to serial/UART and do your best to confirm keystrokes are sent
Turn the device on
After you see the line
S - Core 0 Frequency, 1651 MHz
start pressing any key repeatedly for 21 seconds
Get ready you will start typing things blindly now
Type setenv console_unlock 1 press key called Enter
Type saveenv press key called Enter
You are done typing things blindly
Restart device and you should now see output after
@robimarko@hnyman I've been experiencing intermittent total wifi failure for a few weeks. Everything works fine for anything from a few hours to over five days, and then bang it's dead.
I'm currently running a build from yesterday (commit: commit 14334c222e3a547db2e644a51c26e09b877d50a4)
I've added the smp_affinity init script referenced elsewhere on this thread, which I understood helped others avoid interrupt rebalancing triggered crashes.
For the first time I've managed to capture the log output at the moment of the crash. Googling the error I found @robimarko discussing the same issue over a year ago:
Sat Mar 11 07:25:58 2023 daemon.notice hostapd: phy1-ap0: AP-STA-POLL-OK 84:cc:a8:9d:25:99
Sat Mar 11 07:28:51 2023 daemon.notice hostapd: phy1-ap1: AP-STA-DISCONNECTED a4:50:46:0f:3c:11
Sat Mar 11 07:28:51 2023 kern.err kernel: [43176.121616] qcom-q6v5-wcss-pil cd00000.q6v5_wcss: fatal error received:
Sat Mar 11 07:28:51 2023 kern.err kernel: [43176.121616] QC Image Version: QC_IMAGE_VERSION_STRING=WLAN.HK.2.5.0.1-01208-QCAHKSWPL_SILICONZ-1
Sat Mar 11 07:28:51 2023 kern.err kernel: [43176.121616] Image Variant : IMAGE_VARIANT_STRING=8074.wlanfw.eval_v2Q
Sat Mar 11 07:28:51 2023 kern.err kernel: [43176.121616]
Sat Mar 11 07:28:51 2023 kern.err kernel: [43176.121616] ar_wal_peer.c:2462 Assertion is_graceful_to_handle failedparam0 :zero, param1 :zero, param2 :zero.
Sat Mar 11 07:28:51 2023 kern.err kernel: [43176.121616] Thread ID : 0x00000060 Thread name : WLAN RT1 Process ID : 0
Sat Mar 11 07:28:51 2023 kern.err kernel: [43176.121616] Register:
Sat Mar 11 07:28:51 2023 kern.err kernel: [43176.121616] SP : 0x4c135128
Sat Mar 11 07:28:51 2023 kern.err kernel: [43176.121616] FP : 0x4c135130
Sat Mar 11 07:28:51 2023 kern.err kernel: [43176.121616] PC : 0x4b195a10
Sat Mar 11 07:28:51 2023 kern.err kernel: [43176.121616] SSR : 0x00000008
Sat Mar 11 07:28:51 2023 kern.err kernel: [43176.121616] BADVA : 0x00020000
Sat Mar 11 07:28:51 2023 kern.err kernel: [43176.121616] LR : 0x4b1951ac
Sat Mar 11 07:28:51 2023 kern.err kernel: [43176.121616]
Sat Mar 11 07:28:51 2023 kern.err kernel: [43176.121616] Stack Dump
Sat Mar 11 07:28:51 2023 kern.err kernel: [43176.121616] from : 0x4c135128
Sat Mar 11 07:28:51 2023 kern.err kernel: [43176.121616] to : 0x4c135980
Sat Mar 11 07:28:51 2023 kern.err kernel: [43176.121616]
Sat Mar 11 07:28:51 2023 kern.err kernel: [43176.170228] remoteproc remoteproc0: crash detected in cd00000.q6v5_wcss: type fatal error
Sat Mar 11 07:28:51 2023 kern.err kernel: [43176.192489] remoteproc remoteproc0: handling crash #1 in cd00000.q6v5_wcss
Sat Mar 11 07:28:52 2023 kern.err kernel: [43176.200657] remoteproc remoteproc0: recovering cd00000.q6v5_wcss
Sat Mar 11 07:28:52 2023 kern.info kernel: [43176.233263] remoteproc remoteproc0: stopped remote processor cd00000.q6v5_wcss
Sat Mar 11 07:28:52 2023 kern.warn kernel: [43176.536121] ath11k c000000.wifi: failed to find peer a4:50:46:0f:3c:11 on vdev 0 after creation
After that I get a string of ath11k c000000.wifi: failed messages and I'm force to reboot.
My google search turned this post up:
I also see that @wrcrooks had the same error in his dmesg output here:
In his case he was experiencing crashes at boot time, whereas I'm running for up to 5 days before a crash. @hnyman at the time asked if he was running VLANs or Batman. I'm running both.
@wrcrooks problem seemed to go away after he rebuilt/simplified his config. Do I have to abandon Batman or VLANs? Is it worth giving ath11k 2.7.0.1 firmware a go, or is that to be avoided?
Getting rid of WPA3 looks problematic for me. I'm using 802.11s to create a mesh, and it seems that 802.11s requires WPA3 (according to luci). I've been running this setup successfully for a long time on Belkin RT3200s.
Is it the case that nobody has good uptimes using 802.11s? How are people with high uptimes creating mesh networks with the Dynalinks?
I have flashed the sysupgrade from this snapshot and my router has ceased to work. The WAN port doesn't seem to work as I cannot ping the gateway IP from inside the router.
Is there a solution/workaround to this?