Bug 1599087

Summary: System reboots instead of resuming from suspend
Product: [Fedora] Fedora Reporter: Brad Walker <bwalker>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 28CC: airlied, bskeggs, bwalker, ewk, hdegoede, ichavero, itamar, jarodwilson, jcline, jglisse, john.j5live, jonathan, josef, kernel-maint, linville, mchehab, mjg59, steved
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-11-26 21:01:12 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
suspend logs none

Description Brad Walker 2018-07-08 17:51:09 UTC 
Description of problem:

Did a fresh install of Fedora 28. Enabled suspend when laptop lid is shut. Then when the laptop lid is shut, the system does seem to correctly suspend. I see a lot of disk activity and then powers off. When I re-open the laptop lid and hit the power button, the system boots and if suspend never took place.

For a laptop, I would consider the suspend behavior to be critical for working.

Version-Release number of selected component (if applicable):

4.17.3-200.fc28.x86_64 kernel

How reproducible:

Everytime.

Steps to Reproduce:
1. Close laptop lid
2. Open laptop and hit power button
3. System boots into a fresh instance

Actual results:

System reboots into a new instance.

Expected results:

System resumes from where it was suspended.

Additional info:

Here is what /etc/systemd/logind.conf contains:

HandleLidSwitch=suspend
HandleLidSwitchExternalPower=suspend
HandleLidSwitchDocked=suspend


Here is what I see in the journal

...
Jul 07 16:37:15 localhost.localdomain systemd[1]: Reached target Sleep.
Jul 07 16:37:15 localhost.localdomain systemd[1]: Starting Suspend...
Jul 07 16:37:15 localhost.localdomain systemd-sleep[4320]: Suspending system...
Jul 07 16:37:15 localhost.localdomain kernel: PM: suspend entry (deep)
-- Reboot --

Here is what my grub file looks like.. I'm pretty confident the resume option is properly set.

[bwalker@localhost ~]$ cat /etc/default/grub 
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)"
GRUB_DEFAULT=saved
GRUB_DISABLE_SUBMENU=true
GRUB_TERMINAL_OUTPUT="console"
GRUB_CMDLINE_LINUX="rd.lvm.lv=fedora_localhost-live/root rd.lvm.lv=fedora_localhost-live/swap resume=/dev/mapper/fedora_localhost--live-swap rhgb"
GRUB_DISABLE_RECOVERY="true"
[bwalker@localhost ~]$ 


My system type is a HP Pavilion 17 (model 17-g121wm). Output from /proc/cpuinfo
model name	: AMD A10-8700P Radeon R6, 10 Compute Cores 4C+6G

In addition, I've checked the BIOS to see if there are any power options that I might have missed. There are NO options from the BIOS for configuring the power.  Also, I do have the latest version of the BIOS.

Like I've previously said, this seems like a critical behavior for laptops. So any help is most appreciated.

If there is anything you need for me to debug, I can certainly do that.
Comment 1 Jeremy Cline 2018-07-11 14:23:58 UTC 
Hi Brad,

Can you attach the complete kernel logs ("journalctl -k --no-hostname -b <boot number>")?

Did this work on previous kernels? If so, when did it stop working?
Comment 2 Brad Walker 2018-08-11 16:42:27 UTC 
I have no idea if this previously worked as this is my first Linux install on my laptop...

I have attached logs..
Comment 3 Brad Walker 2018-08-11 16:43:02 UTC 
Created attachment 1475235 [details]
suspend logs
Comment 4 Laura Abbott 2018-10-01 21:27:03 UTC 
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 28 kernel bugs.
 
Fedora 28 has now been rebased to 4.18.10-300.fc28.  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 29, and are still experiencing this issue, please change the version to Fedora 29.
 
If you experience different issues, please open a new bug report for those.
Comment 5 Laura Abbott 2018-11-26 21:01:12 UTC 
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks. If you are still experiencing this issue, please reopen and let us know if the bug is still present on the latest kernel.

(Please note: sometimes bugs get mistakenly closed during our mass closing. If you think your bug was closed in error please reopen)