Description of problem: Computer crashes when attempting to suspend or hibernate, either by closing the lid or by running pm-suspend or pm-hibernate. Version-Release number of selected component (if applicable): Fedora 22. This occured with both kernels 4.0.2 and 4.1-rc3 (rawhide kernel). How reproducible: Happens every time. Steps to Reproduce: 1. Attempt to suspend or hibernate computer. Actual results: Computer crashes. Expected results: Computer suspends or hibernates. Additional info: Caps lock key won't light up if pressed after crash, indicating that it's not just the window manager that's non-responsive. Please fix this, currently I have to turn off my computer every time I stop using it! Also, this bug does not occur under a fresh Ubuntu 15.04 installation.
Noticing that I had an outdated BIOS (F.04), I updated to the latest version of the BIOS (F.12 Rev.A), released Apr 21, 2015. Nothing was resolved by the BIOS update: * Suspending by closing the lid still causes the same crash. * Suspending by pressing the power button still causes the same crash. * Suspending using `pm-suspend` still causes the same crash.
On Fedora 22, manually downgrading to kernel-3.19.7-200.fc21 (latest Fedora 21 stable kernel) fixes the issue! This now seems to be an issue exclusive to Fedora 22's kernel source tree, and therefore I think it's quite important to look into it before fc22 becomes stable.
Issue also occurs on kernel 4.0.3-300.fc22.
*** Bug 1222273 has been marked as a duplicate of this bug. ***
I also have a HP Spectre x360 and can confirm that "sudo pm-suspend" causes an immediate machine freeze, with no apparent reporting whatsoever - the system just stops immediately, with capslock et al also becoming non-responsive.
Issue also occurs on kernel 4.0.4-300.fc22. Could someone please look into this? :-(
It's potentially relevant that both Nadim and I are seeing the Broadwell-U chipset audio compatibility issues described over in bug 1220709
Nadim, are you seeing any of the graphics driver errors reported in bug 1188772?
Via a separate discussion, some checks possibly worth running: pm-is-supported --suspend && echo Supported pm-is-supported --hibernate && echo Supported pm-is-supported --suspend-hybrid && echo Supported (I don't have my laptop with me right now, so needinfo'ing myself to also run these checks)
The chipset at least claims to be supported, although as noted above, that's not the same as having it fully working: $ pm-is-supported --suspend && echo Supported Supported $ pm-is-supported --hibernate && echo Supported Supported $ pm-is-supported --suspend-hybrid && echo Supported Supported
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 22 kernel bugs. Fedora 22 has now been rebased to 4.2.3-200.fc22. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 23, and are still experiencing this issue, please change the version to Fedora 23. If you experience different issues, please open a new bug report for those.
I rechecked this earlier this week, and suspend is working for me on the F23 beta, while hibernate has changed to behave like a system shutdown rather than crashing.
This is indeed fixed in Fedora 23.
(In reply to Nadim Kobeissi from comment #13) > This is indeed fixed in Fedora 23. What kernel version are you running? I just upgraded to Fedora 23 based on your comment, and with kernel version 4.2.6-301.fc23.x86_64 my computer crashes immediately on suspend. The last working kernel for me was 3.19.7-200 on Fedora 21, but unfortunately I lost that one during the upgrade to 23, and cannot find an RPM for in anywhere.
Oliver, perhaps it was also triggered by a BIOS update. Try downloading the latest BIOS image from HP's website and installing it?
(In reply to Nadim Kobeissi from comment #15) > Oliver, perhaps it was also triggered by a BIOS update. Try downloading the > latest BIOS image from HP's website and installing it? I just installed the most recent BIOS (F.2D Rev.A, released 11/12/2015). The changelog says: "Fixes an intermittent issue where the system stops functioning (hangs) while the system enters sleep mode (S3)." Sounds great, but suspend still doesn't work for me. :( It might be that I have a slightly different model laptop than you: HP Spectre x360 - 13t-4000 CTO (ENERGY STAR)
Update: I think I found the problem. One or more of the power savings options enabled by powertop are causing the lock-up on suspend. With all power saving options disabled, the laptop now suspends and resumes on kernel version 4.2.6-301. There are more powertop tunables on this new kernel than there were on 3.19.7, and I am guessing that one of the new tunables is the problem. As the tunables have a significant effect on battery life, I shall try enabling them one by one to see which causes a lock-up. That'll take a while.
(In reply to Oliver Kreylos from comment #17) > Update: I think I found the problem. One or more of the power savings > options enabled by powertop are causing the lock-up on suspend. With all > power saving options disabled, the laptop now suspends and resumes on kernel > version 4.2.6-301. > > There are more powertop tunables on this new kernel than there were on > 3.19.7, and I am guessing that one of the new tunables is the problem. > > As the tunables have a significant effect on battery life, I shall try > enabling them one by one to see which causes a lock-up. That'll take a while. This is odd. I also use powertop and have every single tunable set to the "Good" setting, and I can still suspend/sleep and wake without issue.
Does your touch screen still work when you enable "Autosuspend for USB device Touchscreen [ELAN]"? Mine doesn't.
[Sorry for all the messages while I try sorting this out.] Turns out powertop tunables probably weren't the issue. I booted with the additional grub command line options to enable the built-in soundcard (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1441852 ), and while that didn't fix sound, it seems to have fixes suspend/resume, even with tunables enabled. Strange thing: I booted one more time, *without* the additional grub options, and now both built-in sound and suspend/resume are working. And because I booted without the options, even backlight control is working. It is possible that booting with those options once toggled a bit in the BIOS somewhere that shook things into order. Right now everything is working for me, but I'll keep an eye out for future problems. And immediate correction: I booted yet another time without the grub options, and sound is gone, and suspend crashes again.
Oliver, I don't tend to use Suspend/Hibernate myself, but are you still seeing problems here? Having this as CLOSED NOTABUG suggests that Suspect/Sleep/Hibernate on the Spectre 360 are expected to work in F23+, but that may not be the case.
(In reply to Nick Coghlan from comment #21) > Oliver, I don't tend to use Suspend/Hibernate myself, but are you still > seeing problems here? > > Having this as CLOSED NOTABUG suggests that Suspect/Sleep/Hibernate on the > Spectre 360 are expected to work in F23+, but that may not be the case. Hi Nick, thanks for checking in. I am currently running kernel 4.5.5-201 (64-bit) on F23 on this laptop, and suspend/resume and sound output via the in-CPU soundcard work *if* I add the following options to the kernel boot line: acpi_osi="!Windows 2012" acpi_osi="!Windows 2013" If I leave those off, things happen that I have not been able to reproduce reliably. Usually sound goes away first, and just rebooting with the options added does not fix it; I need to reboot (with the options) one or sometimes more than one times before sound comes back. The computer usually (but not always) locks on suspend. If I have the options there on every reboot, the laptop works fairly reliably.
OK, thanks - I'm going to put this back to "NEW" then, as I also have those boot options set, and "works with particular custom boot options set" isn't the same thing as working properly by default.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.