| Summary: | qemuarm could not startup with 20130521-1 image (gcc 4.8) | ||
|---|---|---|---|
| Product: | [Runtime] General Runtime | Reporter: | Ke Zou <ke.zou> |
| Component: | General Runtime | Assignee: | Bruce Ashfield <bruce.ashfield> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | Medium+ | CC: | alexandru.c.georgescu, dvhart, elizabeth.flanagan, ionutx.chisanovici, ning.zhang, richard.purdie, yi.zhao |
| Version: | 1.5 | ||
| Target Milestone: | 1.5 M2 | ||
| Hardware: | Other | ||
| OS: | arm | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Don't know | |
|
Description
Ke Zou
2013-05-24 06:11:02 UTC
My same comment applies here, just as it did for the beagleboard. Is this a gcc 4.8 build ? If so, return it to the build system category. ARM BSPs should not be using gcc 4.8 as their default yet, and whoever made it the default for them, should have also verified boot and pinned versions for boards that failed. Hello, I would like to have more info about this issue, so that all of us are clear on what happens. I have tested with the today's weekly build: http://autobuilder.yoctoproject.org/pub/nightly/20130528-2/ and I could boot several qemu images (arm, ppc) with ext3 extension or tar.bz2). I have tested on a Fedora 17 64 bit and on CentOS 6.4. So my questions are: - what is your host environment? (Distribution, architecture) - what yocto environment did you use (did you source the toolchain sdk or you sourced the poky environment?) And I can confirm that qemuarm boots fine with ubuntu 12.04 and 13.10 from my builds yesterday. I also re-tested the new build from http://autobuilder.yoctoproject.org/pub/nightly/20130528-2/ . It can boot up without problem. When the kernel booting, I noticed there is a message: ... Linux version 3.8.11-yocto-standard (pokybuild@ab10.i.yoctoproject.org) (gcc version 4.7.2 (GCC) ) #1 PREEMPT Fri May 24 16:29:23 UTC 2013 ... However, for the old build from http://autobuilder.yoctoproject.org/pub/nightly/20130521-1/ , When the kernel booting, the message is: ... Linux version 3.8.11-yocto-standard (pokybuild@ab05) (gcc version 4.8.0 (GCC) ) #1 PREEMPT Tue May 14 21:59:51 UTC 2013 ... It looks like that the kernel was built with gcc 4.8 and didn't re-build since May 14. I don't know why the kernel didn't re-build in this build. Is it a autobuilder issue or a sstate issue ? *** Bug 4548 has been marked as a duplicate of this bug. *** This was the result of a MUT build pulling in gcc 4.8 into sstate and the AB not rebuilding with 4.7. This is expected behavior as a change in the toolchain is explicitly prevented from triggering a rebuild. This bug is now essentially tracking the gcc 4.8 ARM work, which is in progress. Tested with http://autobuilder.yoctoproject.org/pub/nightly/20131019-1/machines/qemu/qemuarm/ runqemu qemuarm zImage--3.10.11+git0+452f0679ea_aa1fa3cec7-r0-qemuarm-20131011191708.bin core-image-sato-qemuarm-20131019051153.rootfs.ext3 nographic The machine booted up without any problems. Linux version 3.10.11-yocto-standard (pokybuild@ab06.i.yoctoproject.org) (gcc version 4.8.1 (GCC) ) #1 PREEMPT Fri Oct 11 19:48:23 UTC 2013 Should we close this bug and 4548, is this still an issue ? This is definitely fixed now. We can close the bug. (In reply to comment #8) > Tested with > http://autobuilder.yoctoproject.org/pub/nightly/20131019-1/machines/qemu/ > qemuarm/ > > runqemu qemuarm > zImage--3.10.11+git0+452f0679ea_aa1fa3cec7-r0-qemuarm-20131011191708.bin > core-image-sato-qemuarm-20131019051153.rootfs.ext3 nographic > > The machine booted up without any problems. > Linux version 3.10.11-yocto-standard (pokybuild@ab06.i.yoctoproject.org) > (gcc version 4.8.1 (GCC) ) #1 PREEMPT Fri Oct 11 19:48:23 UTC 2013 > > Should we close this bug and 4548, is this still an issue ? Then, as stated above, this is verified. |