Mainline kernel boot issue

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Mainline kernel boot issue

2,440 Views
pietercardoen
Contributor II

Dear

I am currently trying to boot the mainline kernel (4.15) on a custom board. I started from tinyconfig and I am adding all needed features. Until now, I am making quite some progress and when the rootfs init is executed, I get an error:

[    7.071161] random: crng init done
[    7.082314] Bad block table written to 0x00001ffe0000, version 0x01
[    7.089719] Bad block table written to 0x00001ffc0000, version 0x01
[    7.120877] gpmi-nand 1806000.gpmi-nand: driver registered.
[    7.137830] NET: Registered protocol family 10
[    7.152721] Segment Routing with IPv6
[    7.156440] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
[    7.172363] NET: Registered protocol family 17
[    7.192059] Loading compiled-in X.509 certificates
[    7.567751] Freeing unused kernel memory: 1024K
[    7.583212] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004
[    7.583212]
[    7.592389] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004
[    7.592389]

What could be the cause of this error?

Thanks
Pieter

Labels (2)
0 Kudos
Reply
5 Replies

2,000 Views
pietercardoen
Contributor II

Apparently, NEON was not enabled in the kernel configuration which caused this error.

Thanks for the support!

BR

Pieter

0 Kudos
Reply

2,000 Views
igorpadykov
NXP Employee
NXP Employee

Hi Pieter

one can try with nsp bsps described on

i.MX Software|NXP 

for building use Yocto Guide from documentation on that link

Best regards
igor

0 Kudos
Reply

2,000 Views
pietercardoen
Contributor II

Hello

The imx_v6_v7_defconfig is working. However I would like to start from tinyconfig and enable all needed stuff. I enabled some debugging and ended up with this:

[    6.096346] Loading compiled-in X.509 certificates
[    6.145207] Freeing unused kernel memory: 1024K
[    6.152239] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004
[    6.152239]
[    6.161429] CPU: 0 PID: 1 Comm: init Not tainted 4.15.0-10687-ge9e0393-dirty #7
[    6.168759] Hardware name: Freescale i.MX6 Ultralite (Device Tree)
[    6.174959] Backtrace:
[    6.177467] [<c010c4b4>] (dump_backtrace) from [<c010c754>] (show_stack+0x18/0x1c)
[    6.185070]  r7:c0a33ccc r6:600d0093 r5:00000000 r4:c0a33ccc
[    6.190765] [<c010c73c>] (show_stack) from [<c05fd9f4>] (dump_stack+0x88/0xa4)
[    6.198028] [<c05fd96c>] (dump_stack) from [<c0123fbc>] (panic+0xd8/0x270)
[    6.204935]  r9:c49c31c0 r8:de059ed4 r7:de059e48 r6:de059cc4 r5:00000000 r4:c0a39288
[    6.212717] [<c0123ee8>] (panic) from [<c0127440>] (do_exit+0xa8c/0xad0)
[    6.219444]  r3:de05a000 r2:00000000 r1:00000004 r0:c0806184
[    6.225124]  r7:de059e48
[    6.227692] [<c01269b4>] (do_exit) from [<c01281a8>] (do_group_exit+0x44/0xc4)
[    6.234932]  r7:0830009f
[    6.237502] [<c0128164>] (do_group_exit) from [<c0132e30>] (get_signal+0x1f8/0x59c)
[    6.245185]  r7:0830009f r6:de05c504 r5:de058000 r4:c0a0507c
[    6.250873] [<c0132c38>] (get_signal) from [<c010b724>] (do_signal+0xd0/0x42c)
[    6.258126]  r10:de058000 r9:00000002 r8:00000000 r7:00000000 r6:de059ec0 r5:00000000
[    6.265974]  r4:de059fb0
[    6.268537] [<c010b654>] (do_signal) from [<c010bc44>] (do_work_pending+0xa4/0xb4)
[    6.276138]  r10:de058000 r9:00000002 r8:00000000 r7:00000000 r6:de059fb0 r5:de058000
[    6.283985]  r4:b6f42700
[    6.286552] [<c010bba0>] (do_work_pending) from [<c010106c>] (slow_work_pending+0xc/0x20)
[    6.294751] Exception stack(0xde059fb0 to 0xde059ff8)
[    6.299832] 9fa0:                                     b6f58e68 bebe7176 00000010 00000024
[    6.308042] 9fc0: bebe7176 00000010 b6f58bf8 fffffffc 6fffffff 00000000 b6f58908 bebafe2c
[    6.316247] 9fe0: b6f58e68 bebafc90 b6f2a15c b6f42700 800d0010 ffffffff
[    6.322894]  r9:de058000 r8:00000000 r7:10c5387d r6:ffffffff r5:800d0010 r4:b6f42700
[    6.330695] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004
[    6.330695]

Thanks

Pieter

0 Kudos
Reply

2,000 Views
fabio_estevam
NXP Employee
NXP Employee

I would suggest you to start with the full imx_v6_v7_defconfig and then try to remove the features you don't need.

0 Kudos
Reply

2,000 Views
fabio_estevam
NXP Employee
NXP Employee

Hi Pieter,

Which SoC is your board based?

If it is mx5/m6, then I would suggest you to use the imx_v6_v7_defconfig instead.

Also, please post your dts as well.

Regards,

Fabio Estevam

0 Kudos
Reply