LS2021A deep sleep exit issue

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

LS2021A deep sleep exit issue

615 Views
kdutuil
Contributor I

Hello,

I have a TWR-LS1021A-PB board, with vanilla QorIQ Linux SDK v2.0 installed.

The board does not exit from deep sleep properly.

Here are the relevant logs:

root@ls1021atwr:~# echo 5 > /sys/devices/platform/soc/29d0000.ftm0/ftm_alarm && echo mem > /sys/power/state

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 177.340 msecs

PM: late suspend of devices complete after 1.348 msecs

PM: noirq suspend of devices complete after 1.230 msecs

Disabling non-boot CPUs ...

kvm: disabling virtualization on CPU1

CPU1: shutdown

Retrying again to check for CPU kill

CPU1 killed.

[5 seconds elapse]

Enabling non-boot CPUs ...

kvm: enabling virtualization on CPU1

CPU1 is up

PM: noirq resume of devices complete after 1.366 msecs

PM: early resume of devices complete after 1.202 msecs

caam 1700000.crypto: Entropy delay = 3200

caam 1700000.crypto: failed to acquire DECO 0

caam 1700000.crypto: failed to instantiate RNG

dpm_run_callback(): platform_pm_resume+0x1/0x1c returns -19

PM: Device 1700000.crypto failed to resume: error -19

usb usb1: root hub lost power or was reset

usb usb2: root hub lost power or was reset

ata1: SATA link down (SStatus 0 SControl 300)

fsl-gianfar soc:ethernet@2d50000 eth1: Link is Down

fsl-gianfar soc:ethernet@2d50000 eth1: Link is Up - 1Gbps/Full - flow control rx/tx

[I manually un-plug eth1]

fsl-gianfar soc:ethernet@2d50000 eth1: Link is Down

[I manually re-plug eth1]

fsl-gianfar soc:ethernet@2d50000 eth1: Link is Up - 1Gbps/Full - flow control rx/tx

I do not have a shell anymore when the board exists from deep sleep.

I also cannot ssh anymore to the board (sometimes it will answer pings, but not TCP packets) after deep sleep exit.

However, I still get kernel logs from eth1 plugs, so the kernel is still running.

Has anyone had this issue before?

0 Kudos
Reply
0 Replies