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
Titl
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 b
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 <1738...@bugs.laun
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
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 reproduce the issue on the XPS 936
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] suspend_c
** 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 n
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:
https://bugs.launchpad.net/u
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 t
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:
https://bugs.launchpad.net/ubuntu/+sour
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 be
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 g
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 about
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
helpfu
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.
https://bugs.launchpad.net/
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
Bu
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 th
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 ma
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 broke
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 are
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 "system
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 t
22 matches
Mail list logo
