[SOLVED} Suspend to ram does not work (with sleep, s2ram, pm-utils)

Question

Hi.
I would like to ask for one thing: i can't suspend to ram or resume from suspend to ram.
I treid to check over www in order to find some help, some solutions, and how to fix that. Unfortunately, i found these:
https://forums.opensuse.org/showthread. … 13-2/page2
https://bugzilla.opensuse.org/show_bug.cgi?id=913105
https://forums.opensuse.org/showthread. … S-13-1-x64
Bug 91921 - WD 2TB Caviar black causes hard lock on resume S2RAM
https://bugzilla.kernel.org/show_bug.cgi?id=91921
In fact, when i was researching of this problem i wanted to check if my graphic card and memory are failing so a did few changes (removed memory stick and so one) but in doing this i removed almost all of my hard disk drives because i didn't want to hurt them with many reboots or resets.
What did i find? It is strange, kernel version is not important because i checked most of them.
I removed 2x2TB Seagate F14 series along with 4x3TB WD Green. Then i checked s2ram, it went to suspend, and resumes correctly. Everything works. I put it to sleep with s2ram -f -a 1. Works
I attached my 4x3TB WD Green drives. I put computer to sleep with s2ram...it causes hard lock, black screen, i could do only poweroff by powerbutton. s2ram -f -a 1 causes freez. Sometimes, but not constantly, s2ram -f -a 3 -p is being able to suspend...(mostly it does a freez, hard lock computer) but sometimes it is able to put it to a sleep, but resume just freezes everyting - no blinking cursor, no blinking num lock led and so on.
I know that you would suggest me to check logs - this is the main problem. Logs for pm-suspend works when i suspend or resume without WD drives attached. When i have them connected, i'm not able to check pm-logs because computer hangs, freezes and logs are not being stored/writed to pm-suspend.log and pm-powersave.log.
Could somebody help? Point me to a solution? I can't check logs because there are not any when freezing occurs. I checked openSuse thread and many others and for other systems there were some kernel fixex, patches.
They wrote that WD blacks are at fault because they don't have APM. Well, in fact my WD Green have APM with very aggresive factory settings: they park heads over 8 seconds not being used. I disabled it in firmware but disabling it is not the point and not the problem. People have the same problem even with APM and parking heads on other WD drives, i found it that some have it with WD Red's drives and even with very old 320GB WD Blue series - what is more funny, i have 640GB AAKS blue from WD and with this drive i can suspend or resume - APM on this drive is also unavilable, like in Green series because i changed it with wdidle with prebootable cd. I can't  supend or resume with 3TB WD Greens.
BTW - suspend to disk, with pm-utils and uswsusp works ok, in 100% every time. (i had to add "shutdown method = shutdown" to /etc/suspend.conf from uswsusp package).
On Windows machine it works. Can suspend, can resume, can hibernate.
Last edited by firekage (2015-03-07 03:27:28)

Answer 1

Hm, sometimes i found myself astonished because some things just does not work at all on one machine, while the other one has no problem at all. I was trying to find why suspend to ram won't work at all...and while i was searching i found one topic that was leading to upower dbus. Similar problem with upower i found, by coincidence, on Manjaro forum.
dbus-send --system --print-reply --dest="org.freedesktop.UPower" /org/freedesktop/UPower org.freedesktop.UPower.Suspend
this command above returns all the time:
Error org.freedesktop.DBus.Error.UnknownMethod: Method "Suspend" with signature "" on interface "org.freedesktop.UPower" doesn't exist
I tried this:
sudo systemctl enable acpid.service
sudo systemctl --system daemon-reload
sudo systemctl restart systemd-logind
As soon as i enabled and started acpid.service...my supend to ram, from kde, works like a charm, without graphic problem, or freezing.
There is few question: why on my desktop suspend doesen't work out of the box, when even archwiki says it should? Why on my netbook machine (Acer AOD270) that has the same package installed it works out of the box? Why on my desktop machine acpid.service was not enabled, was not started and was not running while on the notebook it does?
Anyway...i fixed it by a big coincidence because on Fedora forum somebody has problem with suspend to ram with nvidia GTX750 and this card was new like my card (GTX660). He posted the same problem with upower that i posted in quotes and because of this i found another thing on Manjaro forum and that was it!
BTW - this problem, i now think, is not related to my WD drives because it works with them. I think that there was another one ugly thing that broke my suspend to ram ability - bios of my motherboard (so called uefi bios with support for old one) has no option for S1-S5 stated (like the previous motherboards had) and only have ASPM...and ASPM is in my opinion broken but i will try to veryfi it one again later.
Last edited by firekage (2015-03-07 03:29:20)