Comment 65 for bug 1848771

(In reply to Ferry Toth from comment #36)
> On Ubuntu 19:10 linux 5.3.0-46 (resume bad):
> ferry@chromium:~$ cat /sys/power/mem_sleep
> s2idle [deep]
> root@chromium:~# rtcwake -m mem -s 30
>
> After 30 sec takes me to boot screen.
>
So it reboots during resume. it's quite hard to track at which stage it reboots if there's no uart log. Since the S3 works in old kernel, The most straight way is to do a git bisect to find the offender. Or else, we have to add hack code during resume to spin the kernel at different place thus to narrow down.