This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Problem with MMC access while mounting the root file system.

Other Parts Discussed in Thread: TS3A27518E, AM1808

Hello All,

We have  am335x based board. We trying to boot the kernel and mount the root file system. The u-boot loads the kernel perfectly with access the MMC initially, but when kernel starts to access the MMC block p2 to mount the file system . We got the errors of the I/O related to MMC. The file system doesnot read properly, due to this its not mounted propery, but sometime we got the root prompt.

We formated the card twice, and also changed the card . but  we faced some problems. can you please tell us what might be the problem. How we make the diagnostic for same.

The error logs as follows.

[    1.568237] TCP cubic registered
[    1.571594] NET: Registered protocol family 17
[    1.576263] can: controller area network core (rev 20090105 abi 8)
[    1.582794] NET: Registered protocol family 29
[    1.587432] can: raw protocol (rev 20090105)
[    1.591918] can: broadcast manager protocol (rev 20090105 t)
[    1.597839] Registering the dns_resolver key type
[    1.602874] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
[    1.610870] ThumbEE CPU extension supported.
[    1.615386] mux: Failed to setup hwmod io irq -22
[    1.620910] Power Management for AM33XX family
[    1.625762] Trying to load am335x-pm-firmware.bin (60 secs timeout)
[    1.632415] Copied the M3 firmware to UMEM
[    1.636718] omap_hwmod: wkup_m3: wkup_m3: hwmod data error: OMAP4 does not support st_shift
[    1.650512] clock: disabling unused clocks to save power
[    1.658050] Random MACID=72:c0:dc:a1:6:19
[    1.663757] omap_rtc omap_rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800)
[    1.672943] Waiting for root device /dev/mmcblk0p2...
[    1.714874] mmc0: new high speed SDHC card at address 1234
[    1.721221] mmcblk0: mmc0:1234 SA04G 3.63 GiB
[    1.728149]  mmcblk0: p1 p2 p3
[    3.177703] mmcblk0: error -84 transferring data, sector 1737490, nr 128, cmd response 0x900, card status 0xb00
[    3.188537] mmcblk0: retrying using single block read
[    3.830841] kjournald starting.  Commit interval 5 seconds
[    3.836608] EXT3-fs (mmcblk0p2): warning: ext3_clear_journal_err: Filesystem error recorded from previous mount: IO failure
[    3.848205] EXT3-fs (mmcblk0p2): warning: ext3_clear_journal_err: Marking fs in need of filesystem check.
[    3.868041] EXT3-fs (mmcblk0p2): warning: mounting fs with errors, running e2fsck is recommended
[    3.879882] EXT3-fs (mmcblk0p2): using internal journal
[    3.885345] EXT3-fs (mmcblk0p2): recovery complete
[    3.893157] EXT3-fs (mmcblk0p2): mounted filesystem with ordered data mode
[    3.900390] VFS: Mounted root (ext3 filesystem) on device 179:2.
[    3.907012] Freeing init memory: 244K
INIT: version 2.86 booting
Please wait: booting...
Starting udev
[    5.734405] mmcblk0: error -84 transferring data, sector 3306402, nr 8, cmd response 0x900, card status 0xb00
[    5.744812] mmcblk0: retrying using single block read
[    5.853393] udevd (691): /proc/691/oom_adj is deprecated, please use /proc/691/oom_score_adj instead.
[    8.165405] mmcblk0: error -84 transferring data, sector 288, nr 128, cmd response 0x900, card status 0xb00
[    8.175994] mmcblk0: retrying using single block read
[   12.345031] mmcblk0: error -84 transferring data, sector 7614578, nr 64, cmd response 0x900, card status 0xb00
[   12.355712] mmcblk0: retrying using single block read
[   12.411346] mmcblk0: error -84 transferring data, sector 3630786, nr 128, cmd response 0x900, card status 0xb00
[   12.422271] mmcblk0: retrying using single block read
[   13.968017] mmcblk0: error -84 transferring data, sector 1104442, nr 32, cmd response 0x900, card status 0xb00
[   13.978576] mmcblk0: retrying using single block read
[   16.796966] mmcblk0: error -84 transferring data, sector 2520914, nr 40, cmd response 0x900, card status 0xc00
[   16.808288] end_request: I/O error, dev mmcblk0, sector 2520949
[   16.814453] Buffer I/O error on device mmcblk0p2, logical block 295037
[   16.821258] lost page write due to I/O error on mmcblk0p2
[   19.014160] mmcblk0: error -84 transferring data, sector 3630690, nr 128, cmd response 0x900, card status 0xb00
[   19.025085] mmcblk0: retrying using single block read
[   24.760223] mmcblk0: error -84 transferring data, sector 1738074, nr 128, cmd response 0x900, card status 0xc00
[   24.771636] end_request: I/O error, dev mmcblk0, sector 1738127
[   24.777801] end_request: I/O error, dev mmcblk0, sector 1738130
[   24.783966] end_request: I/O error, dev mmcblk0, sector 1738138
[   24.790130] end_request: I/O error, dev mmcblk0, sector 1738146
[   24.796325] end_request: I/O error, dev mmcblk0, sector 1738154
[   24.802490] end_request: I/O error, dev mmcblk0, sector 1738162
[   24.808654] end_request: I/O error, dev mmcblk0, sector 1738170
[   24.814819] end_request: I/O error, dev mmcblk0, sector 1738178
[   24.820983] end_request: I/O error, dev mmcblk0, sector 1738186
[   24.827148] end_request: I/O error, dev mmcblk0, sector 1738194
[   24.840820] Aborting journal on device mmcblk0p2.
[   27.696899] EXT3-fs (mmcblk0p2): error: ext3_journal_start_sb: Detected aborted journal
[   27.705322] EXT3-fs (mmcblk0p2): error: remounting filesystem read-only
[   29.102722] mmcblk0: error -84 transferring data, sector 3630690, nr 128, cmd response 0x900, card status 0xb00
[   29.113647] mmcblk0: retrying using single block read
[   30.588378] mmcblk0: error -84 transferring data, sector 7614578, nr 64, cmd response 0x900, card status 0xb00
[   30.598999] mmcblk0: retrying using single block read
[   30.659118] kjournald starting.  Commit interval 5 seconds
[   31.374298] EXT3-fs (mmcblk0p3): using internal journal
[   31.379730] EXT3-fs (mmcblk0p3): recovery complete
[   31.384765] EXT3-fs (mmcblk0p3): mounted filesystem with ordered data mode
[   31.459106] alignment: ignoring faults is unsafe on this CPU.  Defaulting to fixup mode.
Remounting root file system...
[   31.522735] EXT3-fs (mmcblk0p2): error: ext3_remount: Abort forced by user
mount: you must specify the filesystem type
Caching udev devnodes
ALSA: Restoring mixer settings...
[   33.296478] mmcblk0: error -84 transferring data, sector 1104290, nr 80, cmd response 0x900, card status 0xb00
[   33.307098] mmcblk0: retrying using single block read
Collected errors:
 * opkg_conf_load: Could not create lock file /usr/lib/opkg/lock: Read-only file system.
No state is present for card EVM
Found hardware: "AM335X_EVM" "" "" "" ""
Hardware is initialized using a generic method
No state is present for card EVM
rm: cannot remove '/etc/rcS.d/S40configure': Read-only file system
Configuring network interfaces... [   35.557891] PHY 0:06 not found
[   35.561096] PHY 0:07 not found
eth0      no wireless extensions.

udhcpc (v1.13.2) started
[   37.006103] mmcblk0: error -84 transferring data, sector 2933442, nr 128, cmd response 0x900, card status 0xb00
[   37.016967] mmcblk0: retrying using single block read
Sending discover...
Sending discover...
Sending discover...
No lease, forking to background
done.
Setting up IP spoofing protection: rp_filter.
rm: cannot remove '/tmp/.automount-mmcblk0p3': Read-only file system
rm: cannot remove '/tmp/.automount-mmcblk0p1': Read-only file system
rm: cannot remove '/tmp/.automount-mmcblk0p2': Read-only file system
rm: cannot remove '/tmp': Read-only file system
ln: /tmp/tmp: Read-only file system
Wed Apr 11 08:27:00 UTC 2012
INIT: Entering runlevel: 5/S99finish.sh: line 5: can't create /e
mkdir: cannot create directory '/var/lib/dbus': Read-only file system
mkdir: cannot create directory '/var/lib/dropbear': Read-only file system
Creating Dropbear SSH server RSA host key.
Will output 1024 bit rsa secret key to '/var/lib/dropbear/dropbear_rsa_host_key'
Generating key, this may take a while...
Couldn't create new file /var/lib/dropbear/dropbear_rsa_host_key
Reason: No such file or directory
Starting Dropbear SSH server: dropbear.
Starting telnet daemon.
Starting network benchmark server: netserver.
Starting syslogd/klogd: done
Starting thttpd[   48.564880] mmcblk0: error -84 transferring data, sector 3562946, nr 72, cmd response 0x900, card status 0xb00
[   48.575500] mmcblk0: retrying using single block read
.
Starting PVR
Usage: insmod filename [args]
Could not find pvrsrvkm driver
Starting Lighttpd Web Server: [   50.151123] mmcblk0: error -84 transferring data, sector 3558274, nr 64, cmd response 0x900, card status 0xb00
[   50.161773] mmcblk0: retrying using single block read
lighttpd.
2012-04-11 08:27:03: (log.c.166) server started
/
Starting Matrix GUI application.
FATAL: Module g_mass_storage not found.
***************************************************************
***************************************************************
NOTICE: This file system contains the followin GPLv3 packages:
        binutils-symlinks
        binutils
        gdbserver

If you do not wish to distribute GPLv3 components please remove
the above packages prior to distribution.  This can be done using
the opkg remove command.  i.e.:
    opkg remove <package>
Where <package> is the name printed in the list above

NOTE: If the package is a dependency of another package you
      will be notified of the dependent packages.  You should
      use the --force-removal-of-dependent-packages option to
      also remove the dependent packages as well
***************************************************************
***************************************************************

 _____                    _____           _         _
|  _  |___ ___ ___ ___   |  _  |___ ___  |_|___ ___| |_
|     |  _| .'| . | . |  |   __|  _| . | | | -_|  _|  _|
|__|__|_| |__,|_  |___|  |__|  |_| |___|_| |___|___|_|
              |___|                    |___|

Arago Project http://arago-project.org am335x-evm ttyO2

Arago 2011.09 am335x-evm ttyO2

am335x-evm login:
 _____

  • Have you tried a different SD card?  Perhaps your card is going bad.

    Also, how did you create this SD card?

    Chase

  • Hi Chase,

    Yes,  actually we thought same,  that problem with SD card. So we format the card of  4GB and create the three partitions using the script mk3partions two times. also we took new card and format the card, but problems remains same.  It looks like the timing issue of SD/MMC. In design we used the MUX  (TS3A27518E) in between the AM335x processor and SD device.

    Is there need to change in the kernel code.?....but firmly we think the timing issue.like dto value.

    We working on the latest branch of kernel linux-am335x - v3.2 staging.

    Can you pls give the suggetions on same?

     

  • Surendra,

    Latest kernel should be using a DTO of 14 which is the maximum value.  Reformatting the card will have little effect if the card is going bad.  You could try doing a "
    dd" to the card to see if you find un-usable sections.  Or just try a different SD card.

    Chase

  • Hi Chase,

    The problem is resolved. On the proto board, some issue with the resistor value, One resistor in series with the CLK signal. Due to this change in the generated freq.

    Now its fine.

    Thanks for your valuable suggetions.

    Surendra

  • Surendra,


    Glad to hear this is resolved.

    Chase

  • Hi All,

     

    I am working on AM1808 platform and running my OS & Fileystem from 4GB SD-Card.

     

    After working 2-3 months time I am getting the below errors randomly in all my devices.

     

    Please suggest me how to resolve my issue. find the errors:

    mmcblk0: error -110 transferring data, sector 4993944, nr 8, card status 0x80900
    end_request: I/O error, dev mmcblk0, sector 4993944
    mmcblk0: error -110 transferring data, sector 4993945, nr 7, card status 0x80900
    end_request: I/O error, dev mmcblk0, sector 4993945
    mmcblk0: error -110 transferring data, sector 4993946, nr 6, card status 0x80900
    end_request: I/O error, dev mmcblk0, sector 4993946
    mmcblk0: error -110 transferring data, sector 4993947, nr 5, card status 0x80900
    end_request: I/O error, dev mmcblk0, sector 4993947
    mmcblk0: error -110 transferring data, sector 4993948, nr 4, card status 0x80900
    end_request: I/O error, dev mmcblk0, sector 4993948
    mmcblk0: error -110 transferring data, sector 4993949, nr 3, card status 0x80900
    end_request: I/O error, dev mmcblk0, sector 4993949
    mmcblk0: error -110 transferring data, sector 4993950, nr 2, card status 0x80900
    end_request: I/O error, dev mmcblk0, sector 4993950
    mmcblk0: error -110 transferring data, sector 4993951, nr 1, card status 0x80900
    end_request: I/O error, dev mmcblk0, sector 4993951
    mmcblk0: retrying using single block read
    mmcblk0: error -110 transferring data, sector 4993944, nr 8, card status 0x80900
    end_request: I/O error, dev mmcblk0, sector 4993944
    mmcblk0: error -110 transferring data, sector 4993945, nr 7, card status 0x80900
    end_request: I/O error, dev mmcblk0, sector 4993945
    mmcblk0: error -110 transferring data, sector 4993946, nr 6, card status 0x80900
    end_request: I/O error, dev mmcblk0, sector 4993946
    mmcblk0: error -110 transferring data, sector 4993947, nr 5, card status 0x80900
    end_request: I/O error, dev mmcblk0, sector 4993947
    mmcblk0: error -110 transferring data, sector 4993948, nr 4, card status 0x80900
    end_request: I/O error, dev mmcblk0, sector 4993948
    mmcblk0: error -110 transferring data, sector 4993949, nr 3, card status 0x80900
    end_request: I/O error, dev mmcblk0, sector 4993949
    mmcblk0: error -110 transferring data, sector 4993950, nr 2, card status 0x80900
    end_request: I/O error, dev mmcblk0, sector 4993950
    mmcblk0: error -110 transferring data, sector 4993951, nr 1, card status 0x80900
    end_request: I/O error, dev mmcblk0, sector 4993951
    mmcblk0: retrying using single block read
    mmcblk0: error -110 transferring data, sector 4993944, nr 8, card status 0x80900
    end_request: I/O error, dev mmcblk0, sector 4993944
    mmcblk0: error -110 transferring data, sector 4993945, nr 7, card status 0x80900
    end_request: I/O error, dev mmcblk0, sector 4993945
    mmcblk0: error -110 transferring data, sector 4993946, nr 6, card status 0x80900
    end_request: I/O error, dev mmcblk0, sector 4993946
    mmcblk0: error -110 transferring data, sector 4993947, nr 5, card status 0x80900
    end_request: I/O error, dev mmcblk0, sector 4993947
    mmcblk0: error -110 transferring data, sector 4993948, nr 4, card status 0x80900
    end_request: I/O error, dev mmcblk0, sector 4993948
    mmcblk0: error -110 transferring data, sector 4993949, nr 3, card status 0x80900
    end_request: I/O error, dev mmcblk0, sector 4993949
    mmcblk0: error -110 transferring data, sector 4993950, nr 2, card status 0x80900
    end_request: I/O error, dev mmcblk0, sector 4993950
    mmcblk0: error -110 transferring data, sector 4993951, nr 1, card status 0x80900
    end_request: I/O error, dev mmcblk0, sector 4993951
    mmcblk0: retrying using single block read
    mmcblk0: error -110 transferring data, sector 4993944, nr 8, card status 0x80900
    end_request: I/O error, dev mmcblk0, sector 4993944
    mmcblk0: error -110 transferring data, sector 4993945, nr 7, card status 0x80900
    end_request: I/O error, dev mmcblk0, sector 4993945
    mmcblk0: error -110 transferring data, sector 4993946, nr 6, card status 0x80900
    end_request: I/O error, dev mmcblk0, sector 4993946
    mmcblk0: error -110 transferring data, sector 4993947, nr 5, card status 0x80900
    end_request: I/O error, dev mmcblk0, sector 4993947
    mmcblk0: error -110 transferring data, sector 4993948, nr 4, card status 0x80900
    end_request: I/O error, dev mmcblk0, sector 4993948
    mmcblk0: error -110 transferring data, sector 4993949, nr 3, card status 0x80900
    end_request: I/O error, dev mmcblk0, sector 4993949
    mmcblk0: error -110 transferring data, sector 4993950, nr 2, card status 0x80900
    end_request: I/O error, dev mmcblk0, sector 4993950
    mmcblk0: error -110 transferring data, sector 4993951, nr 1, card status 0x80900

     

    Thanks,

  • Hi Lofna,

    Did you find solution for the described phenomena? although I'm working with different processor I got the same messages out of the blue.

    Thanks,

    Arie.

  • Hi,

    copy these lines on top of the file /etc/rcS.d/S01psplash

    umount /

    e2fsck -y /dev/mmcblk0p2

    mount -rw -o remount /

  • Hi Sreenivas,

    It is the same as signing the partition to be checked every mount but that's mean a check disk will run every restart and can take between few seconds to few minutes.

    It cause the boot time of the device to be much longer. Do you have any suggestion how to run check disk without extend the boot time?

    Thanks,

    Arie.

  • Hi,

    What you said was correct it will increase the boot time, but if we don't perform this checking it may cause critical data loss, thought it causes boot delay, but it can greatly improve your system stability.

    As you asked i dint have any suggestion to run check disk without extending the boot time, if you found please share.