Kernel Panic - not syncing: Attempted to kill init! exitcode=0x0000000b

[Pranay Srivastava]

Hi

On Tuesday, August 16, 2016, shobhit bhadani <shobhit.nitt at gmail.com> wrote:
> Hi,
>
> I am new to kernel.
> What does this issue mean "not syncing: Attempted to kill init! "?
>
> Is this a user space issue?
>
> 17:10:09.0464-04:00 - Kernel panic - not syncing: Attempted to kill init!
exitcode=0x0000000b   // Is this a User-space Issue ?
>

What were you trying to do?

Which version of kernel are you using?

> 17:10:09.0464-04:00 -
>
> 17:10:09.0464-04:00 - [<c001d4a4>] (unwind_backtrace+0x0/0xf8) from
[<c05aaa0c>] (dump_stack+0x20/0x24)
>
> 17:10:09.0474-04:00 - [<c05aaa0c>] (dump_stack+0x20/0x24) from
[<c05ab36c>] (panic+0xa4/0x1f4)
>
> 17:10:09.0474-04:00 - [<c05ab36c>] (panic+0xa4/0x1f4) from [<c0057dbc>]
(do_exit+0x820/0x968)
>

Your rootfs was mounted?

> 17:10:09.0484-04:00 - [<c0057dbc>] (do_exit+0x820/0x968) from
[<c0058f64>] (do_group_exit+0x50/0xc0)
>
> 17:10:09.0494-04:00 - [<c0058f64>] (do_group_exit+0x50/0xc0) from
[<c00680a0>] (get_signal_to_deliver+0x22c/0x608)
>
> 17:10:09.0494-04:00 - [<c00680a0>] (get_signal_to_deliver+0x22c/0x608)
from [<c0018ae8>] (do_signal+0x94/0x4cc)
>
> 17:10:09.0504-04:00 - [<c0018ae8>] (do_signal+0x94/0x4cc) from
[<c0019244>] (do_work_pending+0x8c/0xc4)
>
> 17:10:09.0514-04:00 - [<c0019244>] (do_work_pending+0x8c/0xc4) from
[<c0014798>] (work_pending+0xc/0x20)
>
> 17:10:09.0514-04:00 - CPU0: stopping
>
> 17:10:09.0514-04:00 - [<c001d4a4>] (unwind_backtrace+0x0/0xf8) from
[<c05aaa0c>] (dump_stack+0x20/0x24)
>
> 17:10:09.0524-04:00 - [<c05aaa0c>] (dump_stack+0x20/0x24) from
[<c001b0a0>] (handle_IPI+0x1a8/0x1dc)
>
> 17:10:09.0534-04:00 - [<c001b0a0>] (handle_IPI+0x1a8/0x1dc) from
[<c0008514>] (gic_handle_irq+0x64/0x6c)
>
> 17:10:09.0534-04:00 - [<c0008514>] (gic_handle_irq+0x64/0x6c) from
[<c0014264>] (__irq_svc+0x44/0x7c)      // Looks like this is an GIC
Interrupt.
>
> 17:10:09.0544-04:00 - Exception stack(0xc0891f20 to 0xc0891f68)
>
> 17:10:09.0544-04:00 - 1f20: c0899488 00000000 c0899488 00000000 c0890000
c0890000 c092d7c8 c05bb458
>
> 17:10:09.0554-04:00 - 1f40: c08a0fd0 00000000 c0890000 c0891f74 c0891f68
c0891f68 c0015ab0 c0015ab4
>
> 17:10:09.0554-04:00 - 1f60: 60000013 ffffffff
>
> 17:10:09.0554-04:00 - [<c0014264>] (__irq_svc+0x44/0x7c) from
[<c0015ab4>] (default_idle+0x30/0x4c)
>
> 17:10:09.0564-04:00 - [<c0015ab4>] (default_idle+0x30/0x4c) from
[<c0015e04>] (cpu_idle+0x68/0x128)
>
> 17:10:09.0574-04:00 - [<c0015e04>] (cpu_idle+0x68/0x128) from
[<c05a45cc>] (rest_init+0x7c/0x94)
>
> 17:10:09.0574-04:00 - [<c05a45cc>] (rest_init+0x7c/0x94) from
[<c082d858>] (start_kernel+0x2d0/0x320)
>
> 17:10:19.0604-04:00 - ### [oops_do_dump:65] should be done
>
>
>
> Can anyone help me in interpreting the above logs??
>
>
> Thanks and Regards,
> Shobhit
>

-- 
        ---P.K.S
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20160816/0897e20d/attachment.html