Different behaviors of sysvinit and systemd on FSL p4080ds(ppce500mc core)

Different behaviors of sysvinit and systemd on FSL p4080ds(ppce500mc core)

[Luo Zhenhua]

[-- Attachment #1: Type: text/plain, Size: 1499 bytes --]

Hi all,

I use jethro of poky + jethro of meta-fsl-ppc layer to build the images (uImage, dtb and core-image-minimal rootfs) for FSL p4080ds board(ppce500mc), the boot process works well. The default init manager is sysvinit.

If I add below two lines in local.conf to switch to systemd as the init manager and build new core-image-minimal rootfs, the boot process will hang.
DISTRO_FEATURES_append = " systemd"
VIRTUAL-RUNTIME_init_manager = "systemd"

The following call trace appears during the systemd rootfs boot up.
...
VFS: Mounted root (ext2 filesystem) on device 1:0.
devtmpfs: mounted
Freeing unused kernel memory: 272K (c085d000 - c08a1000)
init[1]: unhandled signal 4 at 204ea61c nip 204ea61c lr 203bfe24 code 30001
Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004

CPU: 0 PID: 1 Comm: init Not tainted 3.12.37-rt51 #1
Call Trace:
[e80a3d00] [c0006fd4] show_stack+0x34/0x170 (unreliable)
[e80a3d40] [c06837c4] dump_stack+0x78/0xa0
[e80a3d50] [c06818d4] panic+0xd8/0x204
[e80a3da0] [c0030b94] do_exit+0x8f4/0x900
[e80a3e00] [c0031a60] do_group_exit+0x40/0xb0
[e80a3e20] [c00406e4] get_signal_to_deliver+0x254/0x520
[e80a3e70] [c0007b60] do_signal+0x40/0x1f0
[e80a3f30] [c0007e28] do_notify_resume+0x68/0x80
[e80a3f40] [c00109ec] do_user_signal+0x74/0xc4
--- Exception: 700 at 0x204ea61c
    LR = 0x203bfe24
Rebooting in 180 seconds..

Does somebody know what is the reason and how to resolve the issue?


Best Regards,

Zhenhua

[-- Attachment #2: Type: text/html, Size: 4733 bytes --]