FS#54793 - [linux] Dell Latitude 5285 does not wake up after suspend to memory

Attached to Project: Arch Linux
Opened by Nico Schottelius (telmich) - Thursday, 13 July 2017, 19:20 GMT
Last edited by Toolybird (Toolybird) - Thursday, 02 March 2023, 06:57 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

When suspending by closing the attached travel keyboard or my running "echo mem >/sys/power/state", the device suspends.
However waking up is not possible by opening the lid nor by pressing the power button.

The only possibility to restart the device is by holding down the power button for several seconds, multiple times.

According to the Dell website, this device should work with Ubuntu - I haven't tried that yet, however might give this a try to verify if this is arch specific.

If anyone else has seen a similar problem here, I would be grateful for any feedback. I have found various sites citing wakeup issues with the recommendation to upgrade some windows 10 drivers, but well...

Running 4.11.9-1-ARCH, no special boot options currently.


Additional info:
* package version(s)
* config and/or log files etc.


Steps to reproduce:
This task depends upon

Closed by  Toolybird (Toolybird)
Thursday, 02 March 2023, 06:57 GMT
Reason for closing:  None
Additional comments about closing:  Very old/stale bug. Please request reopen if still reproducible on current kernels.
Comment by Nico Schottelius (telmich) - Thursday, 13 July 2017, 19:53 GMT
Just confirmed that it also happens with the install medium, which is 4.11.7-1-ARCH
Comment by Nico Schottelius (telmich) - Thursday, 13 July 2017, 19:59 GMT
whatever it is - it is interesting to see that the problem also exists under some circumstances with windows 10 - which speaks for something that might be solvable in Linux as well
Comment by Nico Schottelius (telmich) - Thursday, 13 July 2017, 20:00 GMT
Ah, and here is the related thread: https://www.reddit.com/r/Windows10/comments/3fmsg8/windows_10_is_great_but_seems_to_have_a_problem/
Comment by Nico Schottelius (telmich) - Wednesday, 26 July 2017, 19:29 GMT
Found the problem: the notebook does not support ACPI S3. Using 54a7d50b9205b5064628c1d10de6531d2d9fbc90 (some commits before 4.13) and setting /sys/power/mem_sleep to s2idle, gets it working.

Loading...