Bug 3859

Summary:	Suspend (S3) only works once per reboot
Product:	ACPI	Reporter:	Siddartha Naidu (snaidu)
Component:	Power-Sleep-Wake	Assignee:	Shaohua (shaohua.li)
Status:	REJECTED INSUFFICIENT_DATA
Severity:	normal	CC:	acpi-bugzilla, mjg59-kernel
Priority:	P2
Hardware:	i386
OS:	Linux
Kernel Version:	2.6.9-gentoo-r1	Subsystem:
Regression:	---	Bisected commit-id:
Attachments:	/var/log/debug after successful suspend-resume /var/log/debug after reboot from hang following second suspend

Description Siddartha Naidu 2004-12-04 00:56:02 UTC

Distribution: gentoo
Hardware Environment: Toshiba Satellite A15-S1292
Software Environment: ACPI enabled, APM disabled
Problem Description:
ACPI generally works well including Toshiba extensions. Suspend-to-RAM works
perfectly the first time with the power led flashing amber after suspend. Resume
also proceeds without any difficulty. However, on the second suspend attempt the
screen blanks but the power led remains solid green. The system is entirely
unresponsive except until (hard) powered down and restarted.

Including the /var/log/debug for success and failure cases. It seems in the
second attempt it never reaches the enter_state call in kernel/power/main.c.

Sorry for posting to the bugzilla-list, missed the correct link.

Steps to reproduce:

0) [Boot]
1) [Suspend] acpitool -s (or echo 3 >/proc/acpi/sleep)
2) [Resume] PWR button
3) [Suspend] acpitool -s
[hangs]

Comment 1 Siddartha Naidu 2004-12-04 00:58:00 UTC

Created attachment 4216 [details]
/var/log/debug after successful suspend-resume

Comment 2 Siddartha Naidu 2004-12-04 01:00:21 UTC

Created attachment 4217 [details]
/var/log/debug after reboot from hang following second suspend

Comment 3 Shaohua 2004-12-05 17:19:47 UTC

Please try to unload sound card driver and USB driver before suspend. The 
drivers caused many similar issues. Thanks.

Comment 4 Siddartha Naidu 2004-12-06 16:58:56 UTC

I unloaded all USB and sound modules but found the same behaviour. I checked the
logs and they are identical to those posted previously. If there is something I
can do to extract more revealing information please let me know. Thank you.

Comment 5 Matthew Garrett 2005-01-01 10:29:26 UTC

Try disabling DRI - this seems to occur with some video drivers.

Comment 6 Adrian Bunk 2006-03-01 15:18:43 UTC

Please reopen this bug:
- if it is still present in recent 2.6 kernels and
- you can answer Matthew's question.