Dynalink DL-WRX36 Askey RT5010W IPQ8072A technical discussion

Yes. Anything specific you need assistance with?

I really have no idea, but I guess that its only important to not move them dynamically but rather distribute them in one go.

A plier to rig the cables together probably enough, but you got yourself a reusable one :slight_smile:

this script from @bitthief works fine for me on the qnap .. note I run the qnap with nss .. I don't have edma irq's

for the dynalink (non nss) i have the below and it works fine as well. But as you say I end up with more load on cpu0

        #assign 4 rx interrupts to each cores
        echo 8 > /proc/irq/50/smp_affinity
        echo 4 > /proc/irq/51/smp_affinity
        echo 2 > /proc/irq/52/smp_affinity
        echo 1 > /proc/irq/53/smp_affinity

        #assign 3 tcl completions to 3 CPUs
        echo 8 > /proc/irq/73/smp_affinity
        echo 2 > /proc/irq/74/smp_affinity
        echo 4 > /proc/irq/75/smp_affinity

I updated today to SNAPSHOT - r22241-acb189179c with the attended sysupgrade and everything is good.

1 Like

3 posts were split to a new topic: Display the CPU temperature

is it possible to unbrick if i get to this massage on serial and no interrupt seem to work

Core 0 Frequency, 1651 MHz
nothing after this and the light on the router is purple

and if there is a way to fix this what is it please

thanks..

Try Dynalink DL-WRX36 Askey RT5010W IPQ8072A technical discussion - #1118 by frollic

cant use that since the router is not booting to anything on serial it just stops at Core 0,,and i cant interrupt have tested more then one uart chip ..

You dont know if it stops, or if the output is suppressed.

Try pressing any key when before you reach the point, and set the two parameters blindly.

How did you end up in this situation, in the 1st place ?

@sampson what was the last output, when uboot printout was disabled ?

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,

since i had uart this is the only thing it posts

Pretty sure you won't see anything, that's kind of the whole point...

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