possible DCD tainted causes?

[ankhazam]

Hey,
short question. I tried to search answers for it in the forum but failed to get a definitive one. So... After Diversion moved to dnsmasq and there is no more pixelserv-tls on the router but when I enabled TrendMicro services I'm still buggered with the dreaded tainted DCD:

Jan 6 23:12:13 router kernel: potentially unexpected fatal signal 11.
Jan 6 23:12:13 router kernel: CPU: 1 PID: 25689 Comm: dcd Tainted: P O 4.1.51 #2
Jan 6 23:12:13 router kernel: Hardware name: Broadcom-v8A (DT)
Jan 6 23:12:13 router kernel: task: ffffffc02fec7540 ti: ffffffc0214f4000 task.ti: ffffffc0214f4000
Jan 6 23:12:13 router kernel: PC is at 0xf6f8039c
Jan 6 23:12:13 router kernel: LR is at 0x1dce0
Jan 6 23:12:13 router kernel: pc : [<00000000f6f8039c>] lr : [<000000000001dce0>] pstate: a0000010
Jan 6 23:12:13 router kernel: sp : 00000000ffeaf5f8
Jan 6 23:12:13 router kernel: x12: 00000000000a2050
Jan 6 23:12:13 router kernel: x11: 00000000f62ff024 x10: 00000000000a2876
Jan 6 23:12:13 router kernel: x9 : 000000000000001c x8 : 00000000000a287c
Jan 6 23:12:13 router kernel: x7 : 000000000000001c x6 : 00000000f62ffd28
Jan 6 23:12:13 router kernel: x5 : 0000000000000000 x4 : 00000000f62ffcc0
Jan 6 23:12:13 router kernel: x3 : 000000000000362f x2 : 0000000080000000
Jan 6 23:12:13 router kernel: x1 : 000000000007d72a x0 : 0000000000000000

which stopped after turning AiProtect off and withdrawing the privacy policy

Jan 6 23:20:56 router kernel: IDPfw: Exit IDPfw
Jan 6 23:20:56 router kernel: mod epilog takes 0 jiffies
Jan 6 23:20:56 router kernel: IDPfw: Exit IDPfw
Jan 6 23:20:56 router kernel: Exit chrdev /dev/idpfw with major 191
Jan 6 23:20:56 router kernel: ** ERROR: [udb_shell_mod_exit:668] Udb static = 0, dynamic = 48

Can you provide with any hints what can also cause the process to crash?

BR,
Ank

EDIT:
@RMerlin My post was moved here but I don't find it as a diversion question... I'm asking as I have removed from the router anything that I knew was related to tainted dcd process and yet it still keeps on showing.

 

[heysoundude]

IIRC, the TL;DR is the problem lies with Asus and TrendMicro and how one implements the other. it's closed source stuff that Merlin can't code around, and in this case causes issues for people choosing to use Merlin's work. which is why turning the TrendMicro stuff off is recommended and use the suite of scripts/apps here to supplant it...which often can be configured to work more efficiently and reliably and definitely more privately