Bug 7333

Summary: Kernel Panic during build the image for qemuarm
Product: [Build System, Metadata & Runtime] Meta-yocto Reporter: suneet saini <suneet.saini>
Component: meta-yoctoAssignee: Richard Purdie <richard.purdie>
Status: RESOLVED DUPLICATE QA Contact:
Severity: normal    
Priority: Undecided CC: poky.bs.watcher, poky.watcher, ross.burton
Version: unspecified   
Target Milestone: ---   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Don't know
Attachments:
Description Flags
snapshot of qemu none

Description suneet saini 2015-02-19 06:39:29 UTC
Created attachment 2415 [details]
snapshot of qemu

Kernel Panic : Not Syncing : Exit code 0x00000004

Hello Team,

          I am using the 'hob' from poky and building the image by selecting the machine as "qemuarm". Initially this file having architecture as followed
qemuarm.conf
+++++++++++++++++++++++++++++++++++++++
#@TYPE: Machine
#@NAME: arm_versatile_926ejs
#@DESCRIPTION: arm_versatile_926ejs

require conf/machine/include/qemu.inc
require conf/machine/include/tune-arm926ejs.inc
#require conf/machine/include/tune-arm1136jf-s.inc

KERNEL_IMAGETYPE = "zImage"

SERIAL_CONSOLE = "115200 ttyAMA0"
+++++++++++++++++++++++++++++++++++++++

After building the image with "core-image-minimal" or "core-image-full-cmdline" while running the image with qemu it works fine.  I want to change qemu working for "arm v7a" means support "Cortex A8". That's why for this I make the changes in qemuarm.conf as in the "~/poky/meta/conf/machine.conf"

qemuarm.conf
+++++++++++++++++++++++++++++++++++++++

require conf/machine/include/qemu.inc
require conf/machine/include/tune-cortexa8.inc

KERNEL_IMAGETYPE = "zImage"

SERIAL_CONSOLE = "115200 ttyAMA0"
+++++++++++++++++++++++++++++++++++++++

After that I am building the image and running it with qemu; I am getting the kernel panic.

Kernel Panic - not syncing : Attempting to kill Init! exitcode=0x00000004
Comment 1 Ross Burton 2015-02-19 15:40:29 UTC
Duplicate of 7332.

*** This bug has been marked as a duplicate of bug 7332 ***