Bug 101 - qemuppc images cannot boot up
Summary: qemuppc images cannot boot up
Status: VERIFIED FIXED
Alias: None
Product: Meta-yocto
Classification: Build System, Metadata & Runtime
Component: meta-yocto (show other bugs)
Version: unspecified
Hardware: x86 ppc
: High critical
Target Milestone: ---
Assignee: Richard Purdie
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2010-07-08 06:35 UTC by Jiajun Xu
Modified: 2010-12-21 06:07 UTC (History)
6 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified: Program Management
Documentation change: ---


Attachments
qemuppc crash log (8.04 KB, text/plain)
2010-07-08 06:36 UTC, Jiajun Xu
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jiajun Xu 2010-07-08 06:35:02 UTC
Testing Env:    
Host: Ubuntu 10.04 LTS
Kernel: 2.6.32-21-generic-pae
Poky gitinfo(used to build qemu-native):
aa416b6133bd55b5ba4d2fb6f5faef274ba511a0 (git.pokylinux.org:poky-wr
+yocto-kernel-clean)
qemuppc images: both sato & sdk from autobuilder, http://autobuilder.pokylinux.org/milestone/20100708-1/

It's known issue but since with latest commit we see there are some fixings, I just tried it.
qemuppc images(sato/sdk) cannot boot up. The dmesg shows that:
###########
Root-NFS: No NFS server available, giving up.
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Cannot open root device "hda" or unknown-block(2,0)
Please append a correct "root=" boot option; here are the available partitions:
VFS: Unable to mount root fs on unknown-block(2,0)
User configuration error - no valid root filesystem found
Kernel panic - not syncing: Invalid configuration from end user prevents continuing
Call Trace:
[c381de90] [c0008834] show_stack+0x48/0x15c (unreliable)
[c381dec0] [c035b928] panic+0x124/0x1a8
[c381df10] [c0431e78] mount_block_root+0x1b0/0x24c
[c381df60] [c043216c] prepare_namespace+0x140/0x1d4
[c381df80] [c04312a0] kernel_init+0x180/0x1bc
[c381dff0] [c0011d70] original_kernel_thread+0x4c/0x68
Rebooting in 180 seconds..
INFO: RCU detected CPU 0 stall (t=2500 jiffies)
###########

The command used to start qemu:
###########
runqemu qemuppc ext3 /home/jxu49/test/M1-new/osel/zImage-2.6.34+r1+git0+63a07cb64ccc3ceae619d3298545d602ab5ecd38-r1-qemuppc-20100708065121.bin /home/jxu49/test/M1-new/osel/poky-image-sdk-qemuppc-20100708065121.rootfs.ext3

/home/jxu49/wr/new/poky-wr/build/tmp/sysroots/i686-linux/usr/bin/qemu-system-ppc -kernel /home/jxu49/test/M1-new/osel/zImage-2.6.34+r1+git0+63a07cb64ccc3ceae619d3298545d602ab5ecd38-r1-qemuppc-20100708065121.bin -net nic,vlan=0 -net tap,vlan=0,ifname=tap0,script=/home/jxu49/wr/new/poky-wr/scripts/poky-qem -ifup,downscript=/home/jxu49/wr/new/poky-wr/scripts/poky-qemu-ifdown -cpu 603e -M prep -bios powerpc_rom.bin -hda /home/jxu49/test/M1-new/osel/poky-image-sdk-qemuppc-20100708065121.rootfs.ext3 -no-reboot -show-cursor -usb -usbdevice wacom-tablet -nographic --append root=/dev/hda console=ttyS0 console=tty0 ip=192.168.7.2::192.168.7.1:255.255.255.0 mem=64M
###########
Comment 1 Jiajun Xu 2010-07-08 06:36:12 UTC
Created attachment 13 [details]
qemuppc crash log
Comment 2 Saul Wold 2010-07-28 01:24:11 UTC
Please verify that this is still a problem in M2
Comment 3 Jiajun Xu 2010-07-28 01:28:15 UTC
Verified with M2 images, the bug is fixed.
http://yoctobuild01.jf.intel.com/milestone/20100725-1/