help decifering error in system log RT-ac88U running 386.4

[al cons]

Hello, I have a reoccurring line in the syslog that I don't know if I should be concerned about. Hopefully someone can put my mind at easy or direct me in fixing it. Many thanks!

A-

Jan 25 11:53:41 kernel: dcd/21291: potentially unexpected fatal signal 11.
Jan 25 11:53:41 kernel: Pid: 21291, comm: dcd
Jan 25 11:53:41 kernel: CPU: 0 Tainted: P (2.6.36.4brcmarm #1)
Jan 25 11:53:41 kernel: PC is at 0x2adca444
Jan 25 11:53:41 kernel: LR is at 0x1c2fc
Jan 25 11:53:41 kernel: pc : [<2adca444>] lr : [<0001c2fc>] psr: 20000010
Jan 25 11:53:41 kernel: sp : 7ede7a40 ip : 000a26a0 fp : 7ede7ba4
Jan 25 11:53:41 kernel: r10: 000869ec r9 : 0000dafc r8 : 00000068
Jan 25 11:53:41 kernel: r7 : 000869ec r6 : 00000000 r5 : 7ede7cf4 r4 : 00000000
Jan 25 11:53:41 kernel: r3 : 00000000 r2 : 00000000 r1 : 000869ec r0 : 00000000
Jan 25 11:53:41 kernel: Flags: nzCv IRQs on FIQs on Mode USER_32 ISA ARM Segment user
Jan 25 11:53:41 kernel: Control: 10c53c7d Table: 5119404a DAC: 00000015
Jan 25 11:55:24 rc_service: httpds 423:notify_rc restart_dnsfilter

 

[al cons]

Nothing? Is there anyone that can help?
Can someone tell me I should be concerned, have a bad router, or need to re-flash the firmware?
"kernel: dcd/21291: potentially unexpected fatal signal 11."
and, "kernel: CPU: 0 Tainted: P (2.6.36.4brcmarm #1)"


thanks-

 

[Skiron]

"kernel: CPU: 0 Tainted: P (2.6.36.4brcmarm #1)"

'Tainted' is a flag added to the kernel when it detects a non-main line module added to the kernel build by a third party (i.e. the module isn't part of the official kernel tree). The idea is that if somebody reports a kernel crash to the Linux kernel mailing list with this present, a lot of developers will not help much as they didn't code it and have no way to help debugging it (as they are usually 'closed source'), and will not waste their time or effort trying. They will only help with a 'clean' trusted kernel.

The rest is the crash reported with the kernel stack pointers where the error occurred.

More technical information here:

Tainted kernels — The Linux Kernel documentation

 

[al cons]

"kernel: CPU: 0 Tainted: P (2.6.36.4brcmarm #1)"

'Tainted' is a flag added to the kernel when it detects a non-main line module added to the kernel build by a third party (i.e. the module isn't part of the official kernel tree). The idea is that if somebody reports a kernel crash to the Linux kernel mailing list with this present, a lot of developers will not help much as they didn't code it and have no way to help debugging it (as they are usually 'closed source'), and will not waste their time or effort trying. They will only help with a 'clean' trusted kernel.

The rest is the crash reported with the kernel stack pointers where the error occurred.

More technical information here:

Tainted kernels — The Linux Kernel documentation

Thanks for the response! Would Merlins fw show up as a tainted kernel? Should I be concerned? Should I just do a clean install?

thanks again

 

[ColinTaylor]

This is a very common error that has been reported many times. The dcd process has crashed. A common cause of this is when you are running Diversion with pixelserv enabled. The solution is to uninstall pixelserv.

 

[Skiron]

Thanks for the response! Would Merlins fw show up as a tainted kernel?

And yes to that - the firmware uses 3rd party kernel modules, so the kernel will always be 'tainted'.

 

[Jaime Alvarez]

This is a very common error that has been reported many times. The dcd process has crashed. A common cause of this is when you are running Diversion with pixelserv enabled. The solution is to uninstall pixelserv.

I thought that Diversion required pixelserev to work. Am I missing something?

 

[dave14305]

I thought that Diversion required pixelserev to work. Am I missing something?

Diversion has 2 modes: Lite (without Pixelserv) and Standard (with Pixelserv). So it’s not required.

 

[Jaime Alvarez]

Thanks! I'll look into the Lite mode to learn about it.