[Question] kernel: potentially unexpected fatal signal 11 (?!)

sentinelvdx

Very Senior Member
Hi @RMerlin,

Since 386.4 Final I've started seeing this on my logs. Should I worry?

Code:
Jan 10 18:47:07 kernel: potentially unexpected fatal signal 11.
Jan 10 18:47:07 kernel: CPU: 1 PID: 487 Comm: dcd Tainted: P           O    4.1.52 #2
Jan 10 18:47:07 kernel: Hardware name: 94908REF (DT)
Jan 10 18:47:07 kernel: task: ffffffc02fc66b00 ti: ffffffc022ae4000 task.ti: ffffffc022ae4000
Jan 10 18:47:07 kernel: PC is at 0xf735039c
Jan 10 18:47:07 kernel: LR is at 0x1dd58
Jan 10 18:47:07 kernel: pc : [<00000000f735039c>] lr : [<000000000001dd58>] pstate: 600f0010
Jan 10 18:47:07 kernel: sp : 00000000ffa3c548
Jan 10 18:47:07 kernel: x12: 00000000000a2050
Jan 10 18:47:07 kernel: x11: 00000000f65ff024 x10: 00000000000a23c4
Jan 10 18:47:07 kernel: x9 : 00000000f65ff93c x8 : 00000000000a287c
Jan 10 18:47:07 kernel: x7 : 00000000f65ff974 x6 : 00000000000a2876
Jan 10 18:47:07 kernel: x5 : 0000000000000000 x4 : 00000000f65ff920
Jan 10 18:47:07 kernel: x3 : 0000000000000000 x2 : 00000000ffa3c524
Jan 10 18:47:07 kernel: x1 : 000000000007d652 x0 : 0000000000000000
Jan 10 18:56:32 kernel: potentially unexpected fatal signal 11.
Jan 10 18:56:32 kernel: CPU: 1 PID: 4000 Comm: dcd Tainted: P           O    4.1.52 #2
Jan 10 18:56:32 kernel: Hardware name: 94908REF (DT)
Jan 10 18:56:32 kernel: task: ffffffc03253c040 ti: ffffffc02256c000 task.ti: ffffffc02256c000
Jan 10 18:56:32 kernel: PC is at 0xf70ff39c
Jan 10 18:56:32 kernel: LR is at 0x1dd58
Jan 10 18:56:32 kernel: pc : [<00000000f70ff39c>] lr : [<000000000001dd58>] pstate: 600f0010
Jan 10 18:56:32 kernel: sp : 00000000ffd97c58
Jan 10 18:56:32 kernel: x12: 00000000000a2050
Jan 10 18:56:32 kernel: x11: 00000000f63ff024 x10: 00000000000a23c4
Jan 10 18:56:32 kernel: x9 : 00000000f63ff93c x8 : 00000000000a287c
Jan 10 18:56:32 kernel: x7 : 00000000f63ff974 x6 : 00000000000a2876
Jan 10 18:56:32 kernel: x5 : 0000000000000000 x4 : 00000000f63ff920
Jan 10 18:56:32 kernel: x3 : 0000000000000000 x2 : 00000000ffd97c34
Jan 10 18:56:32 kernel: x1 : 000000000007d652 x0 : 0000000000000000
Jan 10 19:06:58 kernel: potentially unexpected fatal signal 11.
Jan 10 19:06:58 kernel: CPU: 1 PID: 6886 Comm: dcd Tainted: P           O    4.1.52 #2
Jan 10 19:06:58 kernel: Hardware name: 94908REF (DT)
Jan 10 19:06:58 kernel: task: ffffffc032bdab00 ti: ffffffc02926c000 task.ti: ffffffc02926c000
Jan 10 19:06:58 kernel: PC is at 0xf748939c
Jan 10 19:06:58 kernel: LR is at 0x1dd58
Jan 10 19:06:58 kernel: pc : [<00000000f748939c>] lr : [<000000000001dd58>] pstate: 600f0010
Jan 10 19:06:58 kernel: sp : 00000000ff9e84a8
Jan 10 19:06:58 kernel: x12: 00000000000a2050
Jan 10 19:06:58 kernel: x11: 00000000f67ff024 x10: 00000000000a23c4
Jan 10 19:06:58 kernel: x9 : 00000000f67ff93c x8 : 00000000000a287c
Jan 10 19:06:58 kernel: x7 : 00000000f67ff974 x6 : 00000000000a2876
Jan 10 19:06:58 kernel: x5 : 0000000000000000 x4 : 00000000f67ff920
Jan 10 19:06:58 kernel: x3 : 0000000000000000 x2 : 00000000ff9e8484
Jan 10 19:06:58 kernel: x1 : 000000000007d652 x0 : 0000000000000000
 

ColinTaylor

Part of the Furniture
The frequently reported "dcd crash". Often caused by an incompatibility with Diversion's Pixelserv. Worried?, that's down to you.
 

JohnDeere

Regular Contributor
Same here on my AX88U 386.4 , I have never seen this before in logs. I have been using the exact same amtm scripts and settings on older Merlin versions on the same AX88U, but this is the first time I notice this.

Jan 18 22:03:58 RT-AX88U kernel ERR: rdpa_cpu_tx_port_enet_lan#213: rdpa_cpu_tx_port_enet_lan failed. rdd_rc=120 tx_rdd_error_count=21505
Jan 18 22:04:48 RT-AX88U kernel potentially unexpected fatal signal 11.
Jan 18 22:04:48 RT-AX88U kernel CPU: 1 PID: 5051 Comm: dcd Tainted: P O 4.1.51 #2
Jan 18 22:04:48 RT-AX88U kernel Hardware name: Broadcom-v8A (DT)
Jan 18 22:04:48 RT-AX88U kernel task: ffffffc024360040 ti: ffffffc028208000 task.ti: ffffffc028208000
Jan 18 22:04:48 RT-AX88U kernel PC is at 0xf6f1d39c
Jan 18 22:04:48 RT-AX88U kernel LR is at 0x1dd14
Jan 18 22:04:48 RT-AX88U kernel pc : [<00000000f6f1d39c>] lr : [<000000000001dd14>] pstate: 600f0010
Jan 18 22:04:48 RT-AX88U kernel sp : 00000000ffb1af58
Jan 18 22:04:48 RT-AX88U kernel x12: 00000000000a2050
Jan 18 22:04:48 RT-AX88U kernel x11: 00000000f61ff024 x10: 00000000000a23c4
Jan 18 22:04:48 RT-AX88U kernel x9 : 00000000f61ff814 x8 : 00000000000a287c
Jan 18 22:04:48 RT-AX88U kernel x7 : 00000000f61ff84c x6 : 00000000000a2876
Jan 18 22:04:48 RT-AX88U kernel x5 : 0000000000000000 x4 : 00000000f61ff7f8
Jan 18 22:04:48 RT-AX88U kernel x3 : 0000000000000000 x2 : 00000000ffb1af34
Jan 18 22:04:48 RT-AX88U kernel x1 : 000000000007d75a x0 : 0000000000000000
Jan 18 22:05:47 RT-AX88U kernel ERR: rdpa_cpu_tx_port_enet_lan#213: rdpa_cpu_tx_port_enet_lan failed. rdd_rc=120 tx_rdd_error_count=22529
Jan 18 22:27:46 RT-AX88U kernel potentially unexpected fatal signal 11.
Jan 18 22:27:46 RT-AX88U kernel CPU: 1 PID: 6156 Comm: dcd Tainted: P O 4.1.51 #2
Jan 18 22:27:46 RT-AX88U kernel Hardware name: Broadcom-v8A (DT)
Jan 18 22:27:46 RT-AX88U kernel task: ffffffc02c616bc0 ti: ffffffc023f10000 task.ti: ffffffc023f10000
Jan 18 22:27:46 RT-AX88U kernel PC is at 0xf731a39c
Jan 18 22:27:46 RT-AX88U kernel LR is at 0x1dd14
Jan 18 22:27:46 RT-AX88U kernel pc : [<00000000f731a39c>] lr : [<000000000001dd14>] pstate: 600f0010
Jan 18 22:27:46 RT-AX88U kernel sp : 00000000ff889e38
Jan 18 22:27:46 RT-AX88U kernel x12: 00000000000a2050
Jan 18 22:27:46 RT-AX88U kernel x11: 00000000f65ff024 x10: 00000000000a23c4
Jan 18 22:27:46 RT-AX88U kernel x9 : 00000000f65ff814 x8 : 00000000000a287c
Jan 18 22:27:46 RT-AX88U kernel x7 : 00000000f65ff84c x6 : 00000000000a2876
Jan 18 22:27:46 RT-AX88U kernel x5 : 0000000000000000 x4 : 00000000f65ff7f8
Jan 18 22:27:46 RT-AX88U kernel x3 : 0000000000000000 x2 : 00000000ff889e14
Jan 18 22:27:46 RT-AX88U kernel x1 : 000000000007d75a x0 : 0000000000000000
 

RMerlin

Asuswrt-Merlin dev
dcd process crash, caused by pixelserv-tls. There's been quite a few posts about this on the forums, the only option right now is to uninstall pixelserv-tls.
 

JohnDeere

Regular Contributor
Thank you very much. I found an option which disables pixelserv, so I disabled it, hoping that it might be enough. I will keep an eye on the logs to see the result.
 

archiel

Senior Member
FWIW, I also had these dcd process crashes after a dirty upgrade (386.3_2 to 386.4). I was using diversion + pixelserv and all Trend MIcro disabled. There were no dcd errors before the upgrade. I then did a full WPS reset and manual rebuild, still with diversion + pixelserv and all Trend MIcro disabled, and the dcd crashes have gone.
 

sentinelvdx

Very Senior Member
FWIW, I also had these dcd process crashes after a dirty upgrade (386.3_2 to 386.4). I was using diversion + pixelserv and all Trend MIcro disabled. There were no dcd errors before the upgrade. I then did a full WPS reset and manual rebuild, still with diversion + pixelserv and all Trend MIcro disabled, and the dcd crashes have gone.
I didn't have the time to do a full reset and reconfigure everything, but probably do it during the weekend.
 

GL_Red

Occasional Visitor
Same dcd issue, diversion lite so no pixelserv, but disabling diversion makes it go away.
 

Similar threads

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