Bug 837

Summary: [n450] blacksand could not boot up with n450 BSP image
Product: [Build System, Metadata & Runtime] BSPs Reporter: Jiajun Xu <jiajun.xu>
Component: bsps-configurationAssignee: Darren Hart <dvhart>
Status: VERIFIED FIXED QA Contact:
Severity: critical    
Priority: High CC: dongxiao.xu, kunwei.tian, sgw, tom.zanussi, xudong.hao, yp.bsp.watcher, yp.watcher
Version: 1.0   
Target Milestone: 1.0 M4   
Hardware: Blacksand   
OS: x86   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Program Management Documentation change: ---

Description Jiajun Xu 2011-03-09 23:13:31 UTC 
Image location: http://autobuilder02.pokylinux.org/n450-bernard/nightly/20110307-1/machines/n450/x86_32/
Commit information: 1bac3117fab34673f08bb335170ad013bbd089cf

With the n450 image for RC2, the image could not boot up on blacksand after printing following messages:

#########
EXT3-fs (sda2): warning: checktime reached, running e2fsck is recommended
kjournald starting. Commit interval 5 seconds
EXT3-fs (sda2): using internal journal
EXT3-fs (sda2): recovery complete
EXT3-fs (sda2): mounted filesystem with writeback data mode
EXT3-fs (sda1): warning: checktime reached, running e2fsck is recommended
kjournald starting. Commit interval 5 seconds
EXT3-fs (sda1): using internal journal
EXT3-fs (sda1): recovery complete
EXT3-fs (sda1): mounted filesystem with writeback data mode
#########
Comment 1 Darren Hart 2011-03-10 09:05:24 UTC 
Which image and which image type? sato? live? What media, USB stick?
Comment 2 Jiajun Xu 2011-03-10 17:40:49 UTC 
(In reply to comment #1)
> Which image and which image type? sato? live? What media, USB stick?

I used sato-sdk-live image, http://autobuilder02.pokylinux.org/n450-bernard/nightly/20110307-1/machines/n450/x86_32/poky-image-sato-sdk-live-n450-20110307234401.hddimg.bz2. 
And yes, I use USB stick for live booting.
Comment 3 Darren Hart 2011-03-10 22:35:23 UTC 
Confirmed, I can reproduce reliably. Symptoms are similar to Bug 693. However, reinserting the USB key does not recover the boot. I'm building my own n450 and atom-pc images to test.

I noticed that the n450 kernel SRCREV is AUTOREV, which isn't right, it should match that of atom-pc since it uses the same linux-yocto machine branch.
Comment 4 Dongxiao Xu 2011-03-10 23:40:50 UTC 
I ever tried blacksand BSP (both from autobuilder and my self builds), and it doesn't work.
Comment 5 Darren Hart 2011-03-11 00:44:25 UTC 
According to Bug 798, this booted at least as of e08dc5aaaeba61e332caab4a3df5750df6b49ac1. I'm trying a bisect of poky from there. The -stable kernel hasn't been updated since December from what I can tell, so this doesn't appear to be a kernel source issue. More likely an initrd generation issue or similar.
Comment 6 Darren Hart 2011-03-11 08:49:41 UTC 
The kernel is being built without VFAT support, code pages, LOOPFS, so it can't mount the root filesystem. I'll patch and test.
Comment 7 Darren Hart 2011-03-11 09:43:46 UTC 
Fix under test. machine config was using older WRMACHINE syntax, so KMACHINE was undefined and it build common_pc-standard instead of atom-pc-standard.
Comment 9 Xudong Hao 2011-03-15 00:04:57 UTC 
Download RC3 image http://autobuilder02.pokylinux.org/n450-bernard/nightly/20110313-1/machines/n450/x86_32/poky-image-sato-live-n450-20110313170309.hddimg.bz2

System can boot up with RC3 image, mark it VERIFIED.
commit: a33a2cc024f9c9147c92c5da70d8fbb631b968f9