Bug 1480602 - Kernel 4.12.5-200.fc25 fails to suspend on a Lenovo E531
Kernel 4.12.5-200.fc25 fails to suspend on a Lenovo E531
Status: NEW
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
26
x86_64 Linux
unspecified Severity medium
: ---
: ---
Assigned To: Kernel Maintainer List
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-08-11 09:04 EDT by David H. Gutteridge
Modified: 2017-08-16 09:30 EDT (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
journalctl -k output (274.77 KB, text/plain)
2017-08-11 09:05 EDT, David H. Gutteridge
no flags Details

  None (edit)
Description David H. Gutteridge 2017-08-11 09:04:21 EDT
Description of problem:

After upgrading to kernel 4.12.5-200.fc25, my Lenovo E531 fails to suspend. It has suspended with no issues from kernel 3.11 to 4.9, after which there were intermittent issues which I worked around by setting /sys/power/pm_async to 0. That workaround no longer applies with 4.12, instead the machine consistently fails to suspend.

Version-Release number of selected component (if applicable):
4.12.5-200.fc25

How reproducible:
Always

Steps to Reproduce:
1. Close lid of laptop
2. Observe it fails to suspend
3. Observe various messages in dmesg that relate to the failure

Actual results:
Failure to suspend

Expected results:
Suspension

Additional info:
Snippet from kernel log:

[ 2418.216600] PM: Syncing filesystems ... done.
[ 2418.711550] PM: Preparing system for sleep (mem)
[ 2418.712437] Freezing user space processes ... (elapsed 0.002 seconds) done.
[ 2418.715259] OOM killer disabled.
[ 2418.715261] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[ 2418.716757] PM: Suspending system (mem)
[ 2418.716790] Suspending console(s) (use no_console_suspend to debug)
[ 2418.742342] rmi4_f01 rmi4-00.fn01: Failed to write sleep mode: -6.
[ 2418.742345] rmi4_f01 rmi4-00.fn01: Suspend failed with code -6.
[ 2418.742347] rmi4_physical rmi4-00: Failed to suspend functions: -6
[ 2418.742350] rmi4_smbus 8-002c: Failed to suspend device: -6
[ 2418.742358] dpm_run_callback(): rmi_smb_suspend+0x0/0x50 [rmi_smbus] returns -6
[ 2418.742360] PM: Device 8-002c failed to suspend: error -6
[ 2418.742363] PM: Some devices failed to suspend, or early wake event detected
[ 2418.748592] PM: resume of devices complete after 6.223 msecs
[ 2418.748916] PM: resume devices took 0.006 seconds
[ 2418.748983] PM: Finishing wakeup.
[ 2418.748984] OOM killer enabled.
[ 2418.748987] Restarting tasks ... done.
[ 2418.751321] PM: Syncing filesystems ... 
[ 2418.764380] rmi4_f03 rmi4-00.fn03: rmi_f03_pt_write: Failed to write to F03 TX register (-6).
[ 2418.948815] done.
[ 2418.948826] PM: Preparing system for sleep (freeze)
[ 2418.949090] Freezing user space processes ... (elapsed 0.002 seconds) done.
[ 2418.951905] OOM killer disabled.
[ 2418.951907] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[ 2418.953392] PM: Suspending system (freeze)
[ 2418.953394] Suspending console(s) (use no_console_suspend to debug)
[ 2418.978304] rmi4_f01 rmi4-00.fn01: Failed to write sleep mode: -6.
[ 2418.978307] rmi4_f01 rmi4-00.fn01: Suspend failed with code -6.
[ 2418.978310] rmi4_physical rmi4-00: Failed to suspend functions: -6
[ 2418.978312] rmi4_smbus 8-002c: Failed to suspend device: -6
[ 2418.978321] dpm_run_callback(): rmi_smb_suspend+0x0/0x50 [rmi_smbus] returns -6
[ 2418.978323] PM: Device 8-002c failed to suspend: error -6
[ 2418.978325] PM: Some devices failed to suspend, or early wake event detected
[ 2418.984840] PM: resume of devices complete after 6.509 msecs
[ 2418.985195] PM: resume devices took 0.007 seconds
[ 2418.985241] PM: Finishing wakeup.
[ 2418.985242] OOM killer enabled.
[ 2418.985244] Restarting tasks ... done.
Comment 1 David H. Gutteridge 2017-08-11 09:05 EDT
Created attachment 1312139 [details]
journalctl -k output
Comment 2 David H. Gutteridge 2017-08-11 09:38:36 EDT
Possibly related to bug 1431375.
Comment 3 David H. Gutteridge 2017-08-16 09:30:26 EDT
I can also duplicate this with 4.12.5-300.fc26, unsurprisingly I suppose (I didn't see any differences in downstream patches between it and the Fedora 25 version). I've moved this bug to Fedora 26.

Note You need to log in before you can comment on or make changes to this bug.