Bug 1917

Summary: non-GPLv3 image fails to boot up with no root filesystem found
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Jiajun Xu <jiajun.xu>
Component: coreAssignee: Joshua Lock - Disabled <josh>
Status: VERIFIED FIXED QA Contact:
Severity: normal    
Priority: Medium CC: jessica.zhang, meta.mr.watcher, meta.watcher, ningx.ma, yilongx.y.sun
Version: unspecified   
Target Milestone: 1.2 M3   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: ---
Bug Depends on: 1880    
Bug Blocks:    
Attachments:
Description Flags
boot failure snapshot
none
non-gplv3 build log none

Description Jiajun Xu 2012-01-18 06:13:25 UTC
Created attachment 318 [details]
boot failure snapshot

tree/branch: poky/1.2_M2
commit: 0f4d99d207b224bb9ce23de00a48f795ae20b3a0

With the 1.2_M2 branch, non-GPLv3 image could be built out successfully. But when we start it, QEMU kernel reports failure that no root filesystem found.
Comment 1 Saul Wold 2012-01-18 18:21:52 UTC
Were there any errors during the build?  Do you have the build log still, can you provide the output form a runquemu session with nographic?
Comment 2 Jiajun Xu 2012-01-18 22:24:33 UTC
(In reply to comment #1)
> Were there any errors during the build?  Do you have the build log still, can
> you provide the output form a runquemu session with nographic?

Hi Saul,
There is no provider for binutils in build log. I have no chance to boot up it with -nographic since it will report "Could not open option rom 'sgabios.bin': No such file or directory".
I attach the build faiure log for your reference.
Comment 3 Jiajun Xu 2012-01-18 22:24:57 UTC
Created attachment 320 [details]
non-gplv3 build log
Comment 4 Saul Wold 2012-01-24 11:17:53 UTC
It seems we pick up the linux-yocto-tiny kernel because of the binutils missing. Since binutils are missing we can't build the kernel perf-tools which in turn prevents the kernel from building.
Comment 5 Jessica 2012-03-08 20:19:42 UTC
During the bug triage we thought the problem maybe fixed already, Jiajun can you retest and confirm that it's still an issue? thx
Comment 6 MaNing 2012-03-09 08:57:53 UTC
There is no such issue in poky master testing.

Tree/Branch: Poky/master
Poky Commit id: 6bd23e0faf329f086bb4885991ce5f5d095dac56
Comment 7 Jiajun Xu 2012-03-09 13:49:11 UTC
Change the bug as fixed since we do not meet such issue in latest master.
Comment 8 Jiajun Xu 2012-03-09 13:49:33 UTC
Verify the bug as fixed.