11.4 suspend to ram problem

English Hardware
#1

Hi,

I’m using Thinkpad T500 with Intel graphics.
Suspend to ram usually works first time I do it after fresh boot, but usually after wake up, subsequent suspend to ram makes the system hang.

In both cases, the laptop appears to be working to suspend to ram (HDD LED is blinking), and the suspend LED blinks, and if successful, the suspend LED stays on.
When it hangs, even after the laptop stop doing anything (no HDD LED), the suspend LED keeps blinking and nothing happens.

It was like this in 11.3 and I was hoping upgrading to 11.4 would fix this, but no luck.

Any ideas?

Thank you,
Joon

#2

Maybe your Swarp Partition is just to small in Relation to 8 GB Ram?

Regards
Martin
(pistazienfresser)

#3

It seems after adding S2RAM_OPTS="-f -a2" to a new file in /etc/pm/config.d/, suspend to ram is working at the moment. I need to test it many times for sure though. Hope this solves the problem!

SDB:Suspend to RAM - openSUSE

#4

H’m, I have somewhat similar problem.
Suspend to RAM works a couple of times (3-4)
and then on the 4-5 time hangs.

Can you write which chipset does your laptop have (Intel GM965)?
Did the workaround you posted help?

I have also found this one, but not sure if is related:
https://bugzilla.novell.com/show_bug.cgi?id=675926

#5

Yes. My /etc/pm/config.d/thinkpad.config file is:

:/etc/pm/config.d> cat thinkpad.config
S2RAM_OPTS="-f -a1"

Now I rarely have suspend to ram problem. Why don’t you try a couple of different options?

Regarding the chipset, actually I don’t know how to find out the chipset number. Smolt gave me Mobile 4 Series Chipset Integrated Graphics Controller with i915 driver. (Is there any command which gives me the information? lspci pretty much yield the same thing)

-Joon

#6

Thanks for the reply!

It seems that I have some different problem with Bluetooth or WiFi not wanting to suspend properly. The last couple of days i turn turn off Bluetooth/WiFi with killswitch (hardware button) and laptop suspends just fine. So I will probably follow that bug from my previous post:
https://bugzilla.novell.com/show_bug.cgi?id=675926

But I will use your variant as a backup if turns out
not to be a Bluetooth/WiFi problem, so thanks for the info.

Regarding the chipset, actually I don’t know how to find out the chipset number. Smolt gave me Mobile 4 Series Chipset Integrated Graphics Controller with i915 driver.
I just thought that you have the same chipset as me, but it seems not.
And now I don’t think this info is relevant. So don’t bother yourself checking.

But if for some reason you will need info about your
hardware in Linux, these commands might be useful
(they seem to be commonly installed by default):

lspci
**hwinfo
**dmidecode