Modify

Opened 3 years ago

Closed 3 years ago

#19034 closed defect (invalid)

Kernel Panic : Not Syncing : Exit code 0x00000004 in Yoctoprojects QemuArm

Reported by: suneet Owned by: developers
Priority: normal Milestone:
Component: packages Version: Trunk
Keywords: Cc:

Description

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

Attachments (1)

1.png (25.4 KB) - added by suneet 3 years ago.
Panic snapshot

Download all attachments as: .zip

Change History (2)

Changed 3 years ago by suneet

Panic snapshot

comment:1 Changed 3 years ago by nbd

  • Resolution set to invalid
  • Status changed from new to closed

Seems like you confused openwrt with openembedded :)

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.