[Bug 1848771]

[yu.c.chen]

(In reply to Ferry Toth from comment #28)
> ferry at chromium:~$ tpm_version 
> Tspi_Context_Connect failed: 0x00003011 - layer=tsp, code=0011 (17),
> Communication failure
> 
> ferry at chromium:~$ cat /sys/power/mem_sleep
> s2idle [deep]
> root at chromium:~# echo 'N' > /sys/module/printk/parameters/console_suspend
> root at 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
Foundations Bugs, which is subscribed to ubuntu-release-upgrader in
Ubuntu.
https://bugs.launchpad.net/bugs/1848771

Title:
  Reboot after resume from suspend (deep)

Status in linux package in Ubuntu:
  Incomplete
Status in ubuntu-release-upgrader package in Ubuntu:
  Invalid

Bug description:
  After upgrading to Kubuntu Eoan (19.10) yesterday, my laptop crashes
  after resume from suspending. This is regardless the way of suspending
  (closing lid, selecting suspend from sddm, systemctl suspend).

  The journal shows:
  ferry at chromium:~$ journalctl -b -1 -e
  ..
  sddm[1106]: Message received from greeter: Suspend
  NetworkManager[836]: <info>  manager: sleep: sleep requested (sleeping: no  enabled: yes)
  NetworkManager[836]: <info>  device (60:73:BC:BA:B8:68): state change: disconnected -> unmanaged (reason '
  NetworkManager[836]: <info>  device (60:73:BC:23:8F:3E): state change: disconnected -> unmanaged (reason '
  NetworkManager[836]: <info>  device (p2p-dev-wlp1s0): state change: disconnected -> unmanaged (reason 'sle
  NetworkManager[836]: <info>  manager: NetworkManager state is now ASLEEP
  systemd[1]: Reached target Sleep.
  systemd[1]: Starting Suspend...
  systemd-sleep[1238]: Suspending system...
  kernel: PM: suspend entry (deep)

  On resume (keypress, open lid) resume starts but immediately crashes
  and reboots.

  The laptop is an Acer 720p Chromebook with Chromium replaced and
  working fine with Kubuntu since 5 years or so.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Fri Oct 18 18:45:53 2019
  InstallationDate: Installed on 2017-07-13 (826 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago)
  VarLogDistupgradeTermlog:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848771/+subscriptions