Suspend but won't resume

[ocgltd]

I have a Shuttle XS35GT-804 mobo which I am trying to suspend to S3 (running 2.6.32.21-168.fc12.x86_64). I do so with a script that runs:

echo -n mem > /sys/power/state

The computer appears to go to sleep, but it won't wake up! I try with WOL magic packets but that doesn't work, so I press the power button and although the power button lights up, the PC unresponsive (no video signal, no disk light, etc)

The first question is, am I suspending the right way?

If so, what could be wrong here?

Thanks!

[CSchwangler]

What desktop environment are you using? Gnome, KDE, XFCE and LXDE have action buttons for suspend/hibernate. Have you tried these buttons and how are they working? You may also wish to try pm-suspend or pm-hibernate from a terminal, both as your user and as root.

[Skull One]

The first question is, am I suspending the right way?

If so, what could be wrong here?


Yes you are. But there is some software/hardware that need some caution.
pm-suspend try to handle this (look at the scripts in pm-utils package).

If it still fails with pm-suspend, you will need to find where is the problem.
It is a quite long procedure : http://www.mjmwired.net/kernel/Documentation/power/basic-pm-debugging.txt
In my case, it was the module 'atl1'. I just need to unload it before suspend, and to reload it after.
Good luck ! ;)

[ocgltd]

I'm running Gnome (but need to suspend from a script).

If I "echo -n mem > /sys/power/state" the machine will actually suspend, but it won't wake up properly (just blank screen, no action)

Should I still check the link above?

[CSchwangler]

Why don't you first try pm-suspend and report the results here?

[Skull One]

I'm running Gnome (but need to suspend from a script).

If I "echo -n mem > /sys/power/state" the machine will actually suspend, but it won't wake up properly (just blank screen, no action)

Should I still check the link above?

I was in that case. As I wrote above, the debugging procedure pointed out the problem : atl1.
Check if you are using this module first.

lsmod | grep atl1


If it is not the case, try the debugging procedure to find where is the problem.

P.S. : Did you try pm-suspend ?

[ocgltd]

pm-suspend fails, so I ran through the diagnostic procedures mentioned above, and my system fails on the "echo processors > /sys/power/pm_test" test.

Sooo...the next step in the diagnostic page is "report it"....but I have no idea how/where to report it. I ran the pm-utils-bugreport-info.sh script but I don't think that automatically sends anything anywhere...

[Skull One]

Hum...
You have a dual core CPU, did you try the proposed trick which is turning off cpu1 before ?

echo 0 > /sys/devices/system/cpu/cpu1/online

then do the test

echo processors > /sys/power/pm_test


For pm-utils, you can fill a bug-report at https://bugs.freedesktop.org/

[David Batson]

Probably not related, but I have a desktop PC that my brother gave me that has Vista 64-bit installed. Same symptoms as the OP. Power lights come on, but the monitor will not come on. While Googling for a solution, I read that if there was 4 GB or more of RAM installed, that would cause a resume from suspend problem with this particular ASUS motherboard (AMD processor). Weird.