Linaro Android

Android re-detect microSD card as mmc1 and system crash on imx53loco

Bug #837830 reported by Spring Zhang on 2011-08-31

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Linaro Android	Won't Fix	Undecided	Unassigned

Bug Description

After a suspend(seems to be), microSD card is reported removed but it doesn't, then the card is recognized as mmc1, system crashes. see log.

Environment:
android 11.08 milestone build, #5

Log:

# [ 159.378779] PM: Syncing filesystems ... done.
[ 159.432291] mmc0: card 0fe7 removed
[ 159.477039] Freezing user space processes ...
[ 159.482275] Freezing of user space aborted
[ 159.486931]
[ 159.488490] Restarting tasks ... done.
[ 159.616061] EXT4-fs error (device mmcblk0p3): ext4_find_entry:933: inode #339: comm SurfaceFlinger: reading directory lblock 0
[ 159.627992] EXT4-fs (mmcblk0p3): previous I/O error to superblock detected
[ 159.635235] EXT4-fs error (device mmcblk0p3): ext4_find_entry:933: inode #2: comm SurfaceFlinger: reading directory lblock 0
[ 159.657365] EXT4-fs (mmcblk0p3): previous I/O error to superblock detected
[ 159.664411] EXT4-fs error (device mmcblk0p3): ext4_find_entry:933: inode #339: comm SurfaceFlinger: reading directory lblock 0
[ 160.570782] mmc0: new high speed SDHC card at address 0fe7
[ 160.578386] mmcblk1: mmc0:0fe7 SD04G 3.69 GiB
[ 160.587369] mmcblk1: p1 p2 p3 p4 < p5 p6 p7 >
[ 160.741602] FAT: IO charset iso8859-1 not found
echo $PATH[ 175.678101] EXT4-fs error (device mmcblk0p6): ext4_find_entry:933: inode #98317: comm ThrottleService: reading directory lblock 0
[ 175.690417] EXT4-fs error (device mmcblk0p6): ext4_read_inode_bitmap:160: comm ThrottleService: Cannot read inode bitmap - block_group = 48, inode_bitmap = 393233
[ 175.705043] EXT4-fs error (device mmcblk0p6) in ext4_new_inode:1067: IO failure
[ 175.712369] EXT4-fs (mmcblk0p6): previous I/O error to superblock detected
[ 175.740695] EXT4-fs (mmcblk0p6): previous I/O error to superblock detected
[ 175.747855] EXT4-fs error (device mmcblk0p6): ext4_find_entry:933: inode #98317: comm ThrottleService: reading directory lblock 0
[ 175.790812] alarm_release: clear alarm, pending 0
[ 175.795634] alarm_release: clear alarm, pending 0
[ 175.800345] alarm_release: clear alarm, pending 0
[ 175.831425] init: untracked pid 121 exited
[ 175.857090] EXT4-fs error (device mmcblk0p6): ext4_read_block_bitmap:350: comm Binder Thread #: Cannot read block bitmap - block_group = 4, block_bitmap = 264
[ 175.871389] EXT4-fs error (device mmcblk0p6): ext4_discard_preallocations:3886: comm Binder Thread #: Error reading block bitmap for 4
[ 175.883829] init: untracked pid 122 exited

/sbin:/vendor/bin:/system/sbin:/s[ 175.936045] init: untracked pid 213 exited
ystem/bin:/system/xbin
# [ 176.524889] EXT4-fs (mmcblk0p3): previous I/O error to superblock detected
[ 176.532008] EXT4-fs error (device mmcblk0p3): ext4_find_entry:933: inode #2051: comm zygote: reading directory lblock 0
[ 176.557211] EXT4-fs (mmcblk0p3): previous I/O error to superblock detected
[ 176.574879] EXT4-fs error (device mmcblk0p3): ext4_find_entry:933: inode #2051: comm zygote: reading directory lblock 0
[ 176.596869] EXT4-fs (mmcblk0p3): previous I/O error to superblock detected
[ 176.620590] EXT4-fs error (device mmcblk0p3): ext4_find_entry:933: inode #2051: comm zygote: reading directory lblock 0
[ 176.646926] EXT4-fs (mmcblk0p3): previous I/O error to superblock detected
[ 176.654027] EXT4-fs error (device mmcblk0p3): ext4_find_entry:933: inode #2051: comm zygote: reading directory lblock 0
[ 176.676804] EXT4-fs (mmcblk0p3): previous I/O error to superblock detected
[ 176.694843] EXT4-fs error (device mmcblk0p3): ext4_find_entry:933: inode #2051: comm zygote: reading directory lblock 0
[ 176.716299] EXT4-fs (mmcblk0p3): previous I/O error to superblock detected
[ 176.727919] EXT4-fs error (device mmcblk0p3): ext4_find_entry:933: inode #2051: comm zygote: reading directory lblock 0
[ 176.740479] EXT4-fs (mmcblk0p3): previous I/O error to superblock detected
[ 176.747676] EXT4-fs error (device mmcblk0p3): ext4_find_entry:933: inode #2051: comm zygote: reading directory lblock 0
[ 176.874110] EXT4-fs (mmcblk0p3): previous I/O error to superblock detected
[ 176.881275] EXT4-fs error (device mmcblk0p3): ext4_find_entry:933: inode #391: comm zygote: reading directory lblock 0
[ 177.287696] EXT4-fs (mmcblk0p3): previous I/O error to superblock detected
[ 177.294755] EXT4-fs error (device mmcblk0p3): ext4_find_entry:933: inode #2050: comm zygote: reading directory lblock 0
[ 177.306309] EXT4-fs (mmcblk0p3): previous I/O error to superblock detected
[ 177.313358] EXT4-fs error (device mmcblk0p3): ext4_find_entry:933: inode #2050: comm zygote: reading directory lblock 0
[ 177.324870] EXT4-fs (mmcblk0p3): previous I/O error to superblock detected
[ 177.331934] EXT4-fs error (device mmcblk0p3): ext4_find_entry:933: inode #2050: comm zygote: reading directory lblock 0
[ 177.343298] EXT4-fs (mmcblk0p3): previous I/O error to superblock detected
[ 177.355556] EXT4-fs error (device mmcblk0p3): ext4_find_entry:933: inode #2050: comm zygote: reading directory lblock 0
[ 177.366964] EXT4-fs (mmcblk0p3): previous I/O error to superblock detected
[ 177.374053] EXT4-fs error (device mmcblk0p3): ext4_find_entry:933: inode #2050: comm zygote: reading directory lblock 0
[ 177.385485] EXT4-fs (mmcblk0p3): previous I/O error to superblock detected
[ 177.392528] EXT4-fs error (device mmcblk0p3): ext4_find_entry:933: inode #2050: comm zygote: reading directory lblock 0
[ 177.403929] EXT4-fs (mmcblk0p3): previous I/O error to superblock detected
[ 177.411082] EXT4-fs error (device mmcblk0p3): ext4_find_entry:933: inode #2050: comm zygote: reading directory lblock 0
[ 177.422376] EXT4-fs (mmcblk0p3): previous I/O error to superblock detected
[ 177.429529] EXT4-fs error (device mmcblk0p3): ext4_find_entry:933: inode #2050: comm zygote: reading directory lblock 0
[ 177.440797] EXT4-fs (mmcblk0p3): previous I/O error to superblock detected
[ 177.447955] EXT4-fs error (device mmcblk0p3): ext4_find_entry:933: inode #2050: comm zygote: reading directory lblock 0
[ 177.459471] EXT4-fs (mmcblk0p3): previous I/O error to superblock detected
[ 177.467546] init: untracked pid 388 exited
[ 177.472206] EXT4-fs error (device mmcblk0p3): ext4_find_entry:933: inode #2050: comm zygote: reading directory lblock 0
[ 177.484451] EXT4-fs (mmcblk0p3): previous I/O error to superblock detected
[ 177.492522] init: untracked pid 365 exited
[ 177.497047] EXT4-fs error (device mmcblk0p3): ext4_find_entry:933: inode #2050: comm zygote: reading directory lblock 0
[ 177.509340] init: untracked pid 401 exited
[ 177.514516] init: untracked pid 379 exited
[ 177.519303] EXT4-fs (mmcblk0p3): previous I/O error to superblock detected
[ 177.527451] EXT4-fs error (device mmcblk0p3): ext4_find_entry:933: inode #2050: comm zygote: reading directory lblock 0
[ 177.539842] EXT4-fs (mmcblk0p3): previous I/O error to superblock detected
[ 177.547924] init: untracked pid 323 exited
[ 177.552333] EXT4-fs error (device mmcblk0p3): ext4_find_entry:933: inode #2050: comm zygote: reading directory lblock 0
[ 177.563612] EXT4-fs error (device mmcblk0p6): ext4_read_block_bitmap:350: comm Binder Thread #: Cannot read block bitmap - block_group = 4, block_bitmap = 264
[ 177.577887] EXT4-fs error (device mmcblk0p6): ext4_discard_preallocations:3886: comm Binder Thread #: Error reading block bitmap for 4
[ 177.724113] EXT4-fs (mmcblk0p3): previous I/O error to superblock detected
[ 177.731328] EXT4-fs error (device mmcblk0p3): ext4_find_entry:933: inode #32808: comm zygote: reading directory lblock 0
[ 177.759919] EXT4-fs (mmcblk0p3): previous I/O error to superblock detected
[ 177.767103] EXT4-fs error (device mmcblk0p3): ext4_find_entry:933: inode #391: comm zygote: reading directory lblock 0
[ 177.778225] EXT4-fs (mmcblk0p3): previous I/O error to superblock detected
[ 177.785355] EXT4-fs error (device mmcblk0p3): ext4_find_entry:933: inode #391: comm zygote: reading directory lblock 0
[ 177.851330] EXT4-fs (mmcblk0p3): previous I/O error to superblock detected
[ 177.858496] EXT4-fs error (device mmcblk0p3): ext4_find_entry:933: inode #384: comm zygote: reading directory lblock 0
[ 177.869632] EXT4-fs error (device mmcblk0p6): ext4_read_block_bitmap:350: comm Binder Thread #: Cannot read block bitmap - block_group = 4, block_bitmap = 264
[ 177.883898] EXT4-fs error (device mmcblk0p6): ext4_discard_preallocations:3886: comm Binder Thread #: Error reading block bitmap for 4
[ 177.941411] init: untracked pid 428 exited
[ 177.965161] init: untracked pid 427 exited
[ 178.205784] init: untracked pid 265 exited
[ 178.215508] init: untracked pid 308 exited
[ 178.230676] init: untracked pid 352 exited

# [ 178.346060] init: untracked pid 204 exited
[ 178.368847] init: untracked pid 221 exited

# [ 181.065162] Aborting journal on device mmcblk0p6-8.
[ 181.070152] JBD2: I/O error detected when updating journal superblock for mmcblk0p6-8.

#
# [ 181.431737] init: untracked pid 436 exited
[ 181.455044] init: untracked pid 437 exited
df
[ 182.149133] EXT4-fs (mmcblk0p3): previous I/O error to superblock detected
[ 182.156374] EXT4-fs error (device mmcblk0p3): ext4_find_entry:933: inode #2: comm sh: reading directory lblock 0
df: not found
# df
df: not found
# [ 186.512211] init: untracked pid 446 exited
[ 186.535121] init: untracked pid 445 exited
[ 191.576442] init: untracked pid 456 exited
[ 191.580610] init: untracked pid 457 exited
[ 196.656287] init: untracked pid 465 exited
[ 196.660503] init: untracked pid 466 exited

# [ 201.728815] init: untracked pid 475 exited
[ 201.755211] init: untracked pid 474 exited
[ 206.793773] init: untracked pid 483 exited
[ 206.815040] init: untracked pid 484 exited
[ 211.850250] init: untracked pid 492 exited
[ 211.854418] init: untracked pid 493 exited
[ 216.920012] init: untracked pid 502 exited
[ 216.945250] init: untracked pid 501 exited
[ 222.006274] init: untracked pid 511 exited
[ 222.025214] init: untracked pid 510 exited
[ 226.090132] init: untracked pid 519 exited
[ 226.094299] init: untracked pid 520 exited
[ 231.159280] init: untracked pid 528 exited
[ 231.163449] init: untracked pid 529 exited
[ 236.227850] init: untracked pid 537 exited
[ 236.232020] init: untracked pid 538 exited
[ 241.307988] init: untracked pid 546 exited
[ 241.312155] init: untracked pid 547 exited
[ 246.382194] init: untracked pid 555 exited
[ 246.405053] init: untracked pid 556 exited
[ 251.446305] init: untracked pid 564 exited
[ 251.450472] init: untracked pid 565 exited
[ 256.512172] init: untracked pid 574 exited
[ 256.535115] init: untracked pid 573 exited
[ 261.588830] init: untracked pid 582 exited
[ 261.593000] init: untracked pid 583 exited
[ 266.651988] init: untracked pid 592 exited
[ 266.675120] init: untracked pid 591 exited
[ 271.719316] init: untracked pid 600 exited
[ 271.723485] init: untracked pid 601 exited
[ 276.783279] init: untracked pid 610 exited
[ 276.805114] init: untracked pid 609 exited
[ 281.845577] init: untracked pid 618 exited
[ 281.849793] init: untracked pid 619 exited
[ 286.889242] init: untracked pid 627 exited
[ 286.893410] init: untracked pid 628 exited
[ 291.970395] init: untracked pid 636 exited
[ 291.974562] init: untracked pid 637 exited
[ 296.040264] init: untracked pid 646 exited
[ 296.065262] init: untracked pid 645 exited

Tags:

Spring Zhang (qzhang) on 2011-08-31

summary:

- Android re-detect MMC card as mmc1 on imx53loco
+ Android re-detect microSD card as mmc1 and system crash on imx53loco

Revision history for this message

cmosorccd (cmosorccd) wrote on 2011-09-23:

This issue can be reproduced if USB host driver is enabled.

Revision history for this message

Spring Zhang (qzhang) wrote on 2011-10-10:

Still exists on 11.09 release, and print endless log:

usb wakeup is here
otg host Remote wakeup

tags:

added: imx53

Revision history for this message

Spring Zhang (qzhang) wrote on 2011-10-26:

The endless log may cause by I used a Ripley QS board, but there is still crash issue for DA9052 mx53 QS board.

Revision history for this message

Hong-Xing.Zhu (richard-zhuhongxing) wrote on 2011-12-19: Re: [Bug 837830] Re: Android re-detect microSD card as mmc1 and system crash on imx53loco

Download full text (12.5 KiB)

Pls make sure that the following option is enable in the kernel configuration.
"CONFIG_MMC_UNSAFE_RESUME"

This option should be set to Y when the rootfs is placed on the SD card and
the suspend/resume are supported.

Best Regard
Richard Zhu

On 19 December 2011 15:01, Fathi Boudra <email address hidden> wrote:
> ** Also affects: linaro-landing-team-freescale
> Importance: Undecided
> Status: New
>
> --
> You received this bug notification because you are a member of Linaro
> Landing Team: Freescale, which is subscribed to Linaro Freescale Landing
> Team Project.
> https://bugs.launchpad.net/bugs/837830
>
> Title:
> Android re-detect microSD card as mmc1 and system crash on imx53loco
>
> Status in Linaro Android:
> New
> Status in Linaro Freescale Landing Team Project:
> New
>
> Bug description:
> After a suspend(seems to be), microSD card is reported removed but it
> doesn't, then the card is recognized as mmc1, system crashes. see log.
>
> Environment:
> android 11.08 milestone build, #5
>
> Log:
>
> # [ 159.378779] PM: Syncing filesystems ... done.
> [ 159.432291] mmc0: card 0fe7 removed
> [ 159.477039] Freezing user space processes ...
> [ 159.482275] Freezing of user space aborted
> [ 159.486931]
> [ 159.488490] Restarting tasks ... done.
> [ 159.616061] EXT4-fs error (device mmcblk0p3): ext4_find_entry:933: inode #339: comm SurfaceFlinger: reading directory lblock 0
> [ 159.627992] EXT4-fs (mmcblk0p3): previous I/O error to superblock detected
> [ 159.635235] EXT4-fs error (device mmcblk0p3): ext4_find_entry:933: inode #2: comm SurfaceFlinger: reading directory lblock 0
> [ 159.657365] EXT4-fs (mmcblk0p3): previous I/O error to superblock detected
> [ 159.664411] EXT4-fs error (device mmcblk0p3): ext4_find_entry:933: inode #339: comm SurfaceFlinger: reading directory lblock 0
> [ 160.570782] mmc0: new high speed SDHC card at address 0fe7
> [ 160.578386] mmcblk1: mmc0:0fe7 SD04G 3.69 GiB
> [ 160.587369] mmcblk1: p1 p2 p3 p4 < p5 p6 p7 >
> [ 160.741602] FAT: IO charset iso8859-1 not found
> echo $PATH[ 175.678101] EXT4-fs error (device mmcblk0p6): ext4_find_entry:933: inode #98317: comm ThrottleService: reading directory lblock 0
> [ 175.690417] EXT4-fs error (device mmcblk0p6): ext4_read_inode_bitmap:160: comm ThrottleService: Cannot read inode bitmap - block_group = 48, inode_bitmap = 393233
> [ 175.705043] EXT4-fs error (device mmcblk0p6) in ext4_new_inode:1067: IO failure
> [ 175.712369] EXT4-fs (mmcblk0p6): previous I/O error to superblock detected
> [ 175.740695] EXT4-fs (mmcblk0p6): previous I/O error to superblock detected
> [ 175.747855] EXT4-fs error (device mmcblk0p6): ext4_find_entry:933: inode #98317: comm ThrottleService: reading directory lblock 0
> [ 175.790812] alarm_release: clear alarm, pending 0
> [ 175.795634] alarm_release: clear alarm, pending 0
> [ 175.800345] alarm_release: clear alarm, pending 0
> [ 175.831425] init: untracked pid 121 exited
> [ 175.857090] EXT4-fs error (device mmcblk0p6): ext4_read_block_bitmap:350: comm Binder Thread #: Cannot read block bitmap - block_group = 4, block_bitmap = 264
> [ 175.871389] EXT4-fs error (device ...

Pls make sure that the following option is enable in the kernel configuration.
"CONFIG_MMC_UNSAFE_RESUME"

This option should be set to Y when the rootfs is placed on the SD card and
the suspend/resume are supported.

Best Regard
Richard Zhu

On 19 December 2011 15:01, Fathi Boudra <fathi.boudra@linaro.org> wrote:
> ** Also affects: linaro-landing-team-freescale
>   Importance: Undecided
>       Status: New
>
> --
> You received this bug notification because you are a member of Linaro
> Landing Team: Freescale, which is subscribed to Linaro Freescale Landing
> Team Project.
> https://bugs.launchpad.net/bugs/837830
>
> Title:
>  Android re-detect microSD card as mmc1 and system crash on imx53loco
>
> Status in Linaro Android:
>  New
> Status in Linaro Freescale Landing Team Project:
>  New
>
> Bug description:
>  After a suspend(seems to be), microSD card is reported removed but it
>  doesn't, then the card is recognized as mmc1, system crashes. see log.
>
>  Environment:
>  android 11.08 milestone build, #5
>
>  Log:
>
>  # [  159.378779] PM: Syncing filesystems ... done.
>  [  159.432291] mmc0: card 0fe7 removed
>  [  159.477039] Freezing user space processes ...
>  [  159.482275] Freezing of user space  aborted
>  [  159.486931]
>  [  159.488490] Restarting tasks ... done.
>  [  159.616061] EXT4-fs error (device mmcblk0p3): ext4_find_entry:933: inode #339: comm SurfaceFlinger: reading directory lblock 0
>  [  159.627992] EXT4-fs (mmcblk0p3): previous I/O error to superblock detected
>  [  159.635235] EXT4-fs error (device mmcblk0p3): ext4_find_entry:933: inode #2: comm SurfaceFlinger: reading directory lblock 0
>  [  159.657365] EXT4-fs (mmcblk0p3): previous I/O error to superblock detected
>  [  159.664411] EXT4-fs error (device mmcblk0p3): ext4_find_entry:933: inode #339: comm SurfaceFlinger: reading directory lblock 0
>  [  160.570782] mmc0: new high speed SDHC card at address 0fe7
>  [  160.578386] mmcblk1: mmc0:0fe7 SD04G 3.69 GiB
>  [  160.587369]  mmcblk1: p1 p2 p3 p4 < p5 p6 p7 >
>  [  160.741602] FAT: IO charset iso8859-1 not found
>  echo $PATH[  175.678101] EXT4-fs error (device mmcblk0p6): ext4_find_entry:933: inode #98317: comm ThrottleService: reading directory lblock 0
>  [  175.690417] EXT4-fs error (device mmcblk0p6): ext4_read_inode_bitmap:160: comm ThrottleService: Cannot read inode bitmap - block_group = 48, inode_bitmap = 393233
>  [  175.705043] EXT4-fs error (device mmcblk0p6) in ext4_new_inode:1067: IO failure
>  [  175.712369] EXT4-fs (mmcblk0p6): previous I/O error to superblock detected
>  [  175.740695] EXT4-fs (mmcblk0p6): previous I/O error to superblock detected
>  [  175.747855] EXT4-fs error (device mmcblk0p6): ext4_find_entry:933: inode #98317: comm ThrottleService: reading directory lblock 0
>  [  175.790812] alarm_release: clear alarm, pending 0
>  [  175.795634] alarm_release: clear alarm, pending 0
>  [  175.800345] alarm_release: clear alarm, pending 0
>  [  175.831425] init: untracked pid 121 exited
>  [  175.857090] EXT4-fs error (device mmcblk0p6): ext4_read_block_bitmap:350: comm Binder Thread #: Cannot read block bitmap - block_group = 4, block_bitmap = 264
>  [  175.871389] EXT4-fs error (device mmcblk0p6): ext4_discard_preallocations:3886: comm Binder Thread #: Error reading block bitmap for 4
>  [  175.883829] init: untracked pid 122 exited
>
>  /sbin:/vendor/bin:/system/sbin:/s[  175.936045] init: untracked pid 213 exited
>  ystem/bin:/system/xbin
>  # [  176.524889] EXT4-fs (mmcblk0p3): previous I/O error to superblock detected
>  [  176.532008] EXT4-fs error (device mmcblk0p3): ext4_find_entry:933: inode #2051: comm zygote: reading directory lblock 0
>  [  176.557211] EXT4-fs (mmcblk0p3): previous I/O error to superblock detected
>  [  176.574879] EXT4-fs error (device mmcblk0p3): ext4_find_entry:933: inode #2051: comm zygote: reading directory lblock 0
>  [  176.596869] EXT4-fs (mmcblk0p3): previous I/O error to superblock detected
>  [  176.620590] EXT4-fs error (device mmcblk0p3): ext4_find_entry:933: inode #2051: comm zygote: reading directory lblock 0
>  [  176.646926] EXT4-fs (mmcblk0p3): previous I/O error to superblock detected
>  [  176.654027] EXT4-fs error (device mmcblk0p3): ext4_find_entry:933: inode #2051: comm zygote: reading directory lblock 0
>  [  176.676804] EXT4-fs (mmcblk0p3): previous I/O error to superblock detected
>  [  176.694843] EXT4-fs error (device mmcblk0p3): ext4_find_entry:933: inode #2051: comm zygote: reading directory lblock 0
>  [  176.716299] EXT4-fs (mmcblk0p3): previous I/O error to superblock detected
>  [  176.727919] EXT4-fs error (device mmcblk0p3): ext4_find_entry:933: inode #2051: comm zygote: reading directory lblock 0
>  [  176.740479] EXT4-fs (mmcblk0p3): previous I/O error to superblock detected
>  [  176.747676] EXT4-fs error (device mmcblk0p3): ext4_find_entry:933: inode #2051: comm zygote: reading directory lblock 0
>  [  176.874110] EXT4-fs (mmcblk0p3): previous I/O error to superblock detected
>  [  176.881275] EXT4-fs error (device mmcblk0p3): ext4_find_entry:933: inode #391: comm zygote: reading directory lblock 0
>  [  177.287696] EXT4-fs (mmcblk0p3): previous I/O error to superblock detected
>  [  177.294755] EXT4-fs error (device mmcblk0p3): ext4_find_entry:933: inode #2050: comm zygote: reading directory lblock 0
>  [  177.306309] EXT4-fs (mmcblk0p3): previous I/O error to superblock detected
>  [  177.313358] EXT4-fs error (device mmcblk0p3): ext4_find_entry:933: inode #2050: comm zygote: reading directory lblock 0
>  [  177.324870] EXT4-fs (mmcblk0p3): previous I/O error to superblock detected
>  [  177.331934] EXT4-fs error (device mmcblk0p3): ext4_find_entry:933: inode #2050: comm zygote: reading directory lblock 0
>  [  177.343298] EXT4-fs (mmcblk0p3): previous I/O error to superblock detected
>  [  177.355556] EXT4-fs error (device mmcblk0p3): ext4_find_entry:933: inode #2050: comm zygote: reading directory lblock 0
>  [  177.366964] EXT4-fs (mmcblk0p3): previous I/O error to superblock detected
>  [  177.374053] EXT4-fs error (device mmcblk0p3): ext4_find_entry:933: inode #2050: comm zygote: reading directory lblock 0
>  [  177.385485] EXT4-fs (mmcblk0p3): previous I/O error to superblock detected
>  [  177.392528] EXT4-fs error (device mmcblk0p3): ext4_find_entry:933: inode #2050: comm zygote: reading directory lblock 0
>  [  177.403929] EXT4-fs (mmcblk0p3): previous I/O error to superblock detected
>  [  177.411082] EXT4-fs error (device mmcblk0p3): ext4_find_entry:933: inode #2050: comm zygote: reading directory lblock 0
>  [  177.422376] EXT4-fs (mmcblk0p3): previous I/O error to superblock detected
>  [  177.429529] EXT4-fs error (device mmcblk0p3): ext4_find_entry:933: inode #2050: comm zygote: reading directory lblock 0
>  [  177.440797] EXT4-fs (mmcblk0p3): previous I/O error to superblock detected
>  [  177.447955] EXT4-fs error (device mmcblk0p3): ext4_find_entry:933: inode #2050: comm zygote: reading directory lblock 0
>  [  177.459471] EXT4-fs (mmcblk0p3): previous I/O error to superblock detected
>  [  177.467546] init: untracked pid 388 exited
>  [  177.472206] EXT4-fs error (device mmcblk0p3): ext4_find_entry:933: inode #2050: comm zygote: reading directory lblock 0
>  [  177.484451] EXT4-fs (mmcblk0p3): previous I/O error to superblock detected
>  [  177.492522] init: untracked pid 365 exited
>  [  177.497047] EXT4-fs error (device mmcblk0p3): ext4_find_entry:933: inode #2050: comm zygote: reading directory lblock 0
>  [  177.509340] init: untracked pid 401 exited
>  [  177.514516] init: untracked pid 379 exited
>  [  177.519303] EXT4-fs (mmcblk0p3): previous I/O error to superblock detected
>  [  177.527451] EXT4-fs error (device mmcblk0p3): ext4_find_entry:933: inode #2050: comm zygote: reading directory lblock 0
>  [  177.539842] EXT4-fs (mmcblk0p3): previous I/O error to superblock detected
>  [  177.547924] init: untracked pid 323 exited
>  [  177.552333] EXT4-fs error (device mmcblk0p3): ext4_find_entry:933: inode #2050: comm zygote: reading directory lblock 0
>  [  177.563612] EXT4-fs error (device mmcblk0p6): ext4_read_block_bitmap:350: comm Binder Thread #: Cannot read block bitmap - block_group = 4, block_bitmap = 264
>  [  177.577887] EXT4-fs error (device mmcblk0p6): ext4_discard_preallocations:3886: comm Binder Thread #: Error reading block bitmap for 4
>  [  177.724113] EXT4-fs (mmcblk0p3): previous I/O error to superblock detected
>  [  177.731328] EXT4-fs error (device mmcblk0p3): ext4_find_entry:933: inode #32808: comm zygote: reading directory lblock 0
>  [  177.759919] EXT4-fs (mmcblk0p3): previous I/O error to superblock detected
>  [  177.767103] EXT4-fs error (device mmcblk0p3): ext4_find_entry:933: inode #391: comm zygote: reading directory lblock 0
>  [  177.778225] EXT4-fs (mmcblk0p3): previous I/O error to superblock detected
>  [  177.785355] EXT4-fs error (device mmcblk0p3): ext4_find_entry:933: inode #391: comm zygote: reading directory lblock 0
>  [  177.851330] EXT4-fs (mmcblk0p3): previous I/O error to superblock detected
>  [  177.858496] EXT4-fs error (device mmcblk0p3): ext4_find_entry:933: inode #384: comm zygote: reading directory lblock 0
>  [  177.869632] EXT4-fs error (device mmcblk0p6): ext4_read_block_bitmap:350: comm Binder Thread #: Cannot read block bitmap - block_group = 4, block_bitmap = 264
>  [  177.883898] EXT4-fs error (device mmcblk0p6): ext4_discard_preallocations:3886: comm Binder Thread #: Error reading block bitmap for 4
>  [  177.941411] init: untracked pid 428 exited
>  [  177.965161] init: untracked pid 427 exited
>  [  178.205784] init: untracked pid 265 exited
>  [  178.215508] init: untracked pid 308 exited
>  [  178.230676] init: untracked pid 352 exited
>
>  # [  178.346060] init: untracked pid 204 exited
>  [  178.368847] init: untracked pid 221 exited
>
>  # [  181.065162] Aborting journal on device mmcblk0p6-8.
>  [  181.070152] JBD2: I/O error detected when updating journal superblock for mmcblk0p6-8.
>
>  #
>  # [  181.431737] init: untracked pid 436 exited
>  [  181.455044] init: untracked pid 437 exited
>  df
>  [  182.149133] EXT4-fs (mmcblk0p3): previous I/O error to superblock detected
>  [  182.156374] EXT4-fs error (device mmcblk0p3): ext4_find_entry:933: inode #2: comm sh: reading directory lblock 0
>  df: not found
>  # df
>  df: not found
>  # [  186.512211] init: untracked pid 446 exited
>  [  186.535121] init: untracked pid 445 exited
>  [  191.576442] init: untracked pid 456 exited
>  [  191.580610] init: untracked pid 457 exited
>  [  196.656287] init: untracked pid 465 exited
>  [  196.660503] init: untracked pid 466 exited
>
>  # [  201.728815] init: untracked pid 475 exited
>  [  201.755211] init: untracked pid 474 exited
>  [  206.793773] init: untracked pid 483 exited
>  [  206.815040] init: untracked pid 484 exited
>  [  211.850250] init: untracked pid 492 exited
>  [  211.854418] init: untracked pid 493 exited
>  [  216.920012] init: untracked pid 502 exited
>  [  216.945250] init: untracked pid 501 exited
>  [  222.006274] init: untracked pid 511 exited
>  [  222.025214] init: untracked pid 510 exited
>  [  226.090132] init: untracked pid 519 exited
>  [  226.094299] init: untracked pid 520 exited
>  [  231.159280] init: untracked pid 528 exited
>  [  231.163449] init: untracked pid 529 exited
>  [  236.227850] init: untracked pid 537 exited
>  [  236.232020] init: untracked pid 538 exited
>  [  241.307988] init: untracked pid 546 exited
>  [  241.312155] init: untracked pid 547 exited
>  [  246.382194] init: untracked pid 555 exited
>  [  246.405053] init: untracked pid 556 exited
>  [  251.446305] init: untracked pid 564 exited
>  [  251.450472] init: untracked pid 565 exited
>  [  256.512172] init: untracked pid 574 exited
>  [  256.535115] init: untracked pid 573 exited
>  [  261.588830] init: untracked pid 582 exited
>  [  261.593000] init: untracked pid 583 exited
>  [  266.651988] init: untracked pid 592 exited
>  [  266.675120] init: untracked pid 591 exited
>  [  271.719316] init: untracked pid 600 exited
>  [  271.723485] init: untracked pid 601 exited
>  [  276.783279] init: untracked pid 610 exited
>  [  276.805114] init: untracked pid 609 exited
>  [  281.845577] init: untracked pid 618 exited
>  [  281.849793] init: untracked pid 619 exited
>  [  286.889242] init: untracked pid 627 exited
>  [  286.893410] init: untracked pid 628 exited
>  [  291.970395] init: untracked pid 636 exited
>  [  291.974562] init: untracked pid 637 exited
>  [  296.040264] init: untracked pid 646 exited
>  [  296.065262] init: untracked pid 645 exited
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/linaro-android/+bug/837830/+subscriptions

-- 
Richard Zhu
Best Regards

Revision history for this message

Fathi Boudra (fboudra) wrote on 2011-12-19:

On 19 December 2011 09:16, Hong-Xing.Zhu wrote:
> Pls make sure that the following option is enable in the kernel configuration.
> "CONFIG_MMC_UNSAFE_RESUME"
>
> This option should be set to Y when the rootfs is placed on the SD card and
> the suspend/resume are supported.

The option is set in the latest image:
http://android-build.linaro.org/builds/~linaro-android/staging-imx53-11.12-release/7/kernel_config
[...]
CONFIG_MMC_UNSAFE_RESUME=y

Revision history for this message

Amit Pundir (pundiramit) wrote on 2011-12-29:

Marking Gingerbread open bugs to "Won't fix" state (on Linaro-Android helpdesk) as fixes are done only on ICS track now. Please raise this bug again against latest Linaro-ICS release if it still exist.

Changed in linaro-android:
status:	New → Won't Fix

Revision history for this message

Guodong Xu (guodong-xu) wrote on 2012-04-20:

These two issues share the same root-cause:
#824517 Power management shuts down the root filesystem on i.MX53 Android
#837830 Android re-detect microSD card as mmc1 and system crash on imx53loco

As said above, because i.MX53 Quickstart board uses SD card to host its rootfs. In that case, need to enable "CONFIG_MMC_UNSAFE_RESUME".

This bug is considered fix released. as confirmed by Fathi: The option is set in the latest image:
http://android-build.linaro.org/builds/~linaro-android/staging-imx53-11.12-release/7/kernel_config

Changed in linaro-landing-team-freescale:
status:	New → Fix Released

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Related blueprints

Ensure lava can deploy android images on mx53 boards

Remote bug watches

Bug watches keep track of this bug in other bug trackers.