Bug 6851
Summary: | Suspend to RAM and Ondemand Lockup/Stack trace | ||
---|---|---|---|
Product: | Power Management | Reporter: | Brandon Philips (brandon) |
Component: | cpufreq | Assignee: | Rafael J. Wysocki (rjwysocki) |
Status: | CLOSED CODE_FIX | ||
Severity: | normal | CC: | acpi-bugzilla, davej, pavel, rjwysocki |
Priority: | P2 | ||
Hardware: | i386 | ||
OS: | Linux | ||
Kernel Version: | 2.16.18-rc1, 2.6.18-rc1-mm1, 2.6.18-rc1-mm2 | Subsystem: | |
Regression: | --- | Bisected commit-id: | |
Attachments: | 2.6.18-rc1-mm1 .config |
Description
Brandon Philips
2006-07-17 08:38:50 UTC
Suspend to RAM _not_ software suspend. Created attachment 8568 [details]
2.6.18-rc1-mm1 .config
Does Comment #1 mean that the system resumes successfully from suspend to disk if the ondemand governor is used? Problem: When ondemand is the govenor suspend to ram fails. Suspend to ram works with the performance govenor. On lkml, there's currently discussion about ondemand's locking being termianlly broken. This is probably one of the symptoms Please verify that this issue is gone using 2.6.18-rc4 or later. (moving to PM/cpufreq, since this is not an ACPI issue) Does the lack of activity mean the issue has been fixed? I assume the problem has been fixed, so I'm closing the bug. Please reopen if I'm wrong. |