When I boon in minimalisting environment (single user mode, without Xorg etc.) and try to s2ram it hangs on "Snapshotting system state". Suspending led is blinking and system is unresponsible.
my boot params are:
root=/dev/sda4 resume=swap:/dev/sda1 acpi_sleep=s3_bios nomodeset
My laptop is eMachines D440-1202G16Mi, with AMD V120 processor onboard. I can provide additional information (lspci, lshw) if it is requered.
First, please try with acpi_sleep=nonvs in the kernel command line.
(In reply to comment #1)
The same result (failure) for s2disk. (There was an mistake in my previous post : it failed for s2disk, for s2ram it says:
Machine is unknown.
This machine can be identified by:
sys_vendor = "eMachines "
sys_product = "eMachines D440 "
sys_version = "V1.04 "
bios_version = "V1.04 "
See http://suspend.sf.net/s2ram-support.html for details.
If you report a problem, please include the complete output above.
Please try the following test:
# echo devices > /sys/power/pm_test
# echo disk > /sys/power/state
and see if it gets back to the command prompt (it should do that after about 5-10 seconds, depending on how much it takes to resume devices on your machine).
Thanks, but there is no /sys/power/pm_test
ls -lah /sys/power/
drwxr-xr-x 2 root root 0 Sep 24 12:38 .
drwxr-xr-x 12 root root 0 Sep 24 2010 ..
-rw-r--r-- 1 root root 4.0K Sep 24 12:38 disk
-rw-r--r-- 1 root root 4.0K Sep 24 12:39 image_size
-rw-r--r-- 1 root root 4.0K Sep 24 12:39 pm_async
-rw-r--r-- 1 root root 4.0K Sep 24 12:39 resume
-rw-r--r-- 1 root root 4.0K Sep 24 12:38 state
I simply tried to do "echo disk > /sys/power/state" and it hanged as usual.
I don't know, whether the following be useful: I reported other bug, that my touchpad is recognized as generic PS/2 mouse, and I found the touchpad driver uses some new protocol... and it's developing in process, but some people aslo noted hibernate problems (https://bugzilla.kernel.org/show_bug.cgi?id=14660).
I uncheked all mise in device drivers, recompiled-rebooted... but it hangs again.
What can I do else?
Please build the kernel with CONFIG_PM_DEBUG set and carry out the test from comment #3.
I have done it. It resumes after a few seconds. Do you need dmesg output after resume? What is the next?
What additional info can I provide?
It's great that kernel bugzilla is back.
can you please verify if the problem still exists in the latest upstream
bug closed as there is no response from the bug reporter.
please feel free to reopen it if the problem still exists in the latest upstream kernel.