[SOLVED] Need help figuring out why pc won't resume after suspending.

MudkipLinux · 2019-02-28 13:34:14

This is the first time I used suspend and discovered that I can't wake the system up after suspending.

Pressing the power button, hitting keys on the keyboard, or moving the mouse doesn't do anything. Hitting caps lock or num lock doesn't turn on the led on the keyboard, this means that the system is still suspended

The cpu and gpu fans keep spinning.

I'm using open source ATI driver with HD 7850.

journalctl doesn't show any errors. These are the entry from the last boot before I suspended it:

Feb 28 13:49:26 worktop systemd[1]: Reached target Sleep.
Feb 28 13:49:26 worktop systemd[1]: Starting Suspend...
Feb 28 13:49:26 worktop kdeinit5[711]: ktp-kded-module: "screen-saver-away" presence change request: "away" ""
Feb 28 13:49:26 worktop kdeinit5[711]: ktp-kded-module: plugin queue activation: "away" ""
Feb 28 13:49:26 worktop ksmserver[779]: CreateNotify: 48234551
Feb 28 13:49:26 worktop systemd-sleep[12091]: Suspending system...
Feb 28 13:49:26 worktop kernel: PM: suspend entry (s2idle)

How do I diagnose this?

Last edited by MudkipLinux (2019-03-12 01:46:51)

Head_on_a_Stick · 2019-02-28 20:28:11

MudkipLinux wrote:

Feb 28 13:49:26 worktop kernel: PM: suspend entry (s2idle)

Try setting mem_sleep_default=shallow or perhaps mem_sleep_default=deep as a kernel command line parameter.

Check which options are available on your hardware with

cat /sys/power/mem_sleep

Other suggestions here: https://wiki.archlinux.org/index.php/Po … ibernating

MudkipLinux · 2019-03-01 12:32:18

Head_on_a_Stick wrote:

MudkipLinux wrote:
Feb 28 13:49:26 worktop kernel: PM: suspend entry (s2idle)
Try setting mem_sleep_default=shallow or perhaps mem_sleep_default=deep as a kernel command line parameter.
Check which options are available on your hardware with
cat /sys/power/mem_sleep
Other suggestions here: https://wiki.archlinux.org/index.php/Po … ibernating

It shows s2idle shallow only. I had a look at my bios and it says that it supports S1 only. Maybe that's what causing this problem.

Head_on_a_Stick · 2019-03-01 19:50:15

MudkipLinux wrote:

It shows s2idle shallow only. I had a look at my bios and it says that it supports S1 only.

S1 is the same as shallow so try setting that as the default state.

MudkipLinux · 2019-03-06 14:05:53

Head_on_a_Stick wrote:

MudkipLinux wrote:
It shows s2idle shallow only. I had a look at my bios and it says that it supports S1 only.
S1 is the same as shallow so try setting that as the default state.

Ok, I set it to shallow. The system seems to come back from sleep now but the problem is I end up with a blank screen. The screen turns on but doesn't show anything. Previously, the screen would not even turn on.

The logs don't mention anything about resuming from suspend either.

Head_on_a_Stick · 2019-03-07 08:24:35

What is your graphics hardware and which driver is it running?

MudkipLinux · 2019-03-07 12:18:55

Head_on_a_Stick wrote:

What is your graphics hardware and which driver is it running?

It's a Radeon HD 7850, using open source radeon driver.

01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Pitcairn PRO [Radeon HD 7850 / R7 265 / R9 270 1024SP]
        Subsystem: Gigabyte Technology Co., Ltd Pitcairn PRO [Radeon HD 7850 / R7 265 / R9 270 1024SP]
        Kernel driver in use: radeon
        Kernel modules: radeon, amdgpu

Also, I realized that my keyboard is also not functional when the screen turns on. The keyboard lights up but hitting caps lock doesn't do anything. There's probably something preventing the system from resuming.

Head_on_a_Stick · 2019-03-10 15:05:08

Does the screen still blank if you switch to the amdgpu kernel driver?

See https://wiki.archlinux.org/index.php/AM … K)_support

Not sure about the keyboard issue though

MudkipLinux · 2019-03-11 09:45:18

Head_on_a_Stick wrote:

Does the screen still blank if you switch to the amdgpu kernel driver?
See https://wiki.archlinux.org/index.php/AM … K)_support
Not sure about the keyboard issue though

Seems like switching to amdgpu fixed the problem. I'm now able to suspend and resume without any problems. I thought that the default radeon driver was supposed to be more stable for southern island cards but looks like I was wrong. Even the wiki says that it's experimental. I'll be using this driver from now on.

Thanks a lot!

Head_on_a_Stick · 2019-03-11 20:31:28

Excellent :-)

Please add [SOLVED] to the thread title to help others who may have this problem.

Arch Linux

#1 2019-02-28 13:34:14

[SOLVED] Need help figuring out why pc won't resume after suspending.

#2 2019-02-28 20:28:11

Re: [SOLVED] Need help figuring out why pc won't resume after suspending.

#3 2019-03-01 12:32:18

Re: [SOLVED] Need help figuring out why pc won't resume after suspending.

#4 2019-03-01 19:50:15

Re: [SOLVED] Need help figuring out why pc won't resume after suspending.

#5 2019-03-06 14:05:53

Re: [SOLVED] Need help figuring out why pc won't resume after suspending.

#6 2019-03-07 08:24:35

Re: [SOLVED] Need help figuring out why pc won't resume after suspending.

#7 2019-03-07 12:18:55

Re: [SOLVED] Need help figuring out why pc won't resume after suspending.

#8 2019-03-10 15:05:08

Re: [SOLVED] Need help figuring out why pc won't resume after suspending.

#9 2019-03-11 09:45:18

Re: [SOLVED] Need help figuring out why pc won't resume after suspending.

#10 2019-03-11 20:31:28

Re: [SOLVED] Need help figuring out why pc won't resume after suspending.

Board footer