<?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>3966</bug_id>
          
          <creation_ts>2013-03-01 09:28:58 +0000</creation_ts>
          <short_desc>[danny 1.3.1] beagleboard/routerstation/mpc8315e: abnormal filesystem-related messages in dmesg when plugging a usb stick</short_desc>
          <delta_ts>2013-11-06 16:31:34 +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>BSPs</product>
          <component>bsps-meta-yocto</component>
          <version>1.3.1</version>
          <rep_platform>All</rep_platform>
          <op_sys>Multiple</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>Low</priority>
          <bug_severity>minor</bug_severity>
          <target_milestone>1.3.2</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Yi Zhao">yi.zhao</reporter>
          <assigned_to name="Bruce Ashfield">bruce.ashfield</assigned_to>
          <cc>dvhart</cc>
    
    <cc>ke.zou</cc>
    
    <cc>ross.burton</cc>
    
    <cc>sgw</cc>
          
          
          <cf_os>---</cf_os>
          <cf_regression_type>---</cf_regression_type>
          
          <cf_docchange>No (bug/feature does not impact docs)</cf_docchange>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>30312</commentid>
    <comment_count>0</comment_count>
    <who name="Yi Zhao">yi.zhao</who>
    <bug_when>2013-03-01 09:28:58 +0000</bug_when>
    <thetext>Location: http://autobuilder.yoctoproject.org/pub/nightly/20130226-2

branch: danny
poky: 98292d1ef1cb44cf96f0a28fbca6439eda55ce1b

This issue is same with bug 3935, but for 1.3.1 branch. So I file a new bug. The usb stick works fine. Can mount, write, read and remount without problem.

Beagleboard:
###########
usb 1-2.4.4: new high-speed USB device number 7 using ehci-omap
scsi0 : usb-storage 1-2.4.4:1.0
scsi 0:0:0:0: Direct-Access     Netac    OnlyDisk         1.00 PQ: 0 ANSI: 2
sd 0:0:0:0: [sda] 2009600 512-byte logical blocks: (1.02 GB/981 MiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 03 00 00 00
sd 0:0:0:0: [sda] No Caching mode page present
sd 0:0:0:0: [sda] Assuming drive cache: write through
sd 0:0:0:0: [sda] No Caching mode page present
sd 0:0:0:0: [sda] Assuming drive cache: write through
 sda: sda1
sd 0:0:0:0: [sda] No Caching mode page present
sd 0:0:0:0: [sda] Assuming drive cache: write through
sd 0:0:0:0: [sda] Attached SCSI removable disk
EXT4-fs (sda): VFS: Can&apos;t find ext4 filesystem
EXT3-fs (sda): error: can&apos;t find ext3 filesystem on dev sda.
EXT2-fs (sda): error: can&apos;t find an ext2 filesystem on dev sda.
FAT-fs (sda): invalid media value (0xb9)
FAT-fs (sda): Can&apos;t find a valid FAT filesystem
VFS: Can&apos;t find a Minix filesystem V1 | V2 | V3 on device sda.
kjournald starting.  Commit interval 5 seconds
EXT3-fs (sda1): using internal journal
EXT3-fs (sda1): recovery complete
EXT3-fs (sda1): mounted filesystem with ordered data mode
###########

Routerstation:
###########EXT4-fs (sda): VFS: Can&apos;t find ext4 filesystem
EXT3-fs (sda): error: can&apos;t find ext3 filesystem on dev sda.
EXT2-fs (sda): error: can&apos;t find an ext2 filesystem on dev sda.
FAT-fs (sda): invalid media value (0xb9)
FAT-fs (sda): Can&apos;t find a valid FAT filesystem
VFS: Can&apos;t find a Minix filesystem V1 | V2 | V3 on device sda.
SQUASHFS error: Can&apos;t find a SQUASHFS superblock on sda
FAT-fs (sda): invalid media value (0xb9)
FAT-fs (sda): Can&apos;t find a valid FAT filesystem
EXT3-fs (sda1): warning: maximal mount count 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 ordered data mode
################

Mpc8315e
################
EXT4-fs (sda): VFS: Can&apos;t find ext4 filesystem
EXT3-fs (sda): error: can&apos;t find ext3 filesystem on dev sda.
EXT2-fs (sda): error: can&apos;t find an ext2 filesystem on dev sda.
FAT-fs (sda): invalid media value (0x00)
FAT-fs (sda): Can&apos;t find a valid FAT filesystem
EXT4-fs (sdb): VFS: Can&apos;t find ext4 filesystem
EXT3-fs (sdb): error: can&apos;t find ext3 filesystem on dev sdb.
EXT2-fs (sdb): error: can&apos;t find an ext2 filesystem on dev sdb.
FAT-fs (sdb): bogus number of reserved sectors
FAT-fs (sdb): Can&apos;t find a valid FAT filesystem
VFS: Can&apos;t find a Minix filesystem V1 | V2 | V3 on device sda.
FAT-fs (sda): invalid media value (0x00)
FAT-fs (sda): Can&apos;t find a valid FAT filesystem
VFS: Can&apos;t find a Minix filesystem V1 | V2 | V3 on device sdb.
FAT-fs (sdb): bogus number of reserved sectors
FAT-fs (sdb): Can&apos;t find a valid FAT filesystem
eth0: no IPv6 routers present
EXT4-fs (sda4): unable to read superblock
EXT3-fs (sda4): error: unable to read superblock
EXT2-fs (sda4): error: unable to read superblock
FAT-fs (sda4): bogus number of reserved sectors
FAT-fs (sda4): Can&apos;t find a valid FAT filesystem
MINIX-fs: unable to read superblock
FAT-fs (sda4): bogus number of reserved sectors
FAT-fs (sda4): Can&apos;t find a valid FAT filesystem
kjournald starting.  Commit interval 5 seconds
EXT3-fs (sdb1): using internal journal
EXT3-fs (sdb1): recovery complete
EXT3-fs (sdb1): mounted filesystem with ordered data mode
################</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>30498</commentid>
    <comment_count>1</comment_count>
    <who name="Bruce Ashfield">bruce.ashfield</who>
    <bug_when>2013-03-07 15:48:48 +0000</bug_when>
    <thetext>We need to identify a resource to fix this. Ack&apos;ing it as a placeholder.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>32845</commentid>
    <comment_count>2</comment_count>
    <who name="Ross Burton">ross.burton</who>
    <bug_when>2013-05-02 14:07:42 +0000</bug_when>
    <thetext>This has been fixed in master so hopefully can be easily backported.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>32869</commentid>
    <comment_count>3</comment_count>
    <who name="Ross Burton">ross.burton</who>
    <bug_when>2013-05-03 10:20:37 +0000</bug_when>
    <thetext>Backported be218292ee3f05afe47545aa8e1625452e0cd614 to my danny-next.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>33106</commentid>
    <comment_count>4</comment_count>
    <who name="Ke Zou">ke.zou</who>
    <bug_when>2013-05-16 07:55:36 +0000</bug_when>
    <thetext>looks like that fix have been merged into danny branch , but issue still exists.

from git log:

commit 881f4b9bdd44bd4849155f54915eb5aed005869d
Author: Saul Wold &lt;sgw@linux.intel.com&gt;
Date:   Sat Apr 13 09:55:55 2013 -0700

    udev-extraconf: Add -o silent to auto mount for mount.util-linux
    
    This will silence some of the noisy output from mount.util-linux and the kernel
    when trying to automount filesystems or devices. Busybox does not accept the silent
    option, it uses a loud option instead.
    
    [YOCTO #3935]
    
    (From OE-Core rev: 796e1390487d602c55467d7654f52e43a4617548)
    
    Signed-off-by: Saul Wold &lt;sgw@linux.intel.com&gt;
    Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>38602</commentid>
    <comment_count>5</comment_count>
    <who name="Bruce Ashfield">bruce.ashfield</who>
    <bug_when>2013-11-06 16:31:34 +0000</bug_when>
    <thetext>The uprev to 3.10 has solved this problem in local testing. Closing the bug.</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>