qte-in-use-image rootfs issue

qte-in-use-image rootfs issue

[Diego Sueiro]

[-- Attachment #1: Type: text/plain, Size: 1309 bytes --]

Folks,

I've built qte-in-use-image for cubox-i and the boot log printed some
strange fail messages:
http://pastebin.com/jwEYcUNF

The /sys, /var/lock and /var/log are files and not directories.
Looking
at tmp/work/cubox_i-poky-linux-gnueabi/qte-in-use-image/1.0-r0/rootfs/ the
were created as directories.

There are some libs missing too.
I wanna know if someone is getting this kind of errors too.

Here is my build configuration:

BB_VERSION        = "1.21.1"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "Ubuntu-12.10"
TARGET_SYS        = "arm-poky-linux-gnueabi"
MACHINE           = "cubox-i"
DISTRO            = "poky"
DISTRO_VERSION    = "1.5+snapshot-20140217"
TUNE_FEATURES     = "armv7a vfp neon callconvention-hard cortexa9"
TARGET_FPU        = "vfp-neon"
meta
meta-yocto
meta-yocto-bsp    = "master:3221d97323e655fe5db863157d71ca79983b5b07"
meta-oe           = "master:5b499287f2be91a898507b668d492b20eb7e8b24"
meta-fsl-arm      = "master:40385ba8b3060adb3a535c6e5f08199b69f47754"
meta-fsl-arm-extra = "master-next:c5a714d99208d643262cbb7d2a230c0efffa20fe"
meta-fsl-demos    = "master:ef728d5fc8269fbd47f294a448c356842e4f39cc"




Regards,

--
*dS
Diego Sueiro

Administrador do Embarcados
www.embarcados.com.br

/*long live rock 'n roll*/

[-- Attachment #2: Type: text/html, Size: 2204 bytes --]

Re: qte-in-use-image rootfs issue

[Diego Sueiro]

[-- Attachment #1: Type: text/plain, Size: 1067 bytes --]

On Mon, Feb 17, 2014 at 8:41 AM, Diego Sueiro <diego.sueiro@gmail.com>wrote:

> I've built qte-in-use-image for cubox-i and the boot log printed some
> strange fail messages:
> http://pastebin.com/jwEYcUNF
>
> The /sys, /var/lock and /var/log are files and not directories.
> Looking
> at tmp/work/cubox_i-poky-linux-gnueabi/qte-in-use-image/1.0-r0/rootfs/ the
> were created as directories.
>
> There are some libs missing too.
> I wanna know if someone is getting this kind of errors too.
>

After inserting the uSD on my host I realized that there were errors in the
filesystems. Aftter a e2fsck the box didn't boot anymore.
So, I formatted the rootfs partition and extracted the rootfs.tar.bz2
manually to the roofts partition and the box booted.

I've burn the sdimg twice and the issue persisted. Is there something wrong
with the ext3 image generated?
I've used the same uSD on BBB several times without any issues.

Regards,

--
*dS
Diego Sueiro

Administrador do Embarcados
www.embarcados.com.br

/*long live rock 'n roll*/

[-- Attachment #2: Type: text/html, Size: 1792 bytes --]

Re: qte-in-use-image rootfs issue

[Jacob Kroon]

[-- Attachment #1: Type: text/plain, Size: 1634 bytes --]

FWIW, using master branches, recently I've also been seeing corrupt rootfs
images when dd:ing the .sdcard-file. If I dd the .ext3 file to the second
partition again, everything looks ok.

Using Wandboard Solo machine.


On Mon, Feb 17, 2014 at 2:24 PM, Diego Sueiro <diego.sueiro@gmail.com>wrote:

>
> On Mon, Feb 17, 2014 at 8:41 AM, Diego Sueiro <diego.sueiro@gmail.com>wrote:
>
>> I've built qte-in-use-image for cubox-i and the boot log printed some
>> strange fail messages:
>> http://pastebin.com/jwEYcUNF
>>
>> The /sys, /var/lock and /var/log are files and not directories.
>> Looking
>> at tmp/work/cubox_i-poky-linux-gnueabi/qte-in-use-image/1.0-r0/rootfs/ the
>> were created as directories.
>>
>> There are some libs missing too.
>> I wanna know if someone is getting this kind of errors too.
>>
>
> After inserting the uSD on my host I realized that there were errors in
> the filesystems. Aftter a e2fsck the box didn't boot anymore.
> So, I formatted the rootfs partition and extracted the rootfs.tar.bz2
> manually to the roofts partition and the box booted.
>
> I've burn the sdimg twice and the issue persisted. Is there something
> wrong with the ext3 image generated?
> I've used the same uSD on BBB several times without any issues.
>
>
> Regards,
>
> --
> *dS
> Diego Sueiro
>
> Administrador do Embarcados
> www.embarcados.com.br
>
> /*long live rock 'n roll*/
>
> _______________________________________________
> meta-freescale mailing list
> meta-freescale@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-freescale
>
>


-- 
  -- Jacob

[-- Attachment #2: Type: text/html, Size: 2838 bytes --]

Re: qte-in-use-image rootfs issue

[Otavio Salvador]

On Mon, Feb 17, 2014 at 8:41 AM, Diego Sueiro <diego.sueiro@gmail.com> wrote:
> Folks,
>
> I've built qte-in-use-image for cubox-i and the boot log printed some
> strange fail messages:
> http://pastebin.com/jwEYcUNF
>
> The /sys, /var/lock and /var/log are files and not directories.
> Looking at
> tmp/work/cubox_i-poky-linux-gnueabi/qte-in-use-image/1.0-r0/rootfs/ the were
> created as directories.
>
> There are some libs missing too.
> I wanna know if someone is getting this kind of errors too.

Yes; this is due the master rework of the rootfs generation; the class
which generates the sdcard must to be reviewed and adapter to the new
code. I didn't yet look at this.

Someone wish to take the task? I think I can start looking at this in a day.

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

Re: qte-in-use-image rootfs issue

[Diego Sueiro]

[-- Attachment #1: Type: text/plain, Size: 571 bytes --]

On Mon, Feb 17, 2014 at 10:57 AM, Otavio Salvador
<otavio@ossystems.com.br>wrote:

> Yes; this is due the master rework of the rootfs generation; the class
> which generates the sdcard must to be reviewed and adapter to the new
> code. I didn't yet look at this.
>
> Someone wish to take the task? I think I can start looking at this in a
> day.
>

I can take a look on this. Could you please point me some instructions to
start with?


Regards,

--
*dS
Diego Sueiro

Administrador do Embarcados
www.embarcados.com.br

/*long live rock 'n roll*/

[-- Attachment #2: Type: text/html, Size: 1105 bytes --]

Re: qte-in-use-image rootfs issue

[Eric Nelson]

Hi all,

On 02/17/2014 06:41 AM, Jacob Kroon wrote:
> FWIW, using master branches, recently I've also been seeing corrupt
> rootfs images when dd:ing the .sdcard-file. If I dd the .ext3 file to
> the second partition again, everything looks ok.
>
> Using Wandboard Solo machine.
>
> On Mon, Feb 17, 2014 at 2:24 PM, Diego Sueiro <diego.sueiro@gmail.com
> <mailto:diego.sueiro@gmail.com>> wrote:
>
 > <snip>
>
>     After inserting the uSD on my host I realized that there were errors
>     in the filesystems. Aftter a e2fsck the box didn't boot anymore.
>     So, I formatted the rootfs partition and extracted the
>     rootfs.tar.bz2 manually to the roofts partition and the box booted.
>

Ditto on nitrogen6x building for Qt5.

I think this is not related to the qte-in-use image, but
something more fundamental.

Regards,


Eric

Re: qte-in-use-image rootfs issue

[Otavio Salvador]

Hello Eric,

On Mon, Feb 17, 2014 at 11:23 AM, Eric Nelson
<eric.nelson@boundarydevices.com> wrote:
> On 02/17/2014 06:41 AM, Jacob Kroon wrote:
>>
>> FWIW, using master branches, recently I've also been seeing corrupt
>> rootfs images when dd:ing the .sdcard-file. If I dd the .ext3 file to
>> the second partition again, everything looks ok.
>>
>> Using Wandboard Solo machine.
>>
>> On Mon, Feb 17, 2014 at 2:24 PM, Diego Sueiro <diego.sueiro@gmail.com
>> <mailto:diego.sueiro@gmail.com>> wrote:
>>
>> <snip>
>
>>
>>     After inserting the uSD on my host I realized that there were errors
>>     in the filesystems. Aftter a e2fsck the box didn't boot anymore.
>>     So, I formatted the rootfs partition and extracted the
>>     rootfs.tar.bz2 manually to the roofts partition and the box booted.
>>
>
> Ditto on nitrogen6x building for Qt5.
>
> I think this is not related to the qte-in-use image, but
> something more fundamental.

Yes; the core rootfs support has been rewritten in Python and this has
some radical impact in our use of it. I will look at this to solve the
root cause once I have a time slot.


-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750