Auto suspending and console unresponsive -Android6.0.1 on iMX6QP

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Auto suspending and console unresponsive -Android6.0.1 on iMX6QP

1,448 Views
jaffinmk
Contributor III

Hi

As I have mentioned Im running Android 6.0.1 with 4.1.15 kernel on iMX6QP Sabre.

I am not sure if this is normal but the system keeps suspending automatically when I try to work on the console and it is unresponsive until I hit the power button. It keeps suspending within few seconds so much that I cant even enter a command on the shell terminal. Also it had suggested to enable no_console_suspend so I entered that in the bootargs in uboot terminal. But still it keeps suspending. Here is the serial debug output.

root@sabresd_6dq:/ # mma enable setting inactive
PM: suspend entry 1970-01-01 00:44:53.843975006 UTC
PM: Syncing filesystems ... done.
Freezing user space processes ...
PM: Wakeup pending, aborting suspend
active wakeup source: PowerManagerService.Broadcasts

Freezing of tasks aborted after 0.009 seconds
Restarting tasks ... done.
PM: suspend exit 1970-01-01 00:44:53.896689339 UTC
PM: suspend entry 1970-01-01 00:44:54.002049006 UTC
PM: Syncing filesystems ... done.
Freezing user space processes ... (elapsed 0.001 seconds) done.
Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
PM: suspend of devices complete after 54.871 msecs
PM: suspend devices took 0.060 seconds
PM: late suspend of devices complete after 4.293 msecs
PM: noirq suspend of devices complete after 1.233 msecs
Disabling non-boot CPUs ...
CPU1: shutdown
CPU2: shutdown
CPU3: shutdown
PM: Wakeup pending, aborting suspend
active wakeup source: NETLINK
Enabling non-boot CPUs ...
CPU1 is up
CPU2 is up
CPU3 is up
PM: noirq resume of devices complete after 0.843 msecs
PM: early resume of devices complete after 0.799 msecs
PM: resume of devices complete after 178.655 msecs
PM: resume devices took 0.180 seconds
Restarting tasks ... done.
PM: suspend exit 1970-01-01 00:44:54.527520673 UTC
PM: suspend entry 1970-01-01 00:44:54.632249006 UTC
PM: Syncing filesystems ... done.
Freezing user space processes ... (elapsed 0.002 seconds) done.
Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
ata1: SATA link down (SStatus 0 SControl 300)
PM: suspend of devices complete after 56.338 msecs
PM: suspend devices took 0.060 seconds
PM: late suspend of devices complete after 1.451 msecs
PM: noirq suspend of devices complete after 1.425 msecs
Disabling non-boot CPUs ...
CPU1: shutdown
CPU2: shutdown
CPU3: shutdown
Resume caused by IRQ 58
Resume caused by IRQ 103
Suspended for 0.000 seconds
Enabling non-boot CPUs ...
CPU1 is up
CPU2 is up
CPU3 is up
PM: noirq resume of devices complete after 0.613 msecs
PM: early resume of devices complete after 0.668 msecs
PM: resume of devices complete after 179.001 msecs
PM: resume devices took 0.180 seconds
Restarting tasks ... done.
PM: suspend exit 1970-01-01 00:45:00.167547667 UTC
ata1: SATA link down (SStatus 0 SControl 300)
period 66 ,timeout is 0, wake up is :0
mma enable setting active

root@sabresd_6dq:/ # mma enable setting inactive
PM: suspend entry 1970-01-01 00:45:11.134848001 UTC
PM: Syncing filesystems ... done.
Freezing user space processes ...
PM: Wakeup pending, aborting suspend
active wakeup source: PowerManagerService.Broadcasts

Freezing of tasks aborted after 0.009 seconds
Restarting tasks ... done.
PM: suspend exit 1970-01-01 00:45:11.194698335 UTC
PM: suspend entry 1970-01-01 00:45:11.299397335 UTC
PM: Syncing filesystems ... done.
Freezing user space processes ... (elapsed 0.002 seconds) done.
Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
PM: suspend of devices complete after 54.297 msecs
PM: suspend devices took 0.060 seconds
PM: late suspend of devices complete after 1.440 msecs
PM: noirq suspend of devices complete after 1.433 msecs
Disabling non-boot CPUs ...
CPU1: shutdown
CPU2: shutdown
CPU3: shutdown

Unable to work on the terminal since it keeps suspending.

Labels (3)
Tags (1)
0 Kudos
1 Reply

648 Views
Bio_TICFSL
NXP TechSupport
NXP TechSupport

Hi,

For this case you will have to debug and check the suspend issue, also have to take a look a your device tree power management configuration:

https://community.nxp.com/docs/DOC-98327 

Regards

0 Kudos