* iMX6SL Suspend mode (S3)
@ 2014-01-24 21:14 John Tobias
2014-01-24 21:24 ` Russell King - ARM Linux
0 siblings, 1 reply; 3+ messages in thread
From: John Tobias @ 2014-01-24 21:14 UTC (permalink / raw)
To: linux-arm-kernel
Hello all,
I am testing the suspend mode (S3) for my custom board with iMX6SL and
the iMX6SL EVK as well. I am using 3.13 kernel, eMMC and MMC for the
storage and systemd to control the OS. If I put my device in S3 mode,
I got the following messages:
[ 27.949393] PM: Syncing filesystems ... done.
[ 27.972392] mmc0: card 0001 removed
[ 28.033613] end_request: I/O error, dev mmcblk0, sector 0
[ 28.063493] end_request: I/O error, dev mmcblk0, sector 0
[ 28.107933] end_request: I/O error, dev mmcblk0, sector 0
[ 28.131456] end_request: I/O error, dev mmcblk0, sector 0
[ 28.153651] end_request: I/O error, dev mmcblk0, sector 0
[ 28.215530] Freezing user space processes ... (elapsed 0.001 seconds) done.
[ 28.224284] Freezing remaining freezable tasks ... (elapsed 0.001
seconds) done.
[ 28.233658] Suspending console(s) (use no_console_suspend to debug)
If I press any key, it will wake up. But, I got the following errors:
[ 17.815008] mmc0: new high speed DDR MMC card at address 0001
[ 17.828024] mmcblk0: mmc0:0001 SEM04G 3.68 GiB
[ 17.833522] mmcblk0boot0: mmc0:0001 SEM04G partition 1 2.00 MiB
[ 17.839699] mmcblk0boot1: mmc0:0001 SEM04G partition 2 2.00 MiB
[ 17.847150] mmcblk0rpmb: mmc0:0001 SEM04G partition 3 2.00 MiB
[ 17.860116] mmcblk0: p1 p2 p3 p4 < p5 p6 >
[ 17.883550] mmcblk0boot1: unknown partition table
[ 17.899549] mmcblk0boot0: unknown partition table
[ 17.959186] EXT4-fs error (device mmcblk0p2):
__ext4_get_inode_loc:3909: inode #33300: block 131267: comm systemd:
unable to read itable block
[ 18.126790] EXT4-fs error (device mmcblk0p2):
__ext4_get_inode_loc:3909: inode #33300: block 131267: comm systemd:
unable to read itable block
[ 18.173370] EXT4-fs error (device mmcblk0p2):
__ext4_get_inode_loc:3909: inode #33300: block 131267: comm systemd:
unable to read itable block
[ 18.207744] EXT4-fs error (device mmcblk0p2):
__ext4_get_inode_loc:3909: inode #33300: block 131267: comm systemd:
unable to read itable block
[ 18.316736] EXT4-fs error (device mmcblk0p2):
__ext4_get_inode_loc:3909: inode #33300: block 131267: comm systemd:
unable to read itable block
[ 18.448542] EXT4-fs error (device mmcblk0p2):
__ext4_get_inode_loc:3909: inode #33300: block 131267: comm systemd:
unable to read itable block
[ 18.496749] EXT4-fs error (device mmcblk0p2):
__ext4_get_inode_loc:3909: inode #33300: block 131267: comm systemd:
unable to read itable block
[ 18.530178] EXT4-fs error (device mmcblk0p2):
__ext4_get_inode_loc:3909: inode #33300: block 131267: comm systemd:
unable to read itable block
[ 18.575861] EXT4-fs error (device mmcblk0p2):
__ext4_get_inode_loc:3909: inode #33300: block 131267: comm systemd:
unable to read itable block
[ 18.660139] EXT4-fs warning (device mmcblk0p2):
__ext4_read_dirblock:908: error reading directory block (ino 33142,
block 0)
[ 18.717386] EXT4-fs warning (device mmcblk0p2):
__ext4_read_dirblock:681: error reading directory block (ino 2001,
block 0)
[ 18.830148] EXT4-fs warning (device mmcblk0p2):
__ext4_read_dirblock:908: error reading directory block (ino 33135,
block 0)
[ 19.045944] EXT4-fs warning (device mmcblk0p2):
__ext4_read_dirblock:681: error reading directory block (ino 32928,
block 0)
[ 19.058510] EXT4-fs warning (device mmcblk0p2):
__ext4_read_dirblock:681: error reading directory block (ino 32928,
block 0)
[ 19.071681] EXT4-fs warning (device mmcblk0p2):
__ext4_read_dirblock:681: error reading directory block (ino 90, block
0)
[ 19.083810] EXT4-fs warning (device mmcblk0p2):
__ext4_read_dirblock:681: error reading directory block (ino 90, block
0)
[ 19.097369] EXT4-fs warning (device mmcblk0p2):
__ext4_read_dirblock:681: error reading directory block (ino 2001,
block 0)
[ 19.110210] EXT4-fs warning (device mmcblk0p2):
__ext4_read_dirblock:681: error reading directory block (ino 2001,
block 0)
[ 19.153687] EXT4-fs warning (device mmcblk0p2):
__ext4_read_dirblock:681: error reading directory block (ino 2001,
block 0)
[ 29.800522] EXT4-fs warning: 1 callbacks suppressed
[ 29.805425] EXT4-fs warning (device mmcblk0p2):
__ext4_read_dirblock:681: error reading directory block (ino 2001,
block 0)
[ 29.842343] EXT4-fs warning (device mmcblk0p2):
__ext4_read_dirblock:681: error reading directory block (ino 90, block
0)
[ 29.875698] EXT4-fs warning (device mmcblk0p2):
__ext4_read_dirblock:681: error reading directory block (ino 32928,
block 0)
[ 29.906757] EXT4-fs warning (device mmcblk0p2):
__ext4_read_dirblock:681: error reading directory block (ino 90, block
0)
Regards,
john
^ permalink raw reply [flat|nested] 3+ messages in thread
* iMX6SL Suspend mode (S3)
2014-01-24 21:14 iMX6SL Suspend mode (S3) John Tobias
@ 2014-01-24 21:24 ` Russell King - ARM Linux
2014-01-24 21:31 ` John Tobias
0 siblings, 1 reply; 3+ messages in thread
From: Russell King - ARM Linux @ 2014-01-24 21:24 UTC (permalink / raw)
To: linux-arm-kernel
On Fri, Jan 24, 2014 at 01:14:08PM -0800, John Tobias wrote:
> Hello all,
>
> I am testing the suspend mode (S3) for my custom board with iMX6SL and
> the iMX6SL EVK as well. I am using 3.13 kernel, eMMC and MMC for the
> storage and systemd to control the OS. If I put my device in S3 mode,
> I got the following messages:
>
> [ 27.949393] PM: Syncing filesystems ... done.
> [ 27.972392] mmc0: card 0001 removed
> [ 28.033613] end_request: I/O error, dev mmcblk0, sector 0
> [ 28.063493] end_request: I/O error, dev mmcblk0, sector 0
> [ 28.107933] end_request: I/O error, dev mmcblk0, sector 0
> [ 28.131456] end_request: I/O error, dev mmcblk0, sector 0
> [ 28.153651] end_request: I/O error, dev mmcblk0, sector 0
> [ 28.215530] Freezing user space processes ... (elapsed 0.001 seconds) done.
> [ 28.224284] Freezing remaining freezable tasks ... (elapsed 0.001
> seconds) done.
> [ 28.233658] Suspending console(s) (use no_console_suspend to debug)
>
> If I press any key, it will wake up. But, I got the following errors:
>
> [ 17.815008] mmc0: new high speed DDR MMC card at address 0001
> [ 17.828024] mmcblk0: mmc0:0001 SEM04G 3.68 GiB
> [ 17.833522] mmcblk0boot0: mmc0:0001 SEM04G partition 1 2.00 MiB
> [ 17.839699] mmcblk0boot1: mmc0:0001 SEM04G partition 2 2.00 MiB
> [ 17.847150] mmcblk0rpmb: mmc0:0001 SEM04G partition 3 2.00 MiB
> [ 17.860116] mmcblk0: p1 p2 p3 p4 < p5 p6 >
> [ 17.883550] mmcblk0boot1: unknown partition table
> [ 17.899549] mmcblk0boot0: unknown partition table
This is because MMC insists that when you suspend, the card will be
ejected, and when you resume, it will be re-inserted - it's effectively
the same as if you pulled the card out and then plugged it back in
without shutting the system down.
This is the default for the MMC subsystem, unless MMC_UNSAFE_RESUME
is set - and you can't have rootfs in MMC and suspend/resume unless
that's set.
--
FTTC broadband for 0.8mile line: 5.8Mbps down 500kbps up. Estimation
in database were 13.1 to 19Mbit for a good line, about 7.5+ for a bad.
Estimate before purchase was "up to 13.2Mbit".
^ permalink raw reply [flat|nested] 3+ messages in thread
* iMX6SL Suspend mode (S3)
2014-01-24 21:24 ` Russell King - ARM Linux
@ 2014-01-24 21:31 ` John Tobias
0 siblings, 0 replies; 3+ messages in thread
From: John Tobias @ 2014-01-24 21:31 UTC (permalink / raw)
To: linux-arm-kernel
Thanks Russell. Got it working.
Regards,
john
On Fri, Jan 24, 2014 at 1:24 PM, Russell King - ARM Linux
<linux@arm.linux.org.uk> wrote:
> On Fri, Jan 24, 2014 at 01:14:08PM -0800, John Tobias wrote:
>> Hello all,
>>
>> I am testing the suspend mode (S3) for my custom board with iMX6SL and
>> the iMX6SL EVK as well. I am using 3.13 kernel, eMMC and MMC for the
>> storage and systemd to control the OS. If I put my device in S3 mode,
>> I got the following messages:
>>
>> [ 27.949393] PM: Syncing filesystems ... done.
>> [ 27.972392] mmc0: card 0001 removed
>> [ 28.033613] end_request: I/O error, dev mmcblk0, sector 0
>> [ 28.063493] end_request: I/O error, dev mmcblk0, sector 0
>> [ 28.107933] end_request: I/O error, dev mmcblk0, sector 0
>> [ 28.131456] end_request: I/O error, dev mmcblk0, sector 0
>> [ 28.153651] end_request: I/O error, dev mmcblk0, sector 0
>> [ 28.215530] Freezing user space processes ... (elapsed 0.001 seconds) done.
>> [ 28.224284] Freezing remaining freezable tasks ... (elapsed 0.001
>> seconds) done.
>> [ 28.233658] Suspending console(s) (use no_console_suspend to debug)
>>
>> If I press any key, it will wake up. But, I got the following errors:
>>
>> [ 17.815008] mmc0: new high speed DDR MMC card at address 0001
>> [ 17.828024] mmcblk0: mmc0:0001 SEM04G 3.68 GiB
>> [ 17.833522] mmcblk0boot0: mmc0:0001 SEM04G partition 1 2.00 MiB
>> [ 17.839699] mmcblk0boot1: mmc0:0001 SEM04G partition 2 2.00 MiB
>> [ 17.847150] mmcblk0rpmb: mmc0:0001 SEM04G partition 3 2.00 MiB
>> [ 17.860116] mmcblk0: p1 p2 p3 p4 < p5 p6 >
>> [ 17.883550] mmcblk0boot1: unknown partition table
>> [ 17.899549] mmcblk0boot0: unknown partition table
>
> This is because MMC insists that when you suspend, the card will be
> ejected, and when you resume, it will be re-inserted - it's effectively
> the same as if you pulled the card out and then plugged it back in
> without shutting the system down.
>
> This is the default for the MMC subsystem, unless MMC_UNSAFE_RESUME
> is set - and you can't have rootfs in MMC and suspend/resume unless
> that's set.
>
> --
> FTTC broadband for 0.8mile line: 5.8Mbps down 500kbps up. Estimation
> in database were 13.1 to 19Mbit for a good line, about 7.5+ for a bad.
> Estimate before purchase was "up to 13.2Mbit".
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2014-01-24 21:31 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-01-24 21:14 iMX6SL Suspend mode (S3) John Tobias
2014-01-24 21:24 ` Russell King - ARM Linux
2014-01-24 21:31 ` John Tobias
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox