i.MX6DQ Android 5.1.1_2.1.0-ga fails resume.

cancel
Showing results for 
Search instead for 
Did you mean: 

i.MX6DQ Android 5.1.1_2.1.0-ga fails resume.

1,566 Views
Senior Contributor I

Hi community,

Our customer have a question about i.MX6Q Android 5.1.1 BSP.

This BSP sometimes faile to resume from suspend.

Please see the detail as below.

=====

[Board]

MCIMX6Q-SDP

[BSP]

Android 5.1.1_2.1.0-ga

[Problem]

Sometimes fail to resume from suspend.

[Procedure]

1.Boot Android 5.1.1 and set the following bootargs to use serial console.

  setenv bootargs console=ttymxc0,115200 init=/init video=mxcfb0:dev=ldb,bpp=32 video=mxcfb1:off video=mxcfb2:off video=mxcfb3:off vmalloc=256M androidboot.console=ttymxc0 consoleblank=0 androidboot.hardware=freescale cma=384M androidboot.selinux=disabled androidboot.dm_verity=disabled

2. Suspend Anroid with the following command.

  echo mem > /sys/power/state

3. Resume with pushing power switch (SW1).

[Frequency]

Often

[log]

root@sabresd_6dq:/ # echo mem > /sys/power/state

PM: suspend entry 1970-01-01 00:42:12.771037673 UTC

PM: Syncing filesystems ... done.

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

Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.

Suspending console(s) (use no_console_suspend to debug)    // Suspending Done

PM: suspend of devices complete after 66.477 msecs    // Push power button to resume

PM: suspend devices took 0.070 seconds

PM: late suspend of devices complete after 0.535 msecs

PM: noirq suspend of devices complete after 0.634 msecs

Disabling non-boot CPUs ...

CPU1: shutdown

CPU2: shutdown

CPU3: shutdown

Resume caused by IRQ 103

Suspended for 0.000 seconds

Enabling non-boot CPUs ...

CPU1: Booted secondary processor

CPU1 is up

CPU2: Booted secondary processor

CPU2 is up

CPU3: Booted secondary processor

CPU3 is up

PM: noirq resume of devices complete after 0.392 msecs

PM: early resume of devices complete after 0.454 msecs

PM: resume of devices complete after 131.201 msecs

PM: resume devices took 0.140 seconds

Restarting tasks ... done.

PM: suspend exit 1970-01-01 00:42:16.162975000 UTC

root@sabresd_6dq:/ # ata1: SATA link down (SStatus 0 SControl 300)

mma enable setting inactive

PU: Power-off latency exceeded, new value 29000 ns

PM: suspend entry 1970-01-01 00:42:20.462260334 UTC

PM: Syncing filesystems ... done.

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

Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.

Suspending console(s) (use no_console_suspend to debug)   // Suspend automatically again with no handling

=====

[Question]

How can I modify this resume problem?

Best Regards,

Satoshi Shimoda

Tags (1)
0 Kudos
23 Replies

209 Views
NXP Apps Support
NXP Apps Support

SergioSolis‌ please continue with the follow up

0 Kudos

209 Views
Senior Contributor I

Would you give me advice about this issue?

Best Regards,

Satoshi Shimoda

0 Kudos

209 Views
NXP Employee
NXP Employee

Hello Satoshi,

I will try to reproduce this problem, can you tell me what is the revision of the board you have?

0 Kudos

209 Views
Senior Contributor I

Dear Sergio,

Have you reproduced same issue on your board?

Best Regards,

Satoshi Shimoda

0 Kudos

209 Views
NXP Employee
NXP Employee

Hello Satoshi,

have You tried typing

echo test > /sys/power/wake_lock

at the console or add

no_console_suspend

to bootargs?

0 Kudos

209 Views
Senior Contributor I

Dear Sergio,

I tried the above command and bootargs, but not resolved.

Best Regards,

Satoshi Shimoda

0 Kudos

209 Views
NXP Employee
NXP Employee

Can we get a log of the system?  It may point to what may be not responding to a suspend/resume. My SDB sleeps and resumes without a hiccup so I suspect something with the SDP is causing the resume to not inititate.  I can compare their log to my SDB.

It should wake up if they depress the 'power sw' right next to the slider switch.

0 Kudos

209 Views
Senior Contributor I

Dear SergioSolis,

Any update to my question?

For your information, I tested with not only i.MX6Q SABRE but also i.MX6DL SABRE, then same issue was happened.

Best Regards,

Satoshi Shimoda

0 Kudos

209 Views
NXP Employee
NXP Employee

Hello Satoshi, please see the expert's response:

I have still not been able to reproduce. Do these cards have any mods?

 

Something on the power rail must not be acquiesed in the senario that does not allow a resume.  An ftrace, not a dmesg, may tell us who the culprit is.

This would require you use the ftrace Android has available. A proper ftrace should reveal what process or device is failing to resume.

0 Kudos

209 Views
Senior Contributor I

I'm struggling to enable ftrace, just a moment please.

Best Regards,

Satoshi Shimoda

0 Kudos

209 Views
NXP Employee
NXP Employee

Hello Satoshi, do you have an update?, were you able to do the ftrace?

0 Kudos

209 Views
Senior Contributor I

I got the ftrace log (trace_pipe.log), and console log (console_log.txt) at that time also.

Please see the attached file.

Best Regards,

Satoshi Shimoda

0 Kudos

209 Views
Senior Contributor I

Hi Sergio,

Please give me your status.

Best Regards,

Satoshi Shimoda

0 Kudos

209 Views
NXP Employee
NXP Employee

Hello Satoshi,

I'm still waiting for a response from our experts. I will update you as soon as I have a reply from them.

0 Kudos

209 Views
Senior Contributor I

Hi Sergio,

Would you let me know your status?

Best Regards,

Satoshi Shimoda

0 Kudos

209 Views
Senior Contributor I

Dear Sergio,

I tested with SABRE-SDP as I mentioned.

And I could not test with SDB since I don't have SDB.

So could you test with SDP on your side also in order to make the same test environment?

I send the detail of my test environment.

====

[Board]
MCIMX6Q-SDP (SCH-27392 Rev C2, 700-27392 Rev A) and

MCIMX6Q-SDP (SCH-27392 Rev C4, 700-27392 Rev C)

[Chip on the board]

PCIMX6Q6AVT10AC

SBAG2139

P62958 02

KOREA XMAGSBJ

(on SCH-27392 Rev C2)

[BSP]
android_L5.1.1_2.1.0_full_image_6dqsabresd in android_L5.1.1_2.1.0_image_6dqsabresd

[MFG tool]

android_L5.1.1_2.1.0-ga_mfgtools

[Boot]

This issue is occurred with both SD-card boot and eMMC boot.

[Procedure]
1.Boot Android 5.1.1 and set the following bootargs to use serial console.
setenv bootargs console=ttymxc0,115200 init=/init video=mxcfb0:dev=ldb,bpp=32 video=mxcfb1:off video=mxcfb2:off video=mxcfb3:off vmalloc=256M androidboot.console=ttymxc0 consoleblank=0 androidboot.hardware=freescale cma=384M androidboot.selinux=disabled androidboot.dm_verity=disabled

2. Set "stay awake" and display sleep time as "30 minites" in setting.
3. Suspend Anroid with the following command.
echo mem > /sys/power/state
4. Resume with pushing power switch (SW1).

=====

And could you let me know how many times did you test with SDB in past, and also whether the image you tested is same as the one I tested or not?

Best Regards,

Satoshi Shimoda

0 Kudos

209 Views
Senior Contributor I

Hi Sergio,

I confirmed this issue is occurred on SABRE SDB also, and recorded the issue.

Please see the attached video.

You can see the screen was black out after resume by pushing power switch, the black out indicates entering suspend again.

Best Regards,

Satoshi Shimoda

0 Kudos

209 Views
Senior Contributor I

Hello Sergio,

Could you let me know your status?

Checking the log?

If there is some progress, could you let me know it?

Best Regards,

Satoshi Shimoda

0 Kudos

209 Views
Senior Contributor I

Hello Sergio,

I have not enabled ftrace yet.

Please wait a little more time.

Best Regards,

Satoshi Shimoda

0 Kudos

209 Views
NXP Employee
NXP Employee

I'm waiting for a response from our experts team and I will update you asap.

0 Kudos