[yocto] [linux-yocto] [PATCH 0/1] [linux-yocto-3.0] boot-live.cfg: enable BLK_DEV_INITRD in kernel

Saxena, Rahul rahul.saxena at intel.com
Thu Sep 20 09:26:12 PDT 2012 


-----Original Message-----
From: Zanussi, Tom 
Sent: Wednesday, September 19, 2012 7:38 PM
To: Bruce Ashfield
Cc: Mihai Lindner; Development list for the linux-yocto*.git Linux kernel repositories; yocto at yoctoproject.org; Darren Hart; Bodke, Kishore K; Saxena, Rahul
Subject: Re: [linux-yocto] [yocto] [PATCH 0/1] [linux-yocto-3.0] boot-live.cfg: enable BLK_DEV_INITRD in kernel

On Wed, 2012-09-19 at 19:56 -0400, Bruce Ashfield wrote:
> On 12-09-19 04:54 PM, Mihai Lindner wrote:
> > On 2012-09-19 23:32, Bruce Ashfield wrote:
> >> On 12-09-19 04:22 PM, Bruce Ashfield wrote:
> >>> On 12-09-19 03:39 PM, Mihai Lindner wrote:
> >>>> On 2012-09-19 22:01, Bruce Ashfield wrote:
> >>>>> On 12-09-19 11:56 AM, Mihai Lindner wrote:
> >>>>>> On 2012-09-19 18:43, Bruce Ashfield wrote:
> >>>>>>> On 12-09-18 10:46 AM, Mihai Lindner wrote:
> >>>>>>>> On 2012-09-18 17:23, Tom Zanussi wrote:
> >>>>>>>>> On Tue, 2012-09-18 at 16:58 +0300, Mihai Lindner wrote:
> >>>>>>>>>> On 2012-09-18 16:49, Tom Zanussi wrote:
> >>>>>>>>>>> On Tue, 2012-09-18 at 08:21 -0400, Bruce Ashfield wrote:
> >>>>>>>>>>>> On 12-09-18 01:59 AM, Mihai Lindner wrote:
> >>>>>>>>>>>>> Please pull into linux-yocto-3.0, meta.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> Adding linux-yocto, Darren and Tom.
> >>>>>>>>>>>>
> >>>>>>>>>>>> This looks fine to me, and we should consider it for all 
> >>>>>>>>>>>> the repositories, not just 3.0.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Tom/Darren. Any side effects you can think of for this change ?
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> No, but shouldn't it already be there, inherited from base.cfg?
> >>>>>>>>>>
> >>>>>>>>>> For cedartrail, at least, standard.cfg is used.
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> And standard inherits from base, so it should be turned on. 
> >>>>>>>>> Somehow it's getting turned off in cedartrail...
> >>>>>>>>
> >>>>>>>> Yes, it the final .config file is turned off. Solved it by 
> >>>>>>>> setting it in boot-live.
> >>>>>>>> --Mihai
> >>>>>>>
> >>>>>>> To follow up on this, is someone taking a closer look at this 
> >>>>>>> config to see if we can get a root cause for that option being 
> >>>>>>> disabled for this board ?
> >>>>>>>
> >>>>>>> I won't be able to poke at it myself for another day or so.
> >>>>>>>
> >>>>>>> Bruce
> >>>>>>>
> >>>>>> I'm still digging on this, trying to figure out what cfg files 
> >>>>>> are included / omitted by `configme` and why.
> >>>>>> base.cfg is not included, nor stanadrd.cfg it seems.
> >>>>>> The list of included cfg files is way to short.
> >>>>>
> >>>>> That likely means the BSP .scc file is missing and update (i.e. 
> >>>>> does it still have scc_leaf?) and the tools aren't finding it 
> >>>>> and auto-generating something to get you up and running.
> >>>>>
> >>>>> I just checked the meta branch here, and it looks to be updated, 
> >>>>> but if you look at your build's linux source dir, what's in meta/top_tgt ?
> >>>>>
> >>>>> Bruce
> >>>>>
> >>>> In meta/top_tgt i have:
> >>>>
> >>>> /home/mihai/cedartrail/tmp/work/cedartrail-poky-linux/linux-yocto
> >>>> -3.0.32+git5+46e8fc2bbbe73514e8d99101adaaa373f760ffa7_1+1e79e03d1
> >>>> 15ed177882ab53909a4f3555e434833-r4.1/linux/meta/cfg/kernel-cache/
> >>>> bsp/cedartrail/cedartrail-standard.scc
> >>>>
> >>>>
> >>>>
> >>>> I've also hit an error, after more verbose runs of 
> >>>> ./cedartrail-standard in meta/cfg/scratch/obj/:
> >>>>
> >>>> ./0-cedartrail-standard-897c5c055888aca397b3ab0d7be9e6fa.sco: line 17:
> >>>> standard_5b57715386592f694588063dd3ec6ebb: command not found
> >>>>
> >>>> After this the scripts stops.
> >>>>
> >>>
> >>> Aha. This definitely breaks the configuration chain (and would 
> >>> throw a hard error in the 3.4 kernel) and is where the options 
> >>> drop. But this should no way be specific to this board. I'll get 
> >>> something configured here, since I need to see this happen in front of me.
> >>
> >> I've finally reproduced this. Leave the issue with me and I'll get 
> >> back to you with a fix.
> >>
> >> Bruce
> >
> > Yay! Thanks.
> > It's not specific, it's just easier to hit; for cedartrail only 3.0 is available, and also set as preferred.
> >
> 
> Aha. I was right. It is a tools issue and a interface that changed.
> I made a fix for this in the 3.0 kernel tree some time ago, but I 
> didn't update the lagging BSPs, and the handoff to a meta-intel change 
> was missed.
> 
> With this change (sorry for the linewraps, I'm out of the office):
> 
> --git a/meta-cedartrail/recipes-kernel/linux/linux-yocto_3.0.bbappend
> b/meta-cedartrail/recipes-kernel/linux/linux-yocto_3.0.bbappend
> index 35c4755..212a400 100644
> --- a/meta-cedartrail/recipes-kernel/linux/linux-yocto_3.0.bbappend
> +++ b/meta-cedartrail/recipes-kernel/linux/linux-yocto_3.0.bbappend
> @@ -16,7 +16,7 @@ KBRANCH_cedartrail-nopvr  = "yocto/standard/cedartrail"
>   KERNEL_FEATURES_append_cedartrail-nopvr += " cfg/smp.scc"
> 
>   SRCREV_machine_pn-linux-yocto_cedartrail ?= 
> "1e79e03d115ed177882ab53909a4f3555e434833"
> -SRCREV_meta_pn-linux-yocto_cedartrail ?= 
> "46e8fc2bbbe73514e8d99101adaaa373f760ffa7"
> +SRCREV_meta_pn-linux-yocto_cedartrail ?=
> "bf5ee4945ee6d748e6abe16356f2357f76b5e2f0"
>   SRCREV_pvr_pn-linux-yocto_cedartrail ?= 
> "997f5644664b31ebefd6e16c451c4a3729eb378a"
> 
>   SRCREV_machine_pn-linux-yocto_cedartrail-nopvr ?= 
> "1e79e03d115ed177882ab53909a4f3555e434833"
> 
> i.e. bump the META srcrev and everything is properly configured.
> Tom or Darren .. or someone else can make the change permanently in 
> meta-intel/meta-cedartrail.
> 

Fix pushed to meta-intel/master, thanks, Bruce.

Rahul, Kishore, could you please verify the fix and check whether there might be other SRCREV updates lurking?

Tom

> Cheers,
> 
> Bruce
> 
> 
> 
> 
> > --Mihai
> >
> >>
> >>>
> >>> Cheers,
> >>>
> >>> Bruce
> >>>
> >>>
> >>>> Mihai
> >>>>
> >>>>>
> >>>>>>
> >>>>>> --Mihai
> >>>>>>>>
> >>>>>>>>>
> >>>>>>>>> Tom
> >>>>>>>>>
> >>>>>>>>>> --Mihai
> >>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> Tom
> >>>>>>>>>>>
> >>>>>>>>>>>> Bruce
> >>>>>>>>>>>>
> >>>>>>>>>>>>> Added BLK_DEV_INITRD in boot-live.cfg for 
> >>>>>>>>>>>>> linux-yocto-3.0, meta branch.
> >>>>>>>>>>>>> Cedartrail (at least) cannot boot live from ISO image 
> >>>>>>>>>>>>> due to BLK_DEV_INITRD missing:
> >>>>>>>>>>>>> "VFS: Cannot open root device "ram0" or unkown-block(0,0)"
> >>>>>>>>>>>>> Should fix #3050
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> [YOCTO #3050]
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Signed-off-by: Mihai 
> >>>>>>>>>>>>> Lindner<mihaix.lindner at linux.intel.com>
> >>>>>>>>>>>>> ---
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> The following changes since commit
> >>>>>>>>>>>>> bf5ee4945ee6d748e6abe16356f2357f76b5e2f0:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> meta: rename virto.scc to virtio.scc (2012-08-18 
> >>>>>>>>>>>>> 22:09:35 -0400)
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> are available in the git repository at:
> >>>>>>>>>>>>> git://git.yoctoproject.org/poky-contrib
> >>>>>>>>>>>>> mihai/linux-yocto-3.0/meta
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Mihai Lindner (1):
> >>>>>>>>>>>>> boot-live.cfg: enable BLK_DEV_INITRD in kernel
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> meta/cfg/kernel-cache/cfg/boot-live.cfg | 2 ++
> >>>>>>>>>>>>> 1 files changed, 2 insertions(+), 0 deletions(-)
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Mihai Lindner (1):
> >>>>>>>>>>>>> boot-live.cfg: enable BLK_DEV_INITRD in kernel
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> meta/cfg/kernel-cache/cfg/boot-live.cfg | 2 ++
> >>>>>>>>>>>>> 1 files changed, 2 insertions(+), 0 deletions(-)
> >>>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>
> >>> _______________________________________________
> >>> linux-yocto mailing list
> >>> linux-yocto at yoctoproject.org
> >>> https://lists.yoctoproject.org/listinfo/linux-yocto
> >>
> >>
> >>
> >
> >
> 

 Yes, I was able to now successfully boot my cedartrail image.
Thanks to all who worked on resolving this !

 Rahul

More information about the yocto mailing list