[384.11_Alpha - builds] Testing all variants.

[isr25]

Hmmm. Dirty flashed AC86U from .10 to Alpha4. Still receiving dcd taints. Is anyone else having the same problem, or should I reset to defaults?

 

[QuikSilver]

Hmmm. Dirty flashed AC86U from .10 to Alpha4. Still receiving dcd taints. Is anyone else having the same problem, or should I reset to defaults?

Known issue, has to be fixed by Asus not Merlin.

 

[isr25]

Known issue, has to be fixed by Asus not Merlin.

I know it was a known issue, but I thought the latest 45713 firmware fixed it. A few people attested it was fixed in the previous post. In any case, I understand it's an Asus issue, not Merlin. Just wanted to confirm whether Alpha 4 has the latest 45713 and whether other people has the dcd issue fixed.

 

[L&LD]

Hmmm. Dirty flashed AC86U from .10 to Alpha4. Still receiving dcd taints. Is anyone else having the same problem, or should I reset to defaults?

I know it was a known issue, but I thought the latest 45713 firmware fixed it. A few people attested it was fixed in the previous post. In any case, I understand it's an Asus issue, not Merlin. Just wanted to confirm whether Alpha 4 has the latest 45713 and whether other people has the dcd issue fixed.

If the logs don't bother you too much, I would wait for the final and do a full reset then.

For the record, I went from 384.10_2 to Alpha 1, 2, 3 and now 4 with no resets since _2 and they did stop for me on my RT-AC86U.

 

[QuikSilver]

I know it was a known issue, but I thought the latest 45713 firmware fixed it. A few people attested it was fixed in the previous post. In any case, I understand it's an Asus issue, not Merlin. Just wanted to confirm whether Alpha 4 has the latest 45713 and whether other people has the dcd issue fixed.

The "45713 " firmware is done by Asus. Merlin won't be able to implement those changes until they make them public or give him the source code. The only "fix" I know of that Merlin fixed was the rebooting issue that some of us are having where the unit reboots but never comes up without a physical restart.

 

[Andy1932]

Hmmm. Dirty flashed AC86U from .10 to Alpha4. Still receiving dcd taints. Is anyone else having the same problem, or should I reset to defaults?

Maybe a dumb question, but can you confirm the flash to alpha was successful?

 

[L&LD]

The "45713 " firmware is done by Asus. Merlin won't be able to implement those changes until they make them public or give him the source code. The only "fix" I know of that Merlin fixed was the rebooting issue that some of us are having where the unit reboots but never comes up without a physical restart.

I think it is included in Alpha 4 for the RT-AC86U.

https://www.snbforums.com/threads/p...1-with-dns-over-tls.56095/page-20#post-484148

 

[QuikSilver]

I think it is included in Alpha 4 for the RT-AC86U.

https://www.snbforums.com/threads/p...1-with-dns-over-tls.56095/page-20#post-484148

I looked in there before I posted, and looked again when you linked it and dont see a reference to the DCD taints unless they are going under different item??

Edit: It must be under this item. I apologize @isr25 as I searched for DCD taint not the 86u.

fe5e16c169 Merge SDK + binary blobs from 45713 for RT-AC86U

 

[L&LD]

I looked in there before I posted, and looked again when you linked it and dont see a reference to the DCD taints unless they are going under different item??

I can't track down the post for you now (of course!), but I (think I) have seen it confirmed they were fixed in other threads.

 

[QuikSilver]

I can't track down the post for you now (of course!), but I (think I) have seen it confirmed they were fixed in other threads.

I edited my post to show I what I believe it to be it. If its not I shall remove so as to not lead anyone astray.

 

[L&LD]

I edited my post to show I what I believe it to be it. If its not I shall remove so as to not lead anyone astray.

We need to keep each other on the straight and narrow. I'm sure someone with more details will let me know if I'm wrong!

 

[QuikSilver]

We need to keep each other on the straight and narrow. I'm sure someone with more details will let me know if I'm wrong!

It is hard keeping up with every post so I will admit that I haven't read everyone of them and may have missed it, but I try!

 

[QuikSilver]

This is what I found on Asus website for the 86u (45713) released on 4/18/2019 in case anyone is wondering.....

Version 3.0.0.4.384.457132019/04/1857.76 MBytes

ASUS RT-AC86U Firmware version 3.0.0.4.384.45713
Security Fix
- Fixed CVE-2018-20334
- Fixed CVE-2018-20336
- Fixed null pointer issue. Thanks for CodeBreaker of STARLabs’ contribution.
- Fixed AiCloud buffer overflow vulnerability. Thanks for Resecurity International's contribution.

Bug Fix
- Fixed AiMesh LAN IP issue when router using IPv6 WAN.
- Fixed AIMesh connection issues.
- Fixed Network Map related issues.
- Fixed Download Master icon disappear issue.
- Fixed LAN LED not blinking problem.
- Fixed browser no response problem when enabled Traffic analyzer.
- Fixed wireless mac filter input issue.

 

[isr25]

Maybe a dumb question, but can you confirm the flash to alpha was successful?

I think it was successfully flashed, as the firmware version is listed as .11A4. No worries, I'll try to factory reset and all, just wanted to confirm if the 45713 fixed the dcd taints in your cases as mine did not.

Spoiler: dcd taint

Apr 24 22:52:05 kernel: dcd[8123]: unhandled level 3 translation fault (11) at 0x00000000, esr 0x92000007
Apr 24 22:52:05 kernel: pgd = ffffffc009576000
Apr 24 22:52:05 kernel: [00000000] *pgd=000000000a520003, *pud=000000000a520003, *pmd=0000000014245003, *pte=0000000000000000
Apr 24 22:52:05 kernel: CPU: 1 PID: 8123 Comm: dcd Tainted: P           O    4.1.27 #2
Apr 24 22:52:05 kernel: Hardware name: Broadcom-v8A (DT)
Apr 24 22:52:05 kernel: task: ffffffc0150f4040 ti: ffffffc011dc8000 task.ti: ffffffc011dc8000
Apr 24 22:52:05 kernel: PC is at 0xf6fcdf44
Apr 24 22:52:05 kernel: LR is at 0x1dc74
Apr 24 22:52:05 kernel: pc : [<00000000f6fcdf44>] lr : [<000000000001dc74>] pstate: 600e0010
Apr 24 22:52:05 kernel: sp : 00000000fff3efa8
Apr 24 22:52:05 kernel: x12: 000000000009ff08
Apr 24 22:52:05 kernel: x11: 00000000f62ff024 x10: 00000000000a02ac
Apr 24 22:52:05 kernel: x9 : 00000000f62ffc3c x8 : 00000000000a0764
Apr 24 22:52:05 kernel: x7 : 00000000f62ffc6c x6 : 00000000000a075e
Apr 24 22:52:05 kernel: x5 : 0000000000000000 x4 : 00000000f62ffc20
Apr 24 22:52:05 kernel: x3 : 0000000000000000 x2 : 0000000000000000
Apr 24 22:52:05 kernel: x1 : 000000000007c66c x0 : 0000000000000000

 

[L&LD]

View attachment 17197

I think it was successfully flashed, as the firmware version is listed as .11A4. No worries, I'll try to factory reset and all, just wanted to confirm if the 45713 fixed the dcd taints in your cases as mine did not.

Spoiler: dcd taint

Apr 24 22:52:05 kernel: dcd[8123]: unhandled level 3 translation fault (11) at 0x00000000, esr 0x92000007
Apr 24 22:52:05 kernel: pgd = ffffffc009576000
Apr 24 22:52:05 kernel: [00000000] *pgd=000000000a520003, *pud=000000000a520003, *pmd=0000000014245003, *pte=0000000000000000
Apr 24 22:52:05 kernel: CPU: 1 PID: 8123 Comm: dcd Tainted: P           O    4.1.27 #2
Apr 24 22:52:05 kernel: Hardware name: Broadcom-v8A (DT)
Apr 24 22:52:05 kernel: task: ffffffc0150f4040 ti: ffffffc011dc8000 task.ti: ffffffc011dc8000
Apr 24 22:52:05 kernel: PC is at 0xf6fcdf44
Apr 24 22:52:05 kernel: LR is at 0x1dc74
Apr 24 22:52:05 kernel: pc : [<00000000f6fcdf44>] lr : [<000000000001dc74>] pstate: 600e0010
Apr 24 22:52:05 kernel: sp : 00000000fff3efa8
Apr 24 22:52:05 kernel: x12: 000000000009ff08
Apr 24 22:52:05 kernel: x11: 00000000f62ff024 x10: 00000000000a02ac
Apr 24 22:52:05 kernel: x9 : 00000000f62ffc3c x8 : 00000000000a0764
Apr 24 22:52:05 kernel: x7 : 00000000f62ffc6c x6 : 00000000000a075e
Apr 24 22:52:05 kernel: x5 : 0000000000000000 x4 : 00000000f62ffc20
Apr 24 22:52:05 kernel: x3 : 0000000000000000 x2 : 0000000000000000
Apr 24 22:52:05 kernel: x1 : 000000000007c66c x0 : 0000000000000000

I may have to eat my words. I just checked my syslog right now and regardless of what I may have read (or am misremembering) previously, I am seeing a dcd taint fault from yesterday again. 'dcd[17318]: unhandled level 3 translation fault (11) at 0x00000000, esr 0x92000007'.

I don't normally go looking in the log files, but because they didn't jump out at me, I thought they were fixed. Sorry for the misinformation.

Maybe hold off on that reset for now? But I am curious if this issue was fixed and just not listed in the changelog?

 

[Andy1932]

View attachment 17197

I think it was successfully flashed, as the firmware version is listed as .11A4. No worries, I'll try to factory reset and all, just wanted to confirm if the 45713 fixed the dcd taints in your cases as mine did not.

Spoiler: dcd taint

Apr 24 22:52:05 kernel: dcd[8123]: unhandled level 3 translation fault (11) at 0x00000000, esr 0x92000007
Apr 24 22:52:05 kernel: pgd = ffffffc009576000
Apr 24 22:52:05 kernel: [00000000] *pgd=000000000a520003, *pud=000000000a520003, *pmd=0000000014245003, *pte=0000000000000000
Apr 24 22:52:05 kernel: CPU: 1 PID: 8123 Comm: dcd Tainted: P           O    4.1.27 #2
Apr 24 22:52:05 kernel: Hardware name: Broadcom-v8A (DT)
Apr 24 22:52:05 kernel: task: ffffffc0150f4040 ti: ffffffc011dc8000 task.ti: ffffffc011dc8000
Apr 24 22:52:05 kernel: PC is at 0xf6fcdf44
Apr 24 22:52:05 kernel: LR is at 0x1dc74
Apr 24 22:52:05 kernel: pc : [<00000000f6fcdf44>] lr : [<000000000001dc74>] pstate: 600e0010
Apr 24 22:52:05 kernel: sp : 00000000fff3efa8
Apr 24 22:52:05 kernel: x12: 000000000009ff08
Apr 24 22:52:05 kernel: x11: 00000000f62ff024 x10: 00000000000a02ac
Apr 24 22:52:05 kernel: x9 : 00000000f62ffc3c x8 : 00000000000a0764
Apr 24 22:52:05 kernel: x7 : 00000000f62ffc6c x6 : 00000000000a075e
Apr 24 22:52:05 kernel: x5 : 0000000000000000 x4 : 00000000f62ffc20
Apr 24 22:52:05 kernel: x3 : 0000000000000000 x2 : 0000000000000000
Apr 24 22:52:05 kernel: x1 : 000000000007c66c x0 : 0000000000000000

FWIW, I'm running the latest stock fw for 86u and not getting the dcd error.

 

[QuikSilver]

FWIW, I'm running the latest stock fw for 86u and not getting the dcd error.

Interesting....mine still shows in the log running alpha 4. Didnt see anything in the changelogs for merlin or Asus though suggesting they were fixed. All can do is what. Not hurting anything, just annoying to see in the log when searching for something.

 

[L&LD]

FWIW, I'm running the latest stock fw for 86u and not getting the dcd error.

Thank you for confirming what I am sure I've read before.

This is also an example of how fixes are slipped into the firmware, yet the changelogs may not mention the fixes at all.

 

[CriticJay]

We need to keep each other on the straight and narrow. I'm sure someone with more details will let me know if I'm wrong!

Wait, does this mean the GPL sources for 45713 were already released and Merlin's included them in Alpha 4? That's cool, but I was under the impression it always took at least 2 weeks for Asus to release source code

 

[L&LD]

Wait, does this mean the GPL sources for 45713 were already released and Merlin's included them in Alpha 4? That's cool, but I was under the impression it always took at least 2 weeks for Asus to release source code

Yes, they were released and RMerlin has already included them.

No, they release as and when they feel like it.