Discussion:
Full system emulation error message
(too old to reply)
Thawra Kadeed
2018-10-31 16:17:14 UTC
Permalink
Hello,

I am booting linux on ARM using Gem5 full system mode. I am using the
following kernels which are set in the FSConfig.py file:

default_dtbs = {
"RealViewEB": None,
"RealViewPBX": None,
"VExpress_EMM": "vexpress-v2p-ca15-tc1-gem5_%dcpus.20170616.dtb"
% num_cpus,
"VExpress_EMM64": "vexpress.aarch64.20140821.dtb",
}

default_kernels = {
"RealViewEB": "vmlinux.arm.smp.fb.2.6.38.8",
"RealViewPBX": "vmlinux.arm.smp.fb.2.6.38.8",
"VExpress_EMM": "vmlinux.vexpress_emm.20170616",
"VExpress_EMM64": "vmlinux.vexpress_emm64.20170616",
}


After I connected to a system.terminal using the telnet to see how Gem5
boots linux, I saw the following error message:

Starting init: /sbin/init exists but couldn't execute it (error -8)
Starting init: /etc/init exists but couldn't execute it (error -13)
request_module: runaway loop modprobe binfmt-464c
Starting init: /bin/sh exists but couldn't execute it (error -8)
Kernel panic - not syncing: No working init found. Try passing init=
option to kernel. See Linux Documentation/init.txt for guidance.


Does anyone have an idea about that error?

Taking into consideration that I have seen during the booting process
that it uses the following kernel and dtb:
kernel: vmlinux.vexpress_emm.20170616
dtb: vexpress-v2p-ca15-tc1-gem5_1cpus.20170616.dtb

Thanks in advance.

Loading...