What's new

Advice needed for DCD tainted log spam please

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

skeal

Part of the Furniture
I get these in my log when using AI-Protect ion and Pixelserv.
Code:
Aug 18 07:26:14 RT-AX88U-E770 kernel: potentially unexpected fatal signal 11.
Aug 18 07:26:14 RT-AX88U-E770 kernel: CPU: 1 PID: 29919 Comm: dcd Tainted: P           O    4.1.51 #2
Aug 18 07:26:14 RT-AX88U-E770 kernel: Hardware name: Broadcom-v8A (DT)
Aug 18 07:26:14 RT-AX88U-E770 kernel: task: ffffffc02feff580 ti: ffffffc02a39c000 task.ti: ffffffc02a39c000
Aug 18 07:26:14 RT-AX88U-E770 kernel: PC is at 0xf6cc639c
Aug 18 07:26:14 RT-AX88U-E770 kernel: LR is at 0x1dce0
Aug 18 07:26:14 RT-AX88U-E770 kernel: pc : [<00000000f6cc639c>] lr : [<000000000001dce0>] pstate: 600f0010
Aug 18 07:26:14 RT-AX88U-E770 kernel: sp : 00000000ff9a23e8
Aug 18 07:26:14 RT-AX88U-E770 kernel: x12: 00000000000a2050
Aug 18 07:26:14 RT-AX88U-E770 kernel: x11: 00000000f5fff024 x10: 00000000000a23c4
Aug 18 07:26:14 RT-AX88U-E770 kernel: x9 : 00000000f5fff678 x8 : 00000000000a287c
Aug 18 07:26:14 RT-AX88U-E770 kernel: x7 : 00000000f5fff6b0 x6 : 00000000000a2876
Aug 18 07:26:14 RT-AX88U-E770 kernel: x5 : 0000000000000000 x4 : 00000000f5fff65c
Aug 18 07:26:14 RT-AX88U-E770 kernel: x3 : 0000000000000000 x2 : 00000000ff9a23c4
Aug 18 07:26:14 RT-AX88U-E770 kernel: x1 : 000000000007d72a x0 : 0000000000000000
Aug 18 07:38:09 RT-AX88U-E770 kernel: potentially unexpected fatal signal 11.
Aug 18 07:38:09 RT-AX88U-E770 kernel: CPU: 1 PID: 600 Comm: dcd Tainted: P           O    4.1.51 #2
Aug 18 07:38:09 RT-AX88U-E770 kernel: Hardware name: Broadcom-v8A (DT)
Aug 18 07:38:09 RT-AX88U-E770 kernel: task: ffffffc02750b480 ti: ffffffc022b78000 task.ti: ffffffc022b78000
Aug 18 07:38:09 RT-AX88U-E770 kernel: PC is at 0xf712d39c
Aug 18 07:38:09 RT-AX88U-E770 kernel: LR is at 0x1dce0
Aug 18 07:38:09 RT-AX88U-E770 kernel: pc : [<00000000f712d39c>] lr : [<000000000001dce0>] pstate: 600f0010
Aug 18 07:38:09 RT-AX88U-E770 kernel: sp : 00000000ffeec4e8
Aug 18 07:38:09 RT-AX88U-E770 kernel: x12: 00000000000a2050
Aug 18 07:38:09 RT-AX88U-E770 kernel: x11: 00000000f63ff024 x10: 00000000000a23c4
Aug 18 07:38:09 RT-AX88U-E770 kernel: x9 : 00000000f63ff678 x8 : 00000000000a287c
Aug 18 07:38:09 RT-AX88U-E770 kernel: x7 : 00000000f63ff6b0 x6 : 00000000000a2876
Aug 18 07:38:09 RT-AX88U-E770 kernel: x5 : 0000000000000000 x4 : 00000000f63ff65c
Aug 18 07:38:09 RT-AX88U-E770 kernel: x3 : 0000000000000000 x2 : 00000000ffeec4c4
Aug 18 07:38:09 RT-AX88U-E770 kernel: x1 : 000000000007d72a x0 : 0000000000000000
My question is does this hurt the system in anyway? Should the use of both be discouraged? Can someone give me some insight please? I have the crash reports piped through Scribe so it's not hurting my logs but is this okay to do?
 
Bump
 
You get no answers because there are perhaps 100 threads discussing dcd crashes. Yours is 101.

It's a known issue when Diversion with pixelserv-tls is used along with AiProtection or perhaps any other TrendMicro engine related firmware component. TrendMicro's data collection daemon is closed source and no one here can diagnose the problem or find a solution to it.
 
TrendMicro's data collection daemon is closed source and no one here can diagnose the problem or find a solution to it.
And I'm fairly sure Trend Micro are well aware of the multiple dcd crashes that has been happening for years, but visibly they don't care enough to bother addressing them. I suspect many of the causes are tied to something as silly as buffer overruns or lack of input validation before processing data gathered from the system userspace tools.

Is there anyone else than Asus actually using their bwdpi product?
 
I suspect many of the causes are tied to something as silly as buffer overruns or lack of input validation before processing data gathered from the system userspace tools.

I agree - and the sad thing is Trend Micro is a security firm - go figure...
 
Is there anyone else than Asus actually using their bwdpi product?

TP-Link HomeCare


I had an early version of this on C2300 router, the same hardware as AC86U.
 
You get no answers because there are perhaps 100 threads discussing dcd crashes. Yours is 101.

It's a known issue when Diversion with pixelserv-tls is used along with AiProtection or perhaps any other TrendMicro engine related firmware component. TrendMicro's data collection daemon is closed source and no one here can diagnose the problem or find a solution to it.
I get that. I perused them and found no known conclusion to if this is infact harmful. Please community is there anyway to determine if this is bad for the router or even bad for security?
 
Of course, this is bad for security. The exploit just hasn't been discovered/made known yet.

But I don't see how it can be bad for the router (hardware).
 
Of course, this is bad for security. The exploit just hasn't been discovered/made known yet.

But I don't see how it can be bad for the router (hardware).
Thank you sir, I respect your knowledge in this situation.
 
I perused them and found no known conclusion to if this is infact harmful.

No idea how harmful it is, but if it makes you feel better, here you go - stock Asuswrt on AX86U:

Code:
Aug 16 21:43:51 kernel: CPU: 1 PID: 14428 Comm: dcd Tainted: P           O    4.1.52 #2
Aug 16 21:43:51 kernel: Hardware name: Broadcom-v8A (DT)
Aug 16 21:43:51 kernel: task: ffffffc0226981c0 ti: ffffffc01fbe8000 task.ti: ffffffc01fbe8000
Aug 16 21:43:51 kernel: PC is at 0x29d34
Aug 16 21:43:51 kernel: LR is at 0x29fb4
Aug 16 21:43:51 kernel: pc : [<0000000000029d34>] lr : [<0000000000029fb4>] pstate: 200f0010
Aug 16 21:43:51 kernel: sp : 00000000ffa43160
Aug 16 21:43:51 kernel: x12: 00000000000a211c
Aug 16 21:43:51 kernel: x11: 0000000000081d6c x10: 000000000000004c
Aug 16 21:43:51 kernel: x9 : 0000000000000003 x8 : 000000000000004c
Aug 16 21:43:51 kernel: x7 : 00000000f5bff02c x6 : 0000000000000036
Aug 16 21:43:51 kernel: x5 : 00000000000004b0 x4 : 00000000f5bff08c
Aug 16 21:43:51 kernel: x3 : 0000000000000000 x2 : 000000000000004b
Aug 16 21:43:51 kernel: x1 : 0000000000000010 x0 : 0000000000000000

No 3rd party scripts, obviously. Clean installation of stock Asuswrt on a router basically doing nothing.
 
I get that. I perused them and found no known conclusion to if this is infact harmful. Please community is there anyway to determine if this is bad for the router or even bad for security?
Personally, I just ignore those messages.
 
I’d be interested to hear their take on it.
All I can say is that Asus are already well aware of the issues, but it's not something they can fix. Only Trend Micro can.
 
And I'm fairly sure Trend Micro are well aware of the multiple dcd crashes that has been happening for years, but visibly they don't care enough to bother addressing them. I suspect many of the causes are tied to something as silly as buffer overruns or lack of input validation before processing data gathered from the system userspace tools.

Is there anyone else than Asus actually using their bwdpi product?
Yes I had the same concern on my first Merlin install. Reset and reconfigure and don’t go into AiProtection and you will never see that message again.
 

Latest threads

Sign Up For SNBForums Daily Digest

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