(In reply to Ferry Toth from comment #28) > ferry@chromium:~$ tpm_version > Tspi_Context_Connect failed: 0x00003011 - layer=tsp, code=0011 (17), > Communication failure > > ferry@chromium:~$ cat /sys/power/mem_sleep > s2idle [deep] > root@chromium:~# echo 'N' > /sys/module/printk/parameters/console_suspend > root@chromium:~# echo 'Y' > /sys/module/printk/parameters/initcall_debug > -bash: /sys/module/printk/parameters/initcall_debug: Toegang geweigerd > (that is access denied, because not existing) > > > Going from right to left only none fails (i.e. does not return but goes to > the boot screen). > I captured journal tails in pm_test.txt This has shown that when resuming from BIOS S3 and the BIOS is about to jump back to the vector in OS, the system has triggered a reboot. Did you update your BIOS recently? How about echo deep > /sys/power/mem_sleep rtcwake -m mem -s 30?
And how about: echo s2idle > /sys/power/mem_sleep rtcwake -m freeze -s 30? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848771 Title: Reboot after resume from suspend (deep) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
