<?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>4982</bug_id>
          
          <creation_ts>2013-08-05 09:34:08 +0000</creation_ts>
          <short_desc>[beagleboard xm] ltp test failed because cmd mkfs.ext4 does not exist</short_desc>
          <delta_ts>2013-08-08 04:12:13 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>11</classification_id>
          <classification>Runtime</classification>
          <product>General Runtime</product>
          <component>General Runtime</component>
          <version>1.5</version>
          <rep_platform>Beagleboard</rep_platform>
          <op_sys>arm</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>INVALID</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>Medium</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>1.5</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Ning Zhang">ning.zhang</reporter>
          <assigned_to name="Saul Wold">sgw</assigned_to>
          <cc>ke.zou</cc>
    
    <cc>mark.hatle</cc>
    
    <cc>yi.zhao</cc>
          
          
          <cf_os>---</cf_os>
          <cf_regression_type>---</cf_regression_type>
          
          <cf_docchange>Don&apos;t know</cf_docchange>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>35363</commentid>
    <comment_count>0</comment_count>
    <who name="Ning Zhang">ning.zhang</who>
    <bug_when>2013-08-05 09:34:08 +0000</bug_when>
    <thetext>Poky: master:9de0ad47462c13ac4a2d73e12e92be6c1b4e0415

Steps:
1. download autobuilder.yoctoproject.org/pub/nightly/20130731-1 beagleboard core-image-sato-sdk image, use it bootup target.
2. cd /opt/ltp
3. start ltp test with below cli:
./runltp -p -f syscalls,fs,fsx,dio,io,mm,ipc,sched,math,nptl,pty,admin_tools,timers,commands -l ltp-arch-YYYYMMDD-result.log -C ltp-arch-YYYYMMDD-failed.log -d /opt/tmp &amp;&gt; ltp-arch-YYYYMMDD-output.log

4. the test failed very soon. And it has below error info:
creating a ext4 block device failed                                   
mount: wrong fs type, bad option, bad superblock on /dev/loop0,
       missing codepage or helper program, or other error                       

       In some cases useful info is found in syslog - try
       dmesg | tail or so. 
FATAL: can&apos;t mount block device /dev/loop0

5. try to find mkfs.ext4 command in shell, it does not exist.

root@beagleboard:/opt/ltp# which mkfs.ext4
root@beagleboard:/opt/ltp# mkfs.
mkfs.bfs               mkfs.cramfs            mkfs.minix             mkfs.minix.util-linux</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>35437</commentid>
    <comment_count>1</comment_count>
    <who name="Saul Wold">sgw</who>
    <bug_when>2013-08-06 21:12:37 +0000</bug_when>
    <thetext>Should LTP be run on Sato?  Is this a new bug? Have we run this on SATO before, I thought this should be run on lsb or basic images that include e2fsprogs, I am not sure sato does.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>35452</commentid>
    <comment_count>2</comment_count>
    <who name="Ning Zhang">ning.zhang</who>
    <bug_when>2013-08-07 08:43:22 +0000</bug_when>
    <thetext>(In reply to comment #1)
&gt; Should LTP be run on Sato?  Is this a new bug? Have we run this on SATO
&gt; before, I thought this should be run on lsb or basic images that include
&gt; e2fsprogs, I am not sure sato does.

Hi,

Yes, ltp should run on sato-sdk image. This is a new bug for beagleboard. My last test it with 20130618 image, that time the test pass.

The reason why this time it failed, because ltp test code has been updated. The new test case need &quot;mkfs.ext4&quot; command.

We also do this test on 8315E and routerstation BSP, both of these targets test pass. Because they has the &quot;mkfs.ext4&quot; command. 

The beagleboard failed because it doesn&apos;t have e2fsprogs-mke2fs package.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>35471</commentid>
    <comment_count>3</comment_count>
    <who name="Saul Wold">sgw</who>
    <bug_when>2013-08-07 17:52:19 +0000</bug_when>
    <thetext>So this is a new test, core-image-sato is busybox based, which means that most 
tools will be provided by the busybox tools, what&apos;s interesting is you say that 
the MPC and routerstation have those binaries, that should not be the case, are 
you using images from the autobuilder?  I would need to go in and compare how 
those images and how they are created.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>35472</commentid>
    <comment_count>4</comment_count>
    <who name="Saul Wold">sgw</who>
    <bug_when>2013-08-07 17:53:42 +0000</bug_when>
    <thetext>Nevermind I see the image now!</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>35474</commentid>
    <comment_count>5</comment_count>
    <who name="Saul Wold">sgw</who>
    <bug_when>2013-08-07 21:13:17 +0000</bug_when>
    <thetext>Ok, I tracked this down, this is currently expected behavior.  The qemu image 
also do not have mkfs.ext4 (specifically the e2fsprogs-mke2fs package), as they 
don&apos;t have the &quot;ext2&quot; MACHINE_FEATURE.  So this is a new test for LTP that we 
are running on core-image-sato.  I am not sure it makes sense to enable the 
ext2 for sato just for a test. Where else do we run the LTP test suite.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>35481</commentid>
    <comment_count>6</comment_count>
    <who name="Ning Zhang">ning.zhang</who>
    <bug_when>2013-08-08 02:36:41 +0000</bug_when>
    <thetext>Hi Saul,

Just want to make it clearly, I did all the test on &quot;core-image-sato-sdk&quot; image.

Thanks.

(In reply to comment #5)
&gt; Ok, I tracked this down, this is currently expected behavior.  The qemu
&gt; image 
&gt; also do not have mkfs.ext4 (specifically the e2fsprogs-mke2fs package), as
&gt; they 
&gt; don&apos;t have the &quot;ext2&quot; MACHINE_FEATURE.  So this is a new test for LTP that
&gt; we 
&gt; are running on core-image-sato.  I am not sure it makes sense to enable the 
&gt; ext2 for sato just for a test. Where else do we run the LTP test suite.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>35483</commentid>
    <comment_count>7</comment_count>
    <who name="Saul Wold">sgw</who>
    <bug_when>2013-08-08 04:12:13 +0000</bug_when>
    <thetext>So, I discussed this with Mark Hatle and we are in agreement that we don&apos;t want 
to add the mke2fs package to all Sato Images.

We can acceptably say that this test will fail on a given set of platforms 
since they do not include mke2fs package by default. We
do know that it can pass on machines that do use the ext2 MACHINE_FEATURE, 
which installs the e2fsprogs.  So we know that Sato 
can pass these tests.

This is the curse and blessing of flexibility.</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>