FS#53522 - [linux] Cannot resume laptop from suspend-to-ram, but works when going back to linux-lts

Attached to Project: Arch Linux
Opened by Felix Triebel (triebefx) - Saturday, 01 April 2017, 17:04 GMT
Last edited by Eli Schwartz (eschwartz) - Tuesday, 26 December 2017, 13:04 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:
Since a few weeks I'm experiencing problems with resume from suspend-to-ram, probably since upgrading to kernel 4.10. I'm not able to get any logs from resume. Resume works fine when running on linux-lts kernel, see attached dmesg* files.

Random things I tried without success:
- this kernel parameter doesn't have any effect "acpi_sleep=nonvs", one should update the Wiki:
https://wiki.archlinux.org/index.php/Power_management/Suspend_and_hibernate#VAIO_Users
- no effect with this parameter either: pcie_port_pm=off

Additional info:
* linux 4.10.6-1
* linux-lts 4.9.20-1
* laptop: Sony VAIO SVS1511 X9EB

Steps to reproduce:
1. echo 0 > /sys/power/pm_async
2. echo 1 > /sys/power/pm_trace
3. echo core > /sys/power/pm_test
4. dmesg > dmesg_before; echo mem > /sys/power/state; dmesg > dmesg_after
results in hang and dmesg_after never gets written
5. reboot and PM trace shows this info:
Nov 10 19:57:46 vaio kernel: Magic number: 0:138:999
Nov 10 19:57:46 vaio kernel: hash matches drivers/base/power/main.c:800
Nov 10 19:57:46 vaio kernel: rtc_cmos 00:01: hash matches
Nov 10 19:57:46 vaio kernel: pnp0: hash matches
Nov 10 19:57:46 vaio kernel: rtc_cmos 00:01: setting system clock to 2056-11-10 18:57:27 UTC (2741108247)
   dmesg (65.7 KiB)
   dmesg_before (58.7 KiB)
   dmesg_after (64.1 KiB)
This task depends upon

Closed by  Eli Schwartz (eschwartz)
Tuesday, 26 December 2017, 13:04 GMT
Reason for closing:  Fixed
Additional comments about closing:  OP request: Seems to be fixed with linux 4.14.8-1
Comment by Felix Triebel (triebefx) - Monday, 31 July 2017, 04:25 GMT
Same problem with 4.11 and now 4.12 kernels, but fortunately I can still work with 4.9.
Comment by Jonas Heinrich (onny) - Tuesday, 12 September 2017, 15:33 GMT
You can now try linux 4.13 in the testing repo.
But I'm also encountering this bug with the latest kernel :(
I will post some more debug infos here soon.
Comment by Jonas Heinrich (onny) - Friday, 29 September 2017, 10:56 GMT
Bug still present in 4.13.4

Loading...