<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugzilla.yoctoproject.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.6"
          urlbase="https://bugzilla.yoctoproject.org/"
          
          maintainer="it-coreprojects-helpdesk@linuxfoundation.org"
>

    <bug>
          <bug_id>2209</bug_id>
          
          <creation_ts>2012-03-31 01:25:02 +0000</creation_ts>
          <short_desc>[self-hosted] genext2fs fails to generate rootfs without enough memory</short_desc>
          <delta_ts>2012-04-18 08:43:55 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>7</classification_id>
          <classification>Build System, Metadata &amp; Runtime</classification>
          <product>OE-Core</product>
          <component>core</component>
          <version>unspecified</version>
          <rep_platform>x86</rep_platform>
          <op_sys>Multiple</op_sys>
          <bug_status>VERIFIED</bug_status>
          <resolution>FIXED</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard>(1.2) The fix is already in poky master(Apr 03, 2012). Tested by Dexuan.</status_whiteboard>
          <keywords></keywords>
          <priority>High</priority>
          <bug_severity>major</bug_severity>
          <target_milestone>1.2 M4</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Jiajun Xu">jiajun.xu</reporter>
          <assigned_to name="Dexuan Cui">dexuan.cui</assigned_to>
          <cc>dexuan.cui</cc>
    
    <cc>jessica.zhang</cc>
    
    <cc>meta.mr.watcher</cc>
    
    <cc>meta.watcher</cc>
    
    <cc>sgw</cc>
          
          
          <cf_os>---</cf_os>
          <cf_regression_type>---</cf_regression_type>
          
          <cf_docchange>---</cf_docchange>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>19735</commentid>
    <comment_count>0</comment_count>
    <who name="Jiajun Xu">jiajun.xu</who>
    <bug_when>2012-03-31 01:25:02 +0000</bug_when>
    <thetext>tree/branch: poky/1.2_M4
commit: da6233ea034f35eff59306fdad31f318c340c359

With 1.2 M4 branch, self-hosted image fails to build out due to system has no enough memory for utility genext2fs. All testing for self-hosted-image is blocked by the failure.

The log is as below:
#########
/home/jxu49/osel/m4/self-hosted/tmp/sysroots/i686-linux/usr/sbin/prelink: /usr/lib/gettext/urlget: Using /lib/ld-linux-x86-64.so.2, not /lib64/ld-linux-x86-64.so.2 as dynamic linker
/home/jxu49/osel/m4/self-hosted/tmp/sysroots/i686-linux/usr/sbin/prelink: /usr/lib/gettext/hostname: Using /lib/ld-linux-x86-64.so.2, not /lib64/ld-linux-x86-64.so.2 as dynamic linker
/home/jxu49/osel/m4/self-hosted/tmp/sysroots/i686-linux/usr/sbin/preERROR: Function failed: do_rootfs (see /home/jxu49/osel/m4/self-hosted/tmp/work/qemux86_64-poky-linux/self-hosted-image-1.0-r6/temp/log.do_rootfs.32564 for further information)
link: /usr/lib/quilt/backup-files: Using /lib/ld-linux-x86-64.so.2, not /lib64/ld-linux-x86-64.so.2 as dynamic linker
Size after prelinking 345524.
genext2fs: not enough memory for filesystem
#########</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>19777</commentid>
    <comment_count>1</comment_count>
    <who name="Dexuan Cui">dexuan.cui</who>
    <bug_when>2012-04-02 06:09:56 +0000</bug_when>
    <thetext>Jiajun,
The below patch should have already fixed the bug
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=79c806cb404c2d85aeec45b40ea6adbeae9f6346

You can re-start to test Build Appliance with the below commit(or a newer commmit):
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=2cf38f0d769c8b2d39cccc952846249a1e6cea6b


For BA, at least I think there are 3 known issues:
1) we need Saul&apos;s patch to generate a big enough image, or else, bitbake would get a &quot;no disk space available&quot; error during a building;
You can work this around by using an extra big .vmdk file as the build directory.

2) the RUN Qemu functionality of the hob in the guest can&apos;t work: looks some packages are missing.

3) you can exit the hob that is automatically run, and run hob manually: during a build, you can notice some error messages printed in the shell terminal of the user builder.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>19927</commentid>
    <comment_count>2</comment_count>
    <who name="Dexuan Cui">dexuan.cui</who>
    <bug_when>2012-04-05 05:55:27 +0000</bug_when>
    <thetext>(In reply to comment #1)
&gt; Jiajun,
&gt; The below patch should have already fixed the bug
&gt; http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=79c806cb404c2d85aeec45b40ea6adbeae9f6346
&gt; 
&gt; You can re-start to test Build Appliance with the below commit(or a newer
&gt; commmit):
&gt; http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=2cf38f0d769c8b2d39cccc952846249a1e6cea6b
Jiajun, you can test by using the latest poky master plus a small patch from me:
http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=dcui/master&amp;id=a8b5a3ed58d2a136867fc55b53443b59557c6459

&gt; 
&gt; For BA, at least I think there are 3 known issues:
&gt; 1) we need Saul&apos;s patch to generate a big enough image, or else, bitbake would
&gt; get a &quot;no disk space available&quot; error during a building;
&gt; You can work this around by using an extra big .vmdk file as the build
&gt; directory.
Saul has fixed the issue.

&gt; 2) the RUN Qemu functionality of the hob in the guest can&apos;t work: looks some
&gt; packages are missing.
I think this is still an issue.

&gt; 3) you can exit the hob that is automatically run, and run hob manually: during
&gt; a build, you can notice some error messages printed in the shell terminal of
&gt; the user builder.
Looks I can&apos;t reproduce this with a newly-built image now.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>20213</commentid>
    <comment_count>3</comment_count>
    <who name="Dexuan Cui">dexuan.cui</who>
    <bug_when>2012-04-12 01:38:43 +0000</bug_when>
    <thetext>(In reply to comment #2)
&gt; (In reply to comment #1)
&gt; &gt; Jiajun,
&gt; &gt; The below patch should have already fixed the bug
&gt; &gt; http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=79c806cb404c2d85aeec45b40ea6adbeae9f6346
&gt; &gt; 
&gt; &gt; You can re-start to test Build Appliance with the below commit(or a newer
&gt; &gt; commmit):
&gt; &gt; http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=2cf38f0d769c8b2d39cccc952846249a1e6cea6b
&gt; Jiajun, you can test by using the latest poky master plus a small patch from
&gt; me:
&gt; http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=dcui/master&amp;id=a8b5a3ed58d2a136867fc55b53443b59557c6459
&gt; 
&gt; &gt; 
&gt; &gt; For BA, at least I think there are 3 known issues:
&gt; &gt; 1) we need Saul&apos;s patch to generate a big enough image, or else, bitbake would
&gt; &gt; get a &quot;no disk space available&quot; error during a building;
&gt; &gt; You can work this around by using an extra big .vmdk file as the build
&gt; &gt; directory.
&gt; Saul has fixed the issue.
&gt; 
&gt; &gt; 2) the RUN Qemu functionality of the hob in the guest can&apos;t work: looks some
&gt; &gt; packages are missing.
&gt; I think this is still an issue.
&gt; 
This issue(xterm/vte terminal) was fixed by Saul.


---
This bug itself was fixed by
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=79c806cb404c2d85aeec45b40ea6adbeae9f6346


If anybody wants to try it, please use the 1.2_M4 tag that has more other fixes:
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?h=1.2_M4&amp;id=14286fe71e037ce895f01b51ac66a8986100b18f</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>20623</commentid>
    <comment_count>4</comment_count>
    <who name="Jiajun Xu">jiajun.xu</who>
    <bug_when>2012-04-18 08:43:55 +0000</bug_when>
    <thetext>Verify the bug as fixed with master commit 720fe9e371eef16da19df0885188aa0341ad2090.</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>