Skip to contentSkip to conversation

2.5.51: sleep broken

DISCUSSION P. Christeas 2 participants 3 messages Dec 10, 2002 – Dec 12, 2002 1 message not in the archive ACPI

lore
Share & tools
lore
#0 lore raw

I 've just tested the 2.5.51 (w. official 20021205 ACPI) I noted that S1 is broken now (had worked long since)

In dmesg I note:
ACPI: Wakeup code way too big, will crash on attempt to suspend

However, /proc/acpi/sleep has all S0 S1 S2 S3 S4 S5 When I 'echo 1 >/proc/acpi/sleep', nothing happens. I'll let you know if I have more details..

-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

A message that is not in the archive (sent off-list or not yet received): [email protected]

#2 lore raw

Hi!

Quoted 2 lines

I 've just tested the 2.5.51 (w. official 20021205 ACPI) I noted that S1 is broken now (had worked long since)

Still the 2.5.50 bug with sleep writes being ignored?

Quoted 2 lines

In dmesg I note:
ACPI: Wakeup code way too big, will crash on attempt to suspend

This is about S3

Signature · 10 lines
				Pavel
Written on sharp zaurus, because my Velo1 broke. If you have Velo you don't need...



-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility 
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
#3 lore raw
In reply to a message not in the archive

I've had a better look at it...

I have written:

Quoted 5 lines

I 've just tested the 2.5.51 (w. official 20021205 ACPI) I noted that S1 is broken now (had worked long since)

In dmesg I note:
ACPI: Wakeup code way too big, will crash on attempt to suspend

Seems irrelevant.

Quoted 3 lines

However, /proc/acpi/sleep has all S0 S1 S2 S3 S4 S5 When I 'echo 1 >/proc/acpi/sleep', nothing happens. I'll let you know if I have more details..

I noticed I had some extra dbg code to indicate what's happening in the procfs level.
Now, it seems that "1" doesn't get written to the acpi/sleep entry. It's a procfs bug.

-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/