ASUS RT-AC88U Error

fishstix

New Around Here
ASUS RT-AC88U
Firmware Asuswrt Merlin 386.7._2

I keep seeing the following error, could someone help me with what it means, and is it anything I should be worried about?

I am seeing it at least once an hour.

ov 14 18:23:40 kernel: dcd/19077: potentially unexpected fatal signal 11.
Nov 14 18:23:40 kernel: Pid: 19077, comm: dcd
Nov 14 18:23:40 kernel: CPU: 0 Tainted: P (2.6.36.4brcmarm #1)
Nov 14 18:23:40 kernel: PC is at 0x2abf4444
Nov 14 18:23:40 kernel: LR is at 0x1c310
Nov 14 18:23:40 kernel: pc : [<2abf4444>] lr : [<0001c310>] psr: 20000010
Nov 14 18:23:40 kernel: sp : 7e9dca50 ip : 000a26b4 fp : 7e9dcbb4
Nov 14 18:23:40 kernel: r10: 00086a00 r9 : 0000dafc r8 : 00000068
Nov 14 18:23:40 kernel: r7 : 00086a00 r6 : 00000000 r5 : 7e9dcd04 r4 : 00000000
Nov 14 18:23:40 kernel: r3 : 2adf8e6d r2 : 00000000 r1 : 00086a00 r0 : 00000000
Nov 14 18:23:40 kernel: Flags: nzCv IRQs on FIQs on Mode USER_32 ISA ARM Segment user
Nov 14 18:23:40 kernel: Control: 10c53c7d Table: 51af404a DAC: 00000015
Nov 14 18:23:51 dnsmasq-dhcp[3402]: DHCPDISCOVER(br1) 7c:78:b2:9a:84:30

Thank you
 

ColinTaylor

Part of the Furniture
This error has been reported in these forums hundreds of times over many years. There's nothing RMerlin can do about it so ignore it.
 

popxunga

Regular Contributor
This error has been reported in these forums hundreds of times over many years. There's nothing RMerlin can do about it so ignore it.
From a very brief research it looks like that this error occurs while using the Asus firmware as well.
Should this be reported to Asus or to TrendMicro ?

I'm seeing the same regularly on a AC88U running the latest RMerlin firmware 386.7_2 :

Dec 6 22:27:01 kernel: dcd/3019: potentially unexpected fatal signal 11.
Dec 6 22:27:01 kernel: Pid: 3019, comm: dcd
Dec 6 22:27:01 kernel: CPU: 0 Tainted: P (2.6.36.4brcmarm #1)
Dec 6 22:27:01 kernel: PC is at 0x2ae3c444
Dec 6 22:27:01 kernel: LR is at 0x1c310
Dec 6 22:27:01 kernel: pc : [<2ae3c444>] lr : [<0001c310>] psr: 20000010
Dec 6 22:27:01 kernel: sp : 7eaf6b40 ip : 000a26b4 fp : 7eaf6ca4
Dec 6 22:27:01 kernel: r10: 00086a00 r9 : 0000dafc r8 : 00000068
Dec 6 22:27:01 kernel: r7 : 00086a00 r6 : 00000000 r5 : 7eaf6df4 r4 : 00000000
Dec 6 22:27:01 kernel: r3 : 00000000 r2 : 00000000 r1 : 00086a00 r0 : 00000000
Dec 6 22:27:01 kernel: Flags: nzCv IRQs on FIQs on Mode USER_32 ISA ARM Segment user
Dec 6 22:27:01 kernel: Control: 10c53c7d Table: 5417c04a DAC: 00000015
 
Last edited:

ColinTaylor

Part of the Furniture
From a very brief research it looks like that this error occurs while using the Asus firmware as well.
Should this be reported to Asus then ?

I'm seeing the same regularly on a AC88U running latest RMerlin firmware 386.7_2 :
If people are seeing it on stock firmware then they should use the Feedback option to collect the relevant router data and send it to Asus. There's no point trying to report it if you're using Merlin's firmware because it's most often caused by an addon script like Diversion.
 

popxunga

Regular Contributor
If people are seeing it on stock firmware then they should use the Feedback option to collect the relevant router data and send it to Asus. There's no point trying to report it if you're using Merlin's firmware because it's most often caused by an addon script like Diversion.
I'm not using any addon script such as Diversion, etc,
The only script I' using is a self made one for custom DDNS update.
The dcd process is something related with TrendMicro components (Traffic Analyzer, QOS, Web Traffic History, etc,).
I'm using Merlin's firmware and not the Asus stock firmware, but I've found others reporting the same using the stock firmware.
Currently my AC88U is my main production router and so I'm unable to test with the stock one.
 

ColinTaylor

Part of the Furniture
The dcd process is something related with TrendMicro components (Traffic Analyzer, QOS, Web Traffic History, etc,).
I'm using Merlin's firmware and not the Asus stock firmware, but I've found others reporting the same using the stock firmware.
Third party firmware and software is beyond the control and Asus and TrendMicro. That's why RMerlin removed the Feedback form from his firmware. The only way issues like the dcd crash might be fixed is if people running stock firmware provide the feedback data so that Asus can try and recreate the problem on their systems.
 

Similar threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top