I'm having these dcd unhandled error repeating everytime

[Matthew Patrick]

I'm on AC86U. Version .19 . Clean install, jffs formatted, wps reset. Without any scripts. And this is kinda spamming my log. Is it normal?

Oct 11 13:21:23 kernel: dcd[17193]: unhandled level 3 translation fault (11) at 0x00000000, esr 0x92000007
Oct 11 13:21:23 kernel: pgd = ffffffc008f4a000
Oct 11 13:21:23 kernel: [00000000] *pgd=000000001e95e003, *pud=000000001e95e003, *pmd=00000000119b3003, *pte=0000000000000000
Oct 11 13:21:23 kernel: CPU: 1 PID: 17193 Comm: dcd Tainted: P O 4.1.27 #2
Oct 11 13:21:23 kernel: Hardware name: Broadcom-v8A (DT)
Oct 11 13:21:23 kernel: task: ffffffc01e86a080 ti: ffffffc008dc0000 task.ti: ffffffc008dc0000
Oct 11 13:21:23 kernel: PC is at 0xf7485f44
Oct 11 13:21:23 kernel: LR is at 0x1dc74
Oct 11 13:21:23 kernel: pc : [<00000000f7485f44>] lr : [<000000000001dc74>] pstate: 600e0010
Oct 11 13:21:23 kernel: sp : 00000000ffc0cec8
Oct 11 13:21:23 kernel: x12: 000000000009ff08
Oct 11 13:21:23 kernel: x11: 00000000f67ff024 x10: 00000000000a02ac
Oct 11 13:21:23 kernel: x9 : 00000000f67ffe98 x8 : 00000000000a0764
Oct 11 13:21:23 kernel: x7 : 00000000f67ffec8 x6 : 00000000000a075e
Oct 11 13:21:23 kernel: x5 : 0000000000000000 x4 : 00000000f67ffe7c
Oct 11 13:21:23 kernel: x3 : 0000000000000000 x2 : 0000000000000000
Oct 11 13:21:23 kernel: x1 : 000000000007c66c x0 : 0000000000000000
Oct 11 13:40:30 kernel: pgd = ffffffc0127a6000
Oct 11 13:40:30 kernel: [00000000] *pgd=0000000009bfd003, *pud=0000000009bfd003, *pmd=000000000c183003, *pte=0000000000000000
Oct 11 13:40:30 kernel: CPU: 1 PID: 20333 Comm: dcd Tainted: P O 4.1.27 #2
Oct 11 13:40:30 kernel: Hardware name: Broadcom-v8A (DT)
Oct 11 13:40:30 kernel: task: ffffffc01241f480 ti: ffffffc01503c000 task.ti: ffffffc01503c000
Oct 11 13:40:30 kernel: PC is at 0xf7191f44
Oct 11 13:40:30 kernel: LR is at 0x1dc74
Oct 11 13:40:30 kernel: pc : [<00000000f7191f44>] lr : [<000000000001dc74>] pstate: 600e0010
Oct 11 13:40:30 kernel: sp : 00000000ffe53aa8
Oct 11 13:40:30 kernel: x12: 000000000009ff08
Oct 11 13:40:30 kernel: x11: 00000000f64ff024 x10: 00000000000a02ac
Oct 11 13:40:30 kernel: x9 : 00000000f64ffe98 x8 : 00000000000a0764
Oct 11 13:40:30 kernel: x7 : 00000000f64ffec8 x6 : 00000000000a075e
Oct 11 13:40:30 kernel: x5 : 0000000000000000 x4 : 00000000f64ffe7c
Oct 11 13:40:30 kernel: x3 : 0000000000000000 x2 : 0000000000000000
Oct 11 13:40:30 kernel: x1 : 000000000007c66c x0 : 0000000000000000

 

[Butterfly Bones]

This is known issues with many posts. It is caused by Trend Micro debug code according to RMerlin, though I cannot find the specific post since SNB will not search for three letter words like "dcd".

Here is a simple workaround.

Script to remove dcd crashes from system log

Finally got tired of seeing them; I have little faith Trend Micro or Asus will correct anytime soon. Add the following line to /jffs/scripts/post-mount cru a dcd_crash "*/10 * * * * /jffs/scripts/rm_dcd_crash /tmp/syslog.log" #remove dcd crash lines from syslog Replace /tmp/syslog.log with...

www.snbforums.com

A more complete way to handle those and many others is with Scribe (syslog-ng) that many of us use to clean these debugging mistakes left in closed source code, or just to allow managing sysylog entries easier. Scribe has a filter built in for the DCD crashes, Scribe is highly recommended!

Scribe - scribe - syslog-ng and logrotate installer

scribe v2.4_3 2020-06-22 scribe is a script that installs syslog-ng and logrotate from Entware. Filters for various common logs are included, and logrotate files to manage those logs. NOTE WELL: Looking at log files to "see if anything is wrong" is counter-productive. Log files are best used...

www.snbforums.com

 

[Matthew Patrick]

Thanks!! I searched and I thought it was fixed. But I guess not? For scribe ways, do you have a tutorial on setting it up to categorize that ? I have tried it before and I have no clue of getting it working. Thank you

 

[Butterfly Bones]

The scribe thread is very complete, the filter files are included and the setup script will install the existing dcd script. Install it and ask questions in that thread for help. Many of us can help get it working, and most of the questions have been answered there so you can search in the thread too.

 

[Ronald Schwerer]

IMO, scrubbing the system log file is not a "work-around". Kinda like sayin we have less Covid19 cases because testing isn't available.
I'd rather leave the logs alone and simply not look at them. Much easier and it will tell you whether it is fixed or still happening. There's already so much useless crap there as to be useless.

 

[Matthew Patrick]

IMO, scrubbing the system log file is not a "work-around". Kinda like sayin we have less Covid19 cases because testing isn't available.
I'd rather leave the logs alone and simply not look at them. Much easier and it will tell you whether it is fixed or still happening. There's already so much useless crap there as to be useless.

I mean yeah. But like id love to try to get it cleaner so it's easier to check. Im prob gonna change the log level tho if this keeps happening since well, it lags my whole chrome page while loading it lol.

 

[Butterfly Bones]

I mean yeah. But like id love to try to get it cleaner so it's easier to check. Im prob gonna change the log level tho if this keeps happening since well, it lags my whole chrome page while loading it lol.

The downside to that is the possibility to miss other critical info that will get hidden. The DCD script removes the entries from syslog, however the Scribe / syslog-ng just moves them to a separate log file (you choose what to remove and what to leave). With the add-on of UIscribe, you can still view all the separate log files and the cleaned up syslog. Win - win!

 

[Matthew Patrick]

The downside to that is the possibility to miss other critical info that will get hidden. The DCD script removes the entries from syslog, however the Scribe / syslog-ng just moves them to a separate log file (you choose what to remove and what to leave). With the add-on of UIscribe, you can still view all the separate log files and the cleaned up syslog. Win - win!

Yeah I'll try Scribe first. Thank you