(In reply to Ferry Toth from comment #41)
> While bysecting (I hope to complete tomorrow) I found a workaround (that
> works for me on Acer 720P).
> 
> I always had tpm_tis.force=1 on the kernel command line.
> Now I added tpm_tis.interrupts=0.
> 
> Wakes fine now with linux 5.6.0.

First of all, thanks for bisecting this!

I can confirm setting tpm_tis.interrupts=0 works for me on ASUS C302
kernel 5.7.2 (Arch latest) and kernel 5.4.46 (Arch LTS). Previously I
had no tpm_tis.interrupts setting so it must default to on.

So the question is, why does tpm_tis.interrupts only cause problems on
newer kernels? Is it a kernel bug?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux 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@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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to