Bug 13735 - system fails to suspend ram
Summary: system fails to suspend ram
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Power Management
Classification: Unclassified
Component: Hibernation/Suspend (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: Zhang Rui
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-07 04:21 UTC by Brent Millare
Modified: 2012-05-24 07:19 UTC (History)
3 users (show)

See Also:
Kernel Version: 2.6.30
Subsystem:
Regression: No
Bisected commit-id:


Attachments
dmesg after failure (191.90 KB, text/plain)
2009-07-07 04:21 UTC, Brent Millare
Details
lspci -vv output (29.55 KB, text/plain)
2009-07-07 04:22 UTC, Brent Millare
Details
Log after console mode (163.13 KB, application/octet-stream)
2009-07-13 04:41 UTC, Brent Millare
Details
acpidump (111.73 KB, application/octet-stream)
2009-09-21 03:54 UTC, Brent Millare
Details

Description Brent Millare 2009-07-07 04:21:44 UTC
Created attachment 22242 [details]
dmesg after failure

To reproduce:
1. Boot computer
2. sudo hibernate-ram --force

Computer attempts to suspend but fails and resumes as normal. An error message to console reads "/bin/echo: write error: Resource temporarily unavailable"
Comment 1 Brent Millare 2009-07-07 04:22:47 UTC
Created attachment 22243 [details]
lspci -vv output

Hardware is a Dell Vostro 1400 laptop
Comment 2 Brent Millare 2009-07-07 04:25:04 UTC
Also suspend worked for sure in 2.6.26, I had the same problem in >2.6.29, may 28 too but I can't remember.
Comment 3 ykzhao 2009-07-13 03:29:55 UTC
Hi, Brent
    Will you please boot the system into the console mode and see whether the box can enter the suspend state?
    From the log it seems that one user space application can't be freezed.
    Thanks.
Comment 4 Brent Millare 2009-07-13 04:41:04 UTC
Created attachment 22328 [details]
Log after console mode

Hello,

Should I try single user mode? It still fails after closing X, xdm, and removing nvidia module.
Comment 5 Brent Millare 2009-07-13 04:45:18 UTC
Actually, I just tried when in single user mode and it still fails with the same error.
Comment 6 ykzhao 2009-09-11 03:02:25 UTC
hi, Brent
    Sorry for the late response.
    Will you please try the boot option of "maxcpus=1" and see whether it still fails?
   Thanks.
Comment 7 Brent Millare 2009-09-11 03:08:00 UTC
Hi ykzhao,

IT WORKS! (With those args) Hopefully that will be the key to fixing it.

Best,
Brent
Comment 8 ykzhao 2009-09-21 03:50:16 UTC
Hi, Brent
    Thanks for your test. 
    will you please attach the output of acpidump?

Thanks.
Comment 9 Brent Millare 2009-09-21 03:54:51 UTC
Created attachment 23123 [details]
acpidump
Comment 10 Zhang Rui 2009-10-15 08:10:48 UTC
does the problem still exist in kernel 2.6.31?
we have two acpi patches shipped recently, and now all the SMI calls invoked in AML code are scheduled on CPU0.
Comment 11 Brent Millare 2009-11-05 02:52:12 UTC
The problem still exists for me using 2.6.31-r2 and 2.6.31-r4. Now the system hangs with the flashing underscore instead of resuming back into X
Comment 12 Zhang Rui 2010-01-14 07:25:55 UTC
please just run "echo disk > /sys/power/state" as root user to hibernate instead of "sudo hibernate-ram --force".
If the problem still exist, please re-try latest upstream kernel, say 2.6.32
Comment 13 Brent Millare 2010-01-14 20:06:22 UTC
on 2.6.31 echo mem > /sys/power/state works now although I need to be shutdown xdm and upon resuming I lose the backlight and need to blind restart xdm to resume normal operation

will try 2.6.32 when have time

Any idea on potential solutions or pointers to suspending and resuming a full X session?
Comment 14 Ted Logan 2010-02-03 17:59:17 UTC
Im on fc12 64bit

Linux laptop 2.6.31.12-174.2.3.fc12.x86_64 #1 SMP Mon Jan 18 19:52:07 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux

Vostro 1520.  I am having this same problem, can't suspend to ram.  if I do maxcpus=1, since I have core duo 2, won't that cause performance problems?
Comment 15 Brent Millare 2010-02-03 19:28:07 UTC
Changing to maxcpus=1 was used to help identify the problem, not to be confused with a solution. Changing it to 1 will deactivate the other core and result in less multithreaded performance.
Comment 16 Zhang Rui 2012-01-18 01:51:29 UTC
hey, all,

It's great that kernel bugzilla is back.

can anyone of you verify if the problem still exists in the latest upstream
kernel please?
Comment 17 Zhang Rui 2012-05-24 07:19:16 UTC
bug closed as there is no response from the bug reporter.

Note You need to log in before you can comment on or make changes to this bug.