Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suspend to ram cause reboot. #24

Open
ddejean opened this issue Sep 18, 2016 · 1 comment
Open

Suspend to ram cause reboot. #24

ddejean opened this issue Sep 18, 2016 · 1 comment

Comments

@ddejean
Copy link

ddejean commented Sep 18, 2016

With branch m6.0.1-udoo, trying to suspend to ram leads to a reboot. Here is an extract of the console (shell + kernel logs). Do you see any reason that would lead to this kind of crash ?

130|root@udoo_6dq:/ #  echo mem > /sys/power/state
PM: suspend entry 2016-01-01 00:01:56.491214347 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 18.201 msecs
PM: suspend devices took 0.030 seconds
PM: late suspend of devices complete after 0.469 msecs
PM: noirq suspend of devices complete after 0.508 msecs
Disabling non-boot CPUs ...
CPU1: shutdown

U-Boot SPL 2015.04-g9b809d0 (May 22 2016 - 19:07:51)
SPL: u-boot second stage will be loaded from MMC0


U-Boot 2015.04-g9b809d0 (May 22 2016 - 19:07:51)

CPU:   Freescale i.MX6DL rev1.1 at 792 MHz
CPU:   Temperature 50 C
Reset cause: POR
Board: UDOO DualLite
       Watchdog enabled
DRAM:  1 GiB
MMC:   FSL_SDHC: 0
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
check_and_clean: reg 0, flag_set 0
Fastboot: Normal
flash target is MMC:0
Net:   using phy at 6
FEC [PRIME]
Normal Boot
Hit any key to stop autoboot:  0 
112 bytes read in 134 ms (0 Bytes/s)
Running bootscript from mmc ...
Device Tree: dts/imx6dl-udoo-hdmi.dtb
41234 bytes read in 68 ms (591.8 KiB/s)
boota mmc0 
kernel   @ 14008000 (7260256)
ramdisk  @ 15000000 (910511)
fdt      @ 14f00000 (42363)
## Booting Android Image at 0x12000000 ...
Kernel load addr 0x14008000 size 7091 KiB
Kernel command line: console=ttymxc1,115200 init=/init vmalloc=256M androidboot.console=ttymxc1 consoleblank=0 androidboot.hardware=d
## Flattened Device Tree blob at 14f00000
   Booting using the fdt blob at 0x14f00000
   Loading Kernel Image ... OK
   Using Device Tree in place at 14f00000, end 14f0d111

Starting kernel ...
@secuflag
Copy link

I can confirm the same issue: http://pastebin.com/raw/3YtReur3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants