potentially unexpected fatal signal 11

  • ATTENTION! As of November 1, 2020, you are not able to reply to threads 6 months after the thread is opened if there are more than 500 posts in the thread.
    Threads will not be locked, so posts may still be edited by their authors.
    Just start a new thread on the topic to post if you get an error message when trying to reply to a thread.

Wycleff

Regular Contributor
Hi Guy's,
since the Upgrade to Asus-Merlin 384.19, I'm seeing the following Error in my Log.
Sometimes 2 times in an Hour and I don't know why its appearing.

Little Back history:
Upgraded to an AX-58U several Weeks ago and installed Merlin 384.18. Later Upgraded to 384.19. Then that Error appeared and I did everything from Scratch.
I even did a complete reset with NVRAM Erase via SSH and reverted it back in the GUI to factory default with initializing. Even reformatted the USB (JFFS) and reinstalled everything.
After that, the error did not appear for several Weeks.
But now I changed some Settings regarding Wi-Fi/LAN/DHCP and the Error reappeared again. Very frustrating.

I'm currently running the following Add-ons:
Diversion
Skynet
Flexqos
ntpMerlin

And everything is up to date. Maybe someone has a clue what's triggering this error.

Code:
Sep 20 22:09:08 kernel: potentially unexpected fatal signal 11.
Sep 20 22:09:08 kernel: CPU: 1 PID: 25831 Comm: dcd Tainted: P           O    4.1.52 #1
Sep 20 22:09:08 kernel: Hardware name: Generic DT based system
Sep 20 22:09:08 kernel: task: d2b3b800 ti: c939e000 task.ti: c939e000
Sep 20 22:09:08 kernel: PC is at 0xb6c5b39c
Sep 20 22:09:08 kernel: LR is at 0x1dd14
Sep 20 22:09:08 kernel: pc : [<b6c5b39c>]    lr : [<0001dd14>]    psr: 600f0010
Sep 20 22:09:08 kernel: sp : be97e968  ip : 000a2050  fp : b5cff024
Sep 20 22:09:08 kernel: r10: 000a23c4  r9 : b5cff918  r8 : 000a287c
Sep 20 22:09:08 kernel: r7 : b5cff950  r6 : 000a2876  r5 : 00000000  r4 : b5cff8fc
Sep 20 22:09:08 kernel: r3 : 00000000  r2 : be97e944  r1 : 0007d612  r0 : 00000000
Sep 20 22:09:08 kernel: Flags: nZCv  IRQs on  FIQs on  Mode USER_32  ISA ARM  Segment user
Sep 20 22:09:08 kernel: Control: 10c5387d  Table: 10db004a  DAC: 00000015
Sep 20 22:09:08 kernel: CPU: 1 PID: 25831 Comm: dcd Tainted: P           O    4.1.52 #1
Sep 20 22:09:08 kernel: Hardware name: Generic DT based system
Sep 20 22:09:08 kernel: [<c0026e60>] (unwind_backtrace) from [<c0022c38>] (show_stack+0x10/0x14)
Sep 20 22:09:08 kernel: [<c0022c38>] (show_stack) from [<c045237c>] (dump_stack+0x8c/0xa0)
Sep 20 22:09:08 kernel: [<c045237c>] (dump_stack) from [<c003aad4>] (get_signal+0x490/0x558)
Sep 20 22:09:08 kernel: [<c003aad4>] (get_signal) from [<c00221d0>] (do_signal+0xc8/0x3ac)
Sep 20 22:09:08 kernel: [<c00221d0>] (do_signal) from [<c0022658>] (do_work_pending+0x94/0xa4)
Sep 20 22:09:08 kernel: [<c0022658>] (do_work_pending) from [<c001f4cc>] (work_pending+0xc/0x20)
 

Jeffrey Young

Senior Member
I believe this is related to trend micro and is out of Merlin control.

Do a search for Dcd tainted. Seems to be a well known issue.
 

ARKASHA

Occasional Visitor
Did someone see this error with 386.1?

Code:
Feb  5 18:23:11 kernel: potentially unexpected fatal signal 11.
 

panni

Occasional Visitor
Did someone see this error with 386.1?

Code:
Feb  5 18:23:11 kernel: potentially unexpected fatal signal 11.
I'm seeing this in 386.2 beta 2 (AX-58U):
Mar 22 11:06:52 kernel: potentially unexpected fatal signal 11.
Mar 22 11:06:52 kernel: CPU: 1 PID: 21161 Comm: dcd Tainted: P O 4.1.52 #1
Mar 22 11:06:52 kernel: Hardware name: Generic DT based system
Mar 22 11:06:52 kernel: task: cfa3d000 ti: cf86a000 task.ti: cf86a000
Mar 22 11:06:52 kernel: PC is at 0xb6c8139c
Mar 22 11:06:52 kernel: LR is at 0x1dcd8
Mar 22 11:06:52 kernel: pc : [<b6c8139c>] lr : [<0001dcd8>] psr: 600b0010
Mar 22 11:06:52 kernel: sp : be8e48d8 ip : 000a2050 fp : b5fff024
Mar 22 11:06:52 kernel: r10: 000a23c4 r9 : b5fff940 r8 : 000a287c
Mar 22 11:06:52 kernel: r7 : b5fff978 r6 : 000a2876 r5 : 00000000 r4 : b5fff924
Mar 22 11:06:52 kernel: r3 : 00000000 r2 : be8e48b4 r1 : 0007d726 r0 : 00000000
Mar 22 11:06:52 kernel: Flags: nZCv IRQs on FIQs on Mode USER_32 ISA ARM Segment user
Mar 22 11:06:52 kernel: Control: 10c5387d Table: 0d2e404a DAC: 00000015
Mar 22 11:06:52 kernel: CPU: 1 PID: 21161 Comm: dcd Tainted: P O 4.1.52 #1
Mar 22 11:06:52 kernel: Hardware name: Generic DT based system
Mar 22 11:06:52 kernel: [<c0026fe0>] (unwind_backtrace) from [<c0022c38>] (show_stack+0x10/0x14)
Mar 22 11:06:52 kernel: [<c0022c38>] (show_stack) from [<c044fbf4>] (dump_stack+0x8c/0xa0)
Mar 22 11:06:52 kernel: [<c044fbf4>] (dump_stack) from [<c003ac4c>] (get_signal+0x490/0x558)
Mar 22 11:06:52 kernel: [<c003ac4c>] (get_signal) from [<c00221d0>] (do_signal+0xc8/0x3ac)
Mar 22 11:06:52 kernel: [<c00221d0>] (do_signal) from [<c0022658>] (do_work_pending+0x94/0xa4)
Mar 22 11:06:52 kernel: [<c0022658>] (do_work_pending) from [<c001f4cc>] (work_pending+0xc/0x20)
 

mittar

New Around Here
I have the same errors, RT-AX86U - 386.2 beta3, I disabled AIProtection but the errors remainded:

edit: I found active AIProtection Parental Control so may be it was not disabled as I thought on the end, I am curious if the errors stop.
edit2: I had to use nvram set TM_EULA=0 ... to get the error away, at least I cannot see it anymore

Mar 31 07:54:05 MERLIN kernel: CPU: 1 PID: 7483 Comm: dcd Tainted: P O 4.1.52 #2
Mar 31 07:54:05 MERLIN kernel: Hardware name: Broadcom-v8A (DT)
 
Last edited:

myStar

New Around Here
Same here on a AX86U (Firmware-Version: 386.3_beta2)
Jul 22 08:17:07 AX86U kernel: potentially unexpected fatal signal 11.
Jul 22 08:17:07 AX86U kernel: CPU: 1 PID: 15702 Comm: dcd Tainted: P O 4.1.52 #2
Jul 22 08:17:07 AX86U kernel: Hardware name: Broadcom-v8A (DT)
Jul 22 08:17:07 AX86U kernel: task: ffffffc025c48bc0 ti: ffffffc03e934000 task.ti: ffffffc03e934000
Jul 22 08:17:07 AX86U kernel: PC is at 0xf747a39c
Jul 22 08:17:07 AX86U kernel: LR is at 0x1dd58
Jul 22 08:17:07 AX86U kernel: pc : [<00000000f747a39c>] lr : [<000000000001dd58>] pstate: 600f0010
Jul 22 08:17:07 AX86U kernel: sp : 00000000ffebbaf8
Jul 22 08:17:07 AX86U kernel: x12: 00000000000a2050
Jul 22 08:17:07 AX86U kernel: x11: 00000000f67ff024 x10: 00000000000a23c4
Jul 22 08:17:07 AX86U kernel: x9 : 00000000f67ff8e4 x8 : 00000000000a287c
Jul 22 08:17:07 AX86U kernel: x7 : 00000000f67ff91c x6 : 00000000000a2876
Jul 22 08:17:07 AX86U kernel: x5 : 0000000000000000 x4 : 00000000f67ff8c8
Jul 22 08:17:07 AX86U kernel: x3 : 0000000000000000 x2 : 00000000ffebbad4
Jul 22 08:17:07 AX86U kernel: x1 : 000000000007d652 x0 : 0000000000000000

and this is not a rare one:

tail -n 1000 /opt/var/log/messages | grep fatal
Jul 22 01:09:32 AX86U kernel: potentially unexpected fatal signal 11.
Jul 22 01:36:25 AX86U kernel: potentially unexpected fatal signal 11.
Jul 22 02:07:49 AX86U kernel: potentially unexpected fatal signal 11.
Jul 22 02:23:39 AX86U kernel: potentially unexpected fatal signal 11.
Jul 22 02:47:55 AX86U kernel: potentially unexpected fatal signal 11.
Jul 22 02:48:49 AX86U kernel: potentially unexpected fatal signal 11.
Jul 22 03:10:07 AX86U kernel: potentially unexpected fatal signal 11.
Jul 22 03:19:55 AX86U kernel: potentially unexpected fatal signal 11.
Jul 22 03:25:31 AX86U kernel: potentially unexpected fatal signal 11.
Jul 22 03:50:02 AX86U kernel: potentially unexpected fatal signal 11.
Jul 22 04:13:28 AX86U kernel: potentially unexpected fatal signal 11.
Jul 22 04:39:58 AX86U kernel: potentially unexpected fatal signal 11.
Jul 22 04:42:48 AX86U kernel: potentially unexpected fatal signal 11.
Jul 22 05:05:05 AX86U kernel: potentially unexpected fatal signal 11.
Jul 22 05:35:57 AX86U kernel: potentially unexpected fatal signal 11.
Jul 22 05:41:16 AX86U kernel: potentially unexpected fatal signal 11.
Jul 22 05:51:52 AX86U kernel: potentially unexpected fatal signal 11.
Jul 22 05:56:23 AX86U kernel: potentially unexpected fatal signal 11.
Jul 22 06:16:51 AX86U kernel: potentially unexpected fatal signal 11.
Jul 22 06:19:19 AX86U kernel: potentially unexpected fatal signal 11.
Jul 22 06:36:36 AX86U kernel: potentially unexpected fatal signal 11.
Jul 22 06:43:43 AX86U kernel: potentially unexpected fatal signal 11.
Jul 22 07:12:01 AX86U kernel: potentially unexpected fatal signal 11.
Jul 22 07:40:28 AX86U kernel: potentially unexpected fatal signal 11.
Jul 22 07:47:09 AX86U kernel: potentially unexpected fatal signal 11.
Jul 22 08:12:05 AX86U kernel: potentially unexpected fatal signal 11.
Jul 22 08:17:07 AX86U kernel: potentially unexpected fatal signal 11.
Jul 22 08:37:16 AX86U kernel: potentially unexpected fatal signal 11.
Jul 22 08:57:26 AX86U kernel: potentially unexpected fatal signal 11.
Jul 22 08:59:46 AX86U kernel: potentially unexpected fatal signal 11.

Any Ideas how to fix this? i hope it is not a hardware error?
 

L&LD

Part of the Furniture
It revokes the acceptance of the TrendMicro components.
 

GNUton

Senior Member
Hi there,
This issue seems to affect also my builds on the DSL-AX82U.
nvram set TM_EULA=0 worked out
 

mxoz

Occasional Visitor
Same problem on RT-AX58U / 386.3_2.
"nvram set TM_EUAL=0" didn't help. Getting "potentially unexpected fatal signal 11" every half an hour.

Code:
Aug 15 15:05:45 kernel: potentially unexpected fatal signal 11.
Aug 15 15:05:45 kernel: CPU: 1 PID: 1092 Comm: dcd Tainted: P           O    4.1.52 #1
Aug 15 15:05:45 kernel: Hardware name: Generic DT based system
Aug 15 15:05:45 kernel: task: d6cb0000 ti: d0ea0000 task.ti: d0ea0000
Aug 15 15:05:45 kernel: PC is at 0xb6c6b39c
Aug 15 15:05:45 kernel: LR is at 0x1dcd8
Aug 15 15:05:45 kernel: pc : [<b6c6b39c>]    lr : [<0001dcd8>]    psr: 600b0010
Aug 15 15:05:45 kernel: sp : be84f8f8  ip : 000a2050  fp : b60ff024
Aug 15 15:05:45 kernel: r10: 000a23c4  r9 : b60ff7d8  r8 : 000a287c
Aug 15 15:05:45 kernel: r7 : b60ff810  r6 : 000a2876  r5 : 00000000  r4 : b60ff7bc
Aug 15 15:05:45 kernel: r3 : 00000000  r2 : be84f8d4  r1 : 0007d726  r0 : 00000000
Aug 15 15:05:45 kernel: Flags: nZCv  IRQs on  FIQs on  Mode USER_32  ISA ARM  Segment user
Aug 15 15:05:45 kernel: Control: 10c5387d  Table: 1020004a  DAC: 00000015
Aug 15 15:05:45 kernel: CPU: 1 PID: 1092 Comm: dcd Tainted: P           O    4.1.52 #1
Aug 15 15:05:45 kernel: Hardware name: Generic DT based system
Aug 15 15:05:45 kernel: [<c0026fe0>] (unwind_backtrace) from [<c0022c38>] (show_stack+0x10/0x14)
Aug 15 15:05:45 kernel: [<c0022c38>] (show_stack) from [<c044fc54>] (dump_stack+0x8c/0xa0)
Aug 15 15:05:45 kernel: [<c044fc54>] (dump_stack) from [<c003ac4c>] (get_signal+0x490/0x558)
Aug 15 15:05:45 kernel: [<c003ac4c>] (get_signal) from [<c00221d0>] (do_signal+0xc8/0x3ac)
Aug 15 15:05:45 kernel: [<c00221d0>] (do_signal) from [<c0022658>] (do_work_pending+0x94/0xa4)
Aug 15 15:05:45 kernel: [<c0022658>] (do_work_pending) from [<c001f4cc>] (work_pending+0xc/0x20)

Any other ideas what might be wrong or what may fix it?
 

ColinTaylor

Part of the Furniture
Same problem on RT-AX58U / 386.3_2.
"nvram set TM_EUAL=0" didn't help. Getting "potentially unexpected fatal signal 11" every half an hour.

Code:
Aug 15 15:05:45 kernel: potentially unexpected fatal signal 11.
Aug 15 15:05:45 kernel: CPU: 1 PID: 1092 Comm: dcd Tainted: P           O    4.1.52 #1
Aug 15 15:05:45 kernel: Hardware name: Generic DT based system
Aug 15 15:05:45 kernel: task: d6cb0000 ti: d0ea0000 task.ti: d0ea0000
Aug 15 15:05:45 kernel: PC is at 0xb6c6b39c
Aug 15 15:05:45 kernel: LR is at 0x1dcd8
Aug 15 15:05:45 kernel: pc : [<b6c6b39c>]    lr : [<0001dcd8>]    psr: 600b0010
Aug 15 15:05:45 kernel: sp : be84f8f8  ip : 000a2050  fp : b60ff024
Aug 15 15:05:45 kernel: r10: 000a23c4  r9 : b60ff7d8  r8 : 000a287c
Aug 15 15:05:45 kernel: r7 : b60ff810  r6 : 000a2876  r5 : 00000000  r4 : b60ff7bc
Aug 15 15:05:45 kernel: r3 : 00000000  r2 : be84f8d4  r1 : 0007d726  r0 : 00000000
Aug 15 15:05:45 kernel: Flags: nZCv  IRQs on  FIQs on  Mode USER_32  ISA ARM  Segment user
Aug 15 15:05:45 kernel: Control: 10c5387d  Table: 1020004a  DAC: 00000015
Aug 15 15:05:45 kernel: CPU: 1 PID: 1092 Comm: dcd Tainted: P           O    4.1.52 #1
Aug 15 15:05:45 kernel: Hardware name: Generic DT based system
Aug 15 15:05:45 kernel: [<c0026fe0>] (unwind_backtrace) from [<c0022c38>] (show_stack+0x10/0x14)
Aug 15 15:05:45 kernel: [<c0022c38>] (show_stack) from [<c044fc54>] (dump_stack+0x8c/0xa0)
Aug 15 15:05:45 kernel: [<c044fc54>] (dump_stack) from [<c003ac4c>] (get_signal+0x490/0x558)
Aug 15 15:05:45 kernel: [<c003ac4c>] (get_signal) from [<c00221d0>] (do_signal+0xc8/0x3ac)
Aug 15 15:05:45 kernel: [<c00221d0>] (do_signal) from [<c0022658>] (do_work_pending+0x94/0xa4)
Aug 15 15:05:45 kernel: [<c0022658>] (do_work_pending) from [<c001f4cc>] (work_pending+0xc/0x20)

Any other ideas what might be wrong or what may fix it?
There are hundreds of posts reporting dcd crashes. Try disabling all custom scripts, rebooting the router and seeing if that stops the messages.
 

mxoz

Occasional Visitor
There are hundreds of posts reporting dcd crashes. Try disabling all custom scripts, rebooting the router and seeing if that stops the messages.
By custom scripts you mean things like "Diversion", "Skynet", etc? Well, I can try that suggestion just to see if logs disappear, but I need those scripts all the time so not sure how does it help after that..
 

ColinTaylor

Part of the Furniture
Yes, custom scripts like Diversion. They can be enabled or disabled en mass in the GUI (Administration > System > Enable JFFS custom scripts and configs).

It helps because it's part of the diagnosis process. If you disable the scripts and the problem persists you have eliminated those as the cause of the problem.
 

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