Bug 8694 - S3: no resume - Acer Aspire 5652AWLMi
Summary: S3: no resume - Acer Aspire 5652AWLMi
Status: REJECTED INSUFFICIENT_DATA
Alias: None
Product: ACPI
Classification: Unclassified
Component: Power-Sleep-Wake (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: acpi_power-sleep-wake
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-07-01 05:13 UTC by Josef Hahn
Modified: 2007-10-06 14:24 UTC (History)
2 users (show)

See Also:
Kernel Version: 2.6.21-1.3228.fc7
Subsystem:
Regression: ---
Bisected commit-id:


Attachments

Description Josef Hahn 2007-07-01 05:13:15 UTC
Distribution: Fedora 7
Hardware Environment: Acer Aspire 5652AWLMi
Software Environment: Standard Fedora 7
Problem Description: After S3 Suspend (pm-suspend), resume will hang with blank screen and no reaction on blind-typing "find /" (so system is really dead, no screen problem). Will happen even when in runlevel 3 and even with "init=/bin/bash" kernel option. Happens not only in Fedora, but happened in Suse and Ubuntu, too, so i think, i can post it here since it will be a general kernel problem. I've tried many different quirk-combination, but nothing helped.

I've read about a debugging method using 

echo 1 > /sys/power/pm_trace
pm-suspend

which gives the line

dmesg | grep "hash mat"
  hash matches drivers/base/power/resume.c:70


so, resume_device_early seems to be the problem.

Steps to reproduce:
type "pm-suspend" on my notebook ;)


important fact: some times before, i used gentoo and with
"echo 3 > /proc/acpi/sleep" it was possible to suspend & resume....
Comment 1 Len Brown 2007-07-25 19:36:34 UTC
please include the output from lspci
also, please try with "acpi_sleep=s3_bios" if it has Intel graphics.

Also, you can get /proc/acpi/sleep back with CONFIG_ACPI_PROCFS=y,
let me know if that makes any difference.
Comment 2 Len Brown 2007-09-06 16:02:18 UTC
Is this still an issue in Linux-2.6.22.stable?
Comment 3 Adrian Bunk 2007-10-06 14:24:37 UTC
Please reopen this bug if it's still present with kernel 2.6.22.

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