That particular commit actually breaks proper s2idle. Because of it S3 should be used instead on 9360.
It was intentionally broken because of some reported regression by one guy with an nvme SSD of a particular vendor. Can you please check which SSD you have? Nvme info command on it can be helpful. On Sat, Dec 16, 2017, 16:05 Jeffrey Bouter <1738...@bugs.launchpad.net> wrote: > kai-Heng, on both occasions (suspend working and broken on latest > kernel) I had nothing connected to my USB-C port. I'll test s2idle later > and get back to you. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1738224 > > Title: > Suspend broken after kernel upgrade > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738224/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738224 Title: Suspend broken after kernel upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738224/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
