Bug 657

Summary:	QEMU ppc minimal system boot failed using images of nightly build 20110114-1
Product:	[Yocto Project Subprojects] Kernel	Reporter:	liang li <liang.li2>
Component:	kernel-tooling	Assignee:	Bruce Ashfield <bruce.ashfield>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	normal
Priority:	Undecided	CC:	jiajun.xu, ke.yu, liangliang.wang, sgw, yi.zhao, yp.kernel.watcher, yp.watcher
Version:	unspecified
Target Milestone:	1.0 M3
Hardware:	x86
OS:	Multiple
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	---

Description liang li 2011-01-17 21:38:54 UTC

1.download images from nightly build 20110114-1:
kernel: http://autobuilder.pokylinux.org/nightly/20110114-1/qemu/qemuppc/zImage-2.6.37+git0+7102097a25c7658e0f4d4dc71844e0ff6c446b25_0+20f182db27f3e6fc6bd55bfc9e24c8c023fbff7f-r15-qemuppc-20110115173309.bin
rootfs: http://autobuilder.pokylinux.org/nightly/20110114-1/qemu/qemuppc/poky-image-minimal-qemuppc-20110115205642.rootfs.ext3 
2.run "source /home/liangli/test_poky_git_1/poky-init-build-env /home/liangli/poky-git-build_1" 
3.run "poky-qemu qemuppc /home/liangli/download_1_17/qemu/zImage-2.6.37+git0+7102097a25c7658e0f4d4dc71844e0ff6c446b25_0+20f182db27f3e6fc6bd55bfc9e24c8c023fbff7f-r15-qemuppc-20110115173309.bin /home/liangli/download_1_17/poky-image-minimal-qemuppc-20110115205642.rootfs.ext3 ext3"
4. kernel panic messages below:
...
IP-Config: Complete:
     device=eth0, addr=192.168.7.2, mask=255.255.255.0, gw=192.168.7.1,
     host=192.168.7.2, domain=, nis-domain=(none),
     bootserver=255.255.255.255, rootserver=255.255.255.255, rootpath=
md: Waiting for all devices to be available before autodetect
md: If you don't use raid, use raid=noautodetect
md: Autodetecting RAID arrays.
md: Scanned 0 and added 0 devices.
md: autorun ...
md: ... autorun DONE.
List of all partitions:
0300           88584 hda  driver: ide-gd
No filesystem could mount root, tried:  ext3 ext2
VFS: Unable to mount root fs on unknown-block(3,0)
User configuration error - no valid root filesystem found
Kernel panic - not syncing: Invalid configuration from end user prevents continuing
Call Trace:
[c7843e20] [c000a688] show_stack+0x108/0x1c4 (unreliable)
[c7843e70] [c03c2778] dump_stack+0x2c/0x44
[c7843e80] [c03c284c] panic+0xbc/0x1e4
[c7843ee0] [c04d2eb0] mount_block_root+0x21c/0x244
[c7843f30] [c04d30d8] mount_root+0xbc/0xd4
[c7843f60] [c04d3294] prepare_namespace+0x1a4/0x1e8
[c7843f80] [c04d29dc] kernel_init+0x184/0x1a4
[c7843ff0] [c00129f0] kernel_thread+0x4c/0x68
Rebooting in 180 seconds..Set 'tap0' nonpersistent
Releasing lockfile of preconfigured tap device 'tap0'
liangli@liangli-OptiPlex-745:~/poky-git-build_1$

Comment 1 Bruce Ashfield 2011-01-17 22:10:25 UTC

This must be in your configuration. poky-image* builds and boots fine out of master
for me:

qemuppc login: root
root@qemuppc:~# uname -a
Linux qemuppc 2.6.37-yocto-standard+ #1 PREEMPT Tue Jan 18 00:46:34 EST 2011 ppc GNU/Linux
root@qemuppc:~# 

Can we retry with a build out of master ?

Comment 2 Liang Wang 2011-01-17 22:21:54 UTC

This issue does not occur on qemumips.
image: http://autobuilder.pokylinux.org/nightly/20110114-1/qemu/qemumips/poky-image-minimal-qemumips-20110115173034.rootfs.ext3 

git info:  commit d38ad3271829b2d282c973e69edd265ef52174c8

Comment 3 liang li 2011-01-17 23:21:35 UTC

  (In reply to comment #1)
> This must be in your configuration. poky-image* builds and boots fine out of
> master
> for me:
> 
> qemuppc login: root
> root@qemuppc:~# uname -a
> Linux qemuppc 2.6.37-yocto-standard+ #1 PREEMPT Tue Jan 18 00:46:34 EST 2011
> ppc GNU/Linux
> root@qemuppc:~# 
> 
> Can we retry with a build out of master ?

yes, use git master ,minimal system boot successfully.
master git info:
740ea68258282c459b66bbed550e6347fb8e83a3
images of 20110114-1 git info:
d38ad3271829b2d282c973e69edd265ef52174c8
images in that dir boot failed. 
thanks.

Comment 4 Yi Zhao 2011-01-18 00:06:40 UTC

I download image from http://autobuilder.pokylinux.org/nightly/20110114-1/qemu/qemuppc/

The qemuppc minimal image can boot successfully.

Comment 5 liang li 2011-01-18 00:19:12 UTC

maybe configuration problems.

Comment 6 liang li 2011-01-18 00:24:51 UTC

close it.