• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 386 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

AM335x Suspend delay

Clifton Barnes
Prodigy 155 points

The suspend and resume is working properly on my AM335x device running the TI_Android_JB_4.2.2_DevKit_4.1.1 release, but there is a very long delay when going to suspend as below:

[ 4382.906555] request_suspend_state: sleep (0->3) at 4178595558776 (2014-01-08 15:51:54.565420877 UTC)
[ 4425.124237] PM: Syncing filesystems ... done.
[ 4425.201965] Freezing user space processes ... (elapsed 0.01 seconds) done.
[ 4425.224212] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.

Almost 40 seconds passed before the device actually started to suspend. I don't have any other information to know if Android is keeping the system alive on purpose or if this indicates something not working properly.

Is there something that I can do to avoid this delay?

  • 0
    TI__Intellectual 1195 points

    It seems like most of the delay is due to filesystem flushing/syncing data prior to suspending.

    Perhaps you have an application writing data to the FS or a mount point such as USB thumb drive when the system goes into suspend.

  • 0 in reply to Carlos Hernandez
    Prodigy 155 points

    I had assumed that if the file system was taking the time that I would see an elapsed time message like the following freezing message:

    Freezing user space processes ... (elapsed 0.11 seconds) done.

    Does the file system message not do the same thing? I'm not running any custom applications so unless standard Android applications are writing to the eMMC, I don't think it should take long to sync.