Bug 3354 - S3 state hang the machine
Summary: S3 state hang the machine
Status: CLOSED CODE_FIX
Alias: None
Product: ACPI
Classification: Unclassified
Component: Power-Sleep-Wake (show other bugs)
Hardware: i386 Linux
: P2 high
Assignee: Venkatesh Pallipadi
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-09-07 03:45 UTC by Daniele Depetrini
Modified: 2004-11-08 14:29 UTC (History)
0 users

See Also:
Kernel Version: 2.6.8.1 vanilla
Subsystem:
Regression: ---
Bisected commit-id:


Attachments

Description Daniele Depetrini 2004-09-07 03:45:02 UTC
Distribution: Slackware 9.1
Hardware Environment: Ibm R40
Software Environment: Any
Problem Description: When I activate the S3 state, the machine stop (seems)
properly. The "moon" icon is activating. But after that, it's completely
blocked. Will stop to respond to any key (also a lont time pressure of power
button). The only solution is to detach the power supply AND the battery and reboot.

Steps to reproduce:
Comment 1 Vadim Zeitlin 2004-10-10 08:15:32 UTC
Distribution: any
Hardware: HP nw8000 (see
http://h18000.www1.hp.com/products/quickspecs/11798_na/11798_na.HTML)

I think I observe the same bug on another notebook, HP nw8000 with ATI FireGL T2
card. I've tried the following kernels: stock 2.6.4 from SuSE 9.1 (because this
one is ceritified by HP), 2.6.8-1 and 2.6.9-rc3 on Debian testing. In all cases,
all modules except the required ones (i.e. IDE ones), including USB, sound, ...
were unloaded although I did try it under X too, just in case. The symptoms are
always the same: machine goes to sleep successfully but can't be woken up except
by a hard reset. To reproduce, simply "echo mem > /sys/power/state".

In this thread on ACPI mailing list:
http://article.gmane.org/gmane.linux.acpi.devel/10113
I was told that it was probably a video card bug but I'm not sure about it
because the machine is completely dead when power button is pressed after it
suspends. The disk LED does light up but Caps Lock LED doesn't. Pinging it
doesn't work neither.

I'd be glad to provide any additional information and/or test any patches
susceptible to fix this problem.

TIA!
Comment 2 Venkatesh Pallipadi 2004-11-04 10:59:16 UTC
Is the problem still there with latest 2.6 kernel?

If yes, can you make sure whether the problem is only with restore of the 
video (try connecting through network or serial after resume).

If it is only the video problem, 
- Please try the options in Documentation/power/video.txt
- Try the workaround in bug #3670
Comment 3 Daniele Depetrini 2004-11-04 11:06:51 UTC
Latest stable kernel (2.6.9) solved the problem for me: my laptop is capable to
resume after S3 now.
Comment 4 Venkatesh Pallipadi 2004-11-04 11:10:09 UTC
Thats good to know :). This bug is closed then.

Vadim: If you still have S3 resume issues with HP nw800, please feel free to 
reopen this bug or open a seperate bug for that one.
Comment 5 Vadim Zeitlin 2004-11-07 14:18:23 UTC
Unfortunately updating to 2.6.9 didn't change anything for me. I'm currently
using the Debian (unstable) version with everything compiled as a module and if
I boot in single user mode and unload everything so that only intel_agp,
agpgart, ext3, jbd and mbcache (the 2 last ones used by ext3) are loaded, I
still have the same behaviour as before, i.e. after "echo mem >
/sys/power/state" the machine seems to enter standby (screen goes black, no more
network, keyboard leds don't work any longer) but the battery and AC led remain
permanently on, while normally the battery one should be off and the AC one
should be blinking slowly (i.e. this is what happens under Windows) and, most
importantly, nothing except hard reset can wake it up. Worse, after hard reset
the machine seems to start booting normally but nothing happens and I have to
reset it the second time to be able to reboot. I have no idea how to explain this...

As before, I'd be glad to provide any additional information, just please let me
know what can I do as so far I remain stuck.

Thanks!
Comment 6 Venkatesh Pallipadi 2004-11-08 14:21:29 UTC
Vadim: I have exactly same problem as you described, on my Compaq presario 
x1000. Few other systems have similar behavior to. I am clubbing all such 
reports under bug #3599, so that it can be addressed better. And closing this 
bug, as the original problem here was slightly different. Please follow up on 
bug #3599 from now on. Thanks.

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