Tree/Branch: Poky-contrib/master_under_test Poky Commit id: 2f3994545e757efc575341f2b984a62a0a3441fd Image location: http://autobuilder03.jf.intel.com/nightly/20110730-1/machines/qemu/ There is no such issue in Yocto1.1 20110723 build. Qemux86-64's tasks were blocked due to this issue. Same messages for sato and asto-sdk as below: ###### .... devtmpfs: mounted Freeing unused kernel memory: 604k freed Kernel panic - not syncing : No init found. Try passing init= option to kernel. See Linux Documentation/init.txt for guidance. Pid: 1, comm: swapper Not tainted 2.6.37.6-yocto-standard+ #1 Call Trace: [<ffffffff814c4ac3>] panic+0x110/0x20b [<ffffffff814c3aac>] dump_stack+0x0/0x80 [<ffffffff81772e22>] rootwait_setup+0x0/0x19 [<ffffffff81003574>] kernel_thread_helper+0x4/0x10 [<ffffffff81772bfb>] ? kernel_init+0x0/0x227 [<ffffffff81003570>] ? kernel_thread_helper+0x0/0x10
I was not able to reproduce this. It may have been broken during the initial problems with multi-lib and the tune file changes. Please confirm with the latest builds that are being built today for M3-rc3.
This issue not reappear in latest image. Image location: http://autobuilder03.jf.intel.com/nightly/20110804-1/machines/qemu/qemux86_64/
This issue disappear in Yocto1.1 M3 RC3 build. Commit information as below: Tree/Branch: Poky/1.1_M3 Poky Commit id: 1580d1624647bc07ffd4997b6c8cfbccd8040fc5 Image location: http://autobuilder03.jf.intel.com/nightly/20110804-1/machines/qemu/qemux86_64/
Change the status to verified.