Samsung origen 4412 board is not resume from suspend state

Bug #1157152 reported by Soumya Basak
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Linaro Android
Won't Fix
Undecided
Unassigned

Bug Description

on our Samsung origen 4412 boards with Linaro-android jellybean builds

https://android-build.linaro.org/builds/~linaro-android-member-samsung/origenquad-linaro/#build=110

after the board going to suspend mode, hit F1 or ESC for keyboard or mouse click, the board never come out of suspend state.

log details here:

root@android:/ # [ 70.225000] PM: Syncing filesystems ... done.
[ 70.255000] mmc0: card e624 removed
[ 70.285000] Freezing user space processes ... [ 70.305000] EXT4-fs error (device mmcblk0p6): __ext4_get_inode_loc:3764: inode #252: block
323: comm d.process.media: unable to read itable block
[ 70.355000] Aborting journal on device mmcblk0p6-8.
[ 70.360000] JBD2: Error -5 detected when updating journal superblock for mmcblk0p6-8.
[ 70.365000] Kernel panic - not syncing: EXT4-fs (device mmcblk0p6): panic forced after error
[ 70.365000]
[ 70.365000] [<c00153e4>] (unwind_backtrace+0x0/0xf8) from [<c04c9f38>] (panic+0x90/0x1e8)
[ 70.365000] [<c04c9f38>] (panic+0x90/0x1e8) from [<c01865a4>] (ext4_handle_error+0x68/0xa4)
[ 70.365000] [<c01865a4>] (ext4_handle_error+0x68/0xa4) from [<c01868c4>] (ext4_error_inode+0xa4/0xfc)
[ 70.365000] [<c01868c4>] (ext4_error_inode+0xa4/0xfc) from [<c0166f68>] (__ext4_get_inode_loc+0x1f0/0x488)
[ 70.365000] [<c0166f68>] (__ext4_get_inode_loc+0x1f0/0x488) from [<c016bb6c>] (ext4_reserve_inode_write+0x1c/0x7c)
[ 70.365000] [<c016bb6c>] (ext4_reserve_inode_write+0x1c/0x7c) from [<c016bc08>] (ext4_mark_inode_dirty+0x3c/0x1f4)
[ 70.365000] [<c016bc08>] (ext4_mark_inode_dirty+0x3c/0x1f4) from [<c016e2fc>] (ext4_dirty_inode+0x28/0x40)
[ 70.365000] [<c016e2fc>] (ext4_dirty_inode+0x28/0x40) from [<c0105780>] (__mark_inode_dirty+0x2c/0x1d0)
[ 70.365000] [<c0105780>] (__mark_inode_dirty+0x2c/0x1d0) from [<c00f84d0>] (update_time+0x6c/0x9c)
[ 70.365000] [<c00f84d0>] (update_time+0x6c/0x9c) from [<c00f85a4>] (file_update_time+0xa4/0xf4)
[ 70.365000] [<c00f85a4>] (file_update_time+0xa4/0xf4) from [<c00a6950>] (__generic_file_aio_write+0x1c0/0x448)
[ 70.365000] [<c00a6950>] (__generic_file_aio_write+0x1c0/0x448) from [<c00a6c3c>] (generic_file_aio_write+0x64/0xd4)
[ 70.365000] [<c00a6c3c>] (generic_file_aio_write+0x64/0xd4) from [<c01638f4>] (ext4_file_write+0xb4/0x490)
[ 70.365000] [<c01638f4>] (ext4_file_write+0xb4/0x490) from [<c00e1c44>] (do_sync_write+0x94/0xd4)
[ 70.365000] [<c00e1c44>] (do_sync_write+0x94/0xd4) from [<c00e23a8>] (vfs_write+0x9c/0x140)
[ 70.365000] [<c00e23a8>] (vfs_write+0x9c/0x140) from [<c00e2760>] (sys_pwrite64+0x6c/0x8c)
[ 70.365000] [<c00e2760>] (sys_pwrite64+0x6c/0x8c) from [<c000e2c0>] (ret_fast_syscall+0x0/0x30)

~~ the same issue is reproduced with the builds

https://android-build.linaro.org/builds/~linaro-android-member-samsung/origenquad-linaro-13.03-release/

https://android-build.linaro.org/builds/~linaro-android-member-samsung/origenquad-linaro/#build=130

https://android-build.linaro.org/builds/~linaro-android-member-samsung/origenquad-linaro/#build=137

https://android-build.linaro.org/builds/~linaro-android-member-samsung/origenquad-linaro-13.04-release/

description: updated
description: updated
description: updated
description: updated
Revision history for this message
vishal (vishalbhoj) wrote :

Origen quad is no more supported and hence marking the bug as won't fix

Changed in linaro-android:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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