| Summary: | cannot liveboot or install crownbay-noemgd 1.5_M4 | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] BSPs | Reporter: | Alexandru Georgescu <alexandru.c.georgescu> | ||||||||
| Component: | bsps-meta-intel | Assignee: | Nitin Kamble <nitin.a.kamble> | ||||||||
| Status: | VERIFIED WORKSFORME | QA Contact: | |||||||||
| Severity: | normal | ||||||||||
| Priority: | Medium | CC: | tom.zanussi | ||||||||
| Version: | 1.5 | ||||||||||
| Target Milestone: | 1.5 M5 | ||||||||||
| Hardware: | Crownbay | ||||||||||
| OS: | Multiple | ||||||||||
| Whiteboard: | |||||||||||
| OS type for building Yocto: | --- | Type of Regression: | --- | ||||||||
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |||||||||
| Attachments: |
|
||||||||||
The core-image-sato-sdk-crownbay.hddimg boots and installs fine on the same hardware? Typically this failure is due to there not being enough memory to live-boot larger images such as the sato-sdk images. The difference between noemgd and emgd is new though and not what I would expect. Can you confirm that it was the sato-sdk boot/install that works on the emgd variant? I just tried this with my locally built core-image-sato for crownbay-noemgd and it is able to proceed with installation. Hi Nitin, Darre, I perform this test with this type of image on every full-pass and same hardware and this happened with the build I downloaded from the internal AB on M4.rc2 build: http://autobuilder03.jf.intel.com/pub/nightly-meta-intel/20130829-1/machines/crownbay-noemgd/core-image-sato-sdk-crownbay-noemgd.hddimg - I will try with the new RC3 image and see what happens and try again with the current noemgd variant - for emgd variant I could liveboot and install without problems. (In reply to comment #3) > Hi Nitin, Darre, > > I perform this test with this type of image on every full-pass and same > hardware and this happened with the build I downloaded from the internal AB > on M4.rc2 build: > http://autobuilder03.jf.intel.com/pub/nightly-meta-intel/20130829-1/machines/ > crownbay-noemgd/core-image-sato-sdk-crownbay-noemgd.hddimg > > > - I will try with the new RC3 image and see what happens and try again with > the current noemgd variant > > - for emgd variant I could liveboot and install without problems. Hmm... Just flashed the noemgd image again and tried liveboot and install and I have this X errors: Liveboot: -i could start boot but it hanged when starting X - see attach 1 After install: - same behavior, but different output - see attach 2 I will wait and try with the RC3 images and see if that reproduces. Created attachment 1464 [details]
attach 1
Created attachment 1465 [details]
attach 2
Hi, I tried again with the RC3 image: http://autobuilder03.jf.intel.com/pub/nightly-meta-intel/20130905-1/machines/crownbay-noemgd/core-image-sato-sdk-crownbay-noemgd.hddimg poky: ed3ef0823fde89371a473d20c0127c0bd16d062b meta-intel: a30089ab6a38541f729c680f1b3f05c3fbdc6ecf The installation worked but I could not liveboot. I just tried the latest bits for crownbay-noemgd ** poky repo: master: commit 0ca5d1fb38157564a2b9452ade32391d18a41b09 ** meta-intel: master: commit c5bce5dcaedc570c5220632c65dcf00773e0fd6b ** kernel version:linux-yocto-3.8.13+gitAUTOINC+f706bd410c_f20047520a-r4.2 And the liveboot is working as expected. Can you try again? Sure, I will try with 1.5_M5.rc1 Marking this as worksforme since I couldn't reroduce it on 1.5_m5.rc4. Will reopen it if this happens again. verified. |
Created attachment 1454 [details] dots poky 5745e45b18e5099e94b4d5a73bc97dc6d4cdc91f meta-intel 164067980e18e8ba60b317677ced2d75c3725dbe hardware - crownbay 1. Download the core-image-sato-sdk-crownbay-noemgd.hddimg from AB and write it on a USB drive 2. Try to install/liveboot it on a crownbay hardware. EXPECTED 2. Boot / Install successful ACTUAL 2. Boog/Install hangs when loading vmlinuz. When loading vmlinuz some dots appear to show that it is loading. The process hangs there: (see attachment) This happens only with crownbay-noemgd image. Without noemgd the Install/Boot works.