[Bug 1738224] Re: Suspend broken after kernel upgrade

2018-01-02 Thread Kai-Heng Feng
Thanks for the info. Please reopen this bug once the issue appears again. ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738224

[Bug 1738224] Re: Suspend broken after kernel upgrade

2017-12-20 Thread Jeffrey Bouter
Fair enough. Thanks for the information. I just rebooted into 4.13.0-21-generic. Either it's a lucky boot in which suspend works, or the issue has been resolved. For those interested, the value of /sys/power/mem_sleep (after a clean boot, suspended once) is: s2idle [deep] -- You received this

Re: [Bug 1738224] Re: Suspend broken after kernel upgrade

2017-12-20 Thread Mario Limonciello
Information isn't available on what has changed between NVM releases from Intel. It generally improves performance and resolves issues with the ICM stack. Those could lead to for example the controller not going to sleep when it should. On Wed, Dec 20, 2017, 11:26 Jeffrey Bouter

[Bug 1738224] Re: Suspend broken after kernel upgrade

2017-12-20 Thread Jeffrey Bouter
Kai-Heng, As posted before, I have since upgraded to 2.4.2 - this *sometimes* fixes the issue, but not always. Currently, it is fixed. So I don't plan on rebooting my machine (just letting it suspend) until either a new kernel release comes out, or a firmware update comes out. Mario, What would

Re: [Bug 1738224] Re: Suspend broken after kernel upgrade

2017-12-19 Thread Mario Limonciello
Thunderbolt NVM isn't on LVFS stable but it's on testing. Either turn on fwupd LVFS testing remote or install manually from this file: https://fwupd.org/lvfs/device/dfd51125-338f-56ff-b721-fa3bea8e534e On Tue, Dec 19, 2017, 02:45 Kai-Heng Feng wrote: > I can't

[Bug 1738224] Re: Suspend broken after kernel upgrade

2017-12-19 Thread Kai-Heng Feng
I can't reproduce the issue on the XPS 9360 at my hand, which unfortunately is not the mass production one, with both BIOS 2.3.1 (the version you currently used) and 2.4.2. The TBT's XHCI HC failed to suspend, [ 87.718350] xhci_hcd :39:00.0: WARN: xHC CMD_RUN timeout [ 87.718372]

[Bug 1738224] Re: Suspend broken after kernel upgrade

2017-12-18 Thread Kai-Heng Feng
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng) -- 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

[Bug 1738224] Re: Suspend broken after kernel upgrade

2017-12-18 Thread Jeffrey Bouter
Kai, it is: s2idle [deep] -- 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:

[Bug 1738224] Re: Suspend broken after kernel upgrade

2017-12-17 Thread Kai-Heng Feng
What's the value of "/sys/power/mem_sleep" on 4.13.0-19? -- 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

[Bug 1738224] Re: Suspend broken after kernel upgrade

2017-12-17 Thread Jeffrey Bouter
No, I did not. -- 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:

Re: [Bug 1738224] Re: Suspend broken after kernel upgrade

2017-12-16 Thread Mario Limonciello
Did you manually set s2idle? That policy shouldn't have been picked unless you were on 4.14. On Sat, Dec 16, 2017, 17:55 Jeffrey Bouter <1738...@bugs.launchpad.net> wrote: > Kai-Heng, > > A cat on /sys/power/mem_sleep already shows: > > [s2idle] deep > > -- > You received this bug notification

[Bug 1738224] Re: Suspend broken after kernel upgrade

2017-12-16 Thread Jeffrey Bouter
Kai-Heng, A cat on /sys/power/mem_sleep already shows: [s2idle] deep -- 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

[Bug 1738224] Re: Suspend broken after kernel upgrade

2017-12-16 Thread Jeffrey Bouter
Mario, THNSN5512GPUK NVMe TOSHIBA 512GB would be the model -- 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

Re: [Bug 1738224] Re: Suspend broken after kernel upgrade

2017-12-16 Thread Mario Limonciello
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

[Bug 1738224] Re: Suspend broken after kernel upgrade

2017-12-16 Thread Jeffrey Bouter
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 a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1738224] Re: Suspend broken after kernel upgrade

2017-12-16 Thread Kai-Heng Feng
This commit might cause your issue: http://kernel.ubuntu.com/git/ubuntu /ubuntu-artful.git/commit/?id=56aa325de02d0448345358cb1b851a4c1e94f758 Return to s2idle should solve the issue. # echo s2idle > /sys/power/mem_sleep -- You received this bug notification because you are a member of Ubuntu

[Bug 1738224] Re: Suspend broken after kernel upgrade

2017-12-16 Thread Kai-Heng Feng
Do you have anything connected to your thunderbolt/USB type-c port? -- 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

[Bug 1738224] Re: Suspend broken after kernel upgrade

2017-12-15 Thread Jeffrey Bouter
Updating my XPS to the latest firmware (I was only one release behind) has resolved the issue. -- 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

[Bug 1738224] Re: Suspend broken after kernel upgrade

2017-12-15 Thread Jeffrey Bouter
Nevermind. Only worked once. After a reboot, just to check, the issue still persists. Both on battery and on regular power. -- 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

[Bug 1738224] Re: Suspend broken after kernel upgrade

2017-12-14 Thread Jeffrey Bouter
Joseph, I've added the requested tag. Upstream/mainline (4.15) fixes the issue. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Tags removed: kernel-fixed-upstream wayland-session ** Tags added: kernel-fixed-upstream -- You received this bug notification because you

[Bug 1738224] Re: Suspend broken after kernel upgrade

2017-12-14 Thread Jeffrey Bouter
apport information ** Tags added: apport-collected wayland-session ** Description changed: My machine (XPS 13 9360) won't go into suspend properly after upgrading from linux-image-4.13.0-17-generic to linux-image-4.13.0-19-generic. This affects both suspend through lid close and

[Bug 1738224] Re: Suspend broken after kernel upgrade

2017-12-14 Thread Joseph Salisbury
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.15 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix