Dynalink DL-WRX36 Askey RT5010W IPQ8072A technical discussion

The last line of output is "S - Core 0 Frequency, 1651 MHz".

@missingcharacter would you please share how you "blindly" recovered your router?

looks like we have the same problem

@QatarMo and @sampson

I already shared it here: Dynalink DL-WRX36 Askey RT5010W IPQ8072A technical discussion - #693 by missingcharacter.

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:

  1. Connect to serial/UART and do your best to confirm keystrokes are sent
  2. Turn the device on
  3. After you see the line
    S - Core 0 Frequency, 1651 MHz
    
    start pressing any key repeatedly for 21 seconds
  4. Get ready you will start typing things blindly now
  5. Type setenv console_unlock 1 press key called Enter
  6. Type saveenv press key called Enter
  7. You are done typing things blindly
  8. Restart device and you should now see output after
    S - Core 0 Frequency, 1651 MHz
    
    when connected to serial/UART
6 Likes

thanks a lot for this,,and i can confirm it works...

2 Likes

@frollic @robimarko @sampson are these instructions good enough to be added to the wiki?

1 Like

they are, was going to link to the post from it.

thank you for putting it together.

EDIT: wiki updated.

4 Likes

@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?

Thanks

1 Like

I have noticed something similar. I first thought that it was the IRQ balancing tries, but it happens also with the standard IRQ (all core0).

I suspect that for me it comes from trying wpa3 with 802.11r. I removed that 802.11r and have been testing stability...

Not yet sure if that helps.

1 Like

Mine are now at 25+ days uptime, with zero issues.
Got 802.11r enabled, no WPA3 though, using hostapd for the roaming.

I am using wpa3 with 802.11s. I've not looked at 802.11r yet.

I'm using multiple VLANs with WPA2 802.11r SSID's for each in a dumb AP set up. So far so good for me.

1 Like

Same for me, VLANs with WPA2 802.11r. I had issues with WPA3 or the WPA3 mixed mode.

1 Like

granted I do not use 802.11r or WPA3, but have not had the issues you’re reporting on my routers. Uptime only impacted when I flash an update.

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?

1 Like

The mesh has nothing to do with WPA3. You can use WPA2 if you want. But at least in the Xiaomi AX3600 I use it with WPA3 without problem.

EDIT: Sorry, I've seen you are right. My mistake. It seems is mandatory.

SNAPSHOT (r22257-166ab6f90e) Date:2023-03-11 05:27:32

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?

At least it's not a soft brick.

Wait for newer snapshot, or hope someone have an older version saved somewhere.

Unless you want to investigate, in that case, start by running logread -f in ssh, and unplug, and reconnect the WAN cable.

Thank you so much.
I have a spare router to use so I will wait for a newer snapshot.
If anyone shares a working snapshot, then I can use that.

@NinjaBreaker can you kindly share the snapshot?
I installed the one for 20230311 and it has failed to work.

Problem is, you don't know how long it'll take for the issue to get fixed (assuming there's an issue to fix), and you're probably prolonging the process, by not helping out.