AMD64 Swsusp on 2.6.9-rc4-mm1
Hey, Im running 2.6.9-rc4-mm1, and when i run either a echo 4 > /proc/acpi/sleep or echo disk > /sys/power/state I get the following messages:
Stopping tasks: =================|
Freeing memory... done (0 pages freed)
PM: Attempting to suspend to disk.
PM: snapshotting memory.
ACPI: PCI interrupt 0000:00:02.7[C] -> GSI 18 (level, low) -> IRQ 18 Restarting tasks... done
It basically just stops everything, then starts it all back up again immediately. Any idea whats going on here? This was done right after booting and just logging in with no X running.
Quoted 14 lines · William Wolf
Hey, Im running 2.6.9-rc4-mm1, and when i run either a echo 4 >
/proc/acpi/sleepor echo disk >/sys/power/stateI get the following messages:Stopping tasks: =================|
Freeing memory... done (0 pages freed)
PM: Attempting to suspend to disk.
PM: snapshotting memory.
ACPI: PCI interrupt 0000:00:02.7[C] -> GSI 18 (level, low) -> IRQ 18 Restarting tasks... done
Quoted 3 lines
It basically just stops everything, then starts it all back up again immediately. Any idea whats going on here? This was done right after booting and just logging in with no X running.
IIRC, on 2.6.9-rc4-mm1 swsusp cannot free memory because of some unfinished VM patches that are in there, so it won't work (Andrew, please correct if I'm wrong).
Greets,
RJW
Signature · 3 lines
- Would you tell me, please, which way I ought to go from here? - That depends a good deal on where you want to get to. -- Lewis Carroll "Alice's Adventures in Wonderland"
Is this supposedly something new in rc4-mm1? I have been having the same problems since around 2.6.8.1, though i havent gone through every single -mm patch, i have tried at least one in every -rcx candidate, and they have all done this same thing.
Quoted 26 lines · Rafael J. Wysocki
Quoted 14 lines · William Wolf
Hey, Im running 2.6.9-rc4-mm1, and when i run either a echo 4 >
/proc/acpi/sleepor echo disk >/sys/power/stateI get the following messages:Stopping tasks: =================|
Freeing memory... done (0 pages freed)
PM: Attempting to suspend to disk.
PM: snapshotting memory.
ACPI: PCI interrupt 0000:00:02.7[C] -> GSI 18 (level, low) -> IRQ 18 Restarting tasks... doneQuoted 3 lines
It basically just stops everything, then starts it all back up again immediately. Any idea whats going on here? This was done right after booting and just logging in with no X running.
IIRC, on 2.6.9-rc4-mm1 swsusp cannot free memory because of some unfinished VM patches that are in there, so it won't work (Andrew, please correct if I'm wrong).
Greets,
RJW
Quoted 4 lines · William Wolf
Is this supposedly something new in rc4-mm1? I have been having the same problems since around 2.6.8.1, though i havent gone through every single -mm patch, i have tried at least one in every -rcx candidate, and they have all done this same thing.
This may be for another reason. I generally test all of the -rc and -mm patches on an AMD64 box and apparently 2.6.9-rc4-mm1 is the first one that has the problem I was talking about. AFAICT, the other kernels may fail in a similar way if memory is stuffed with something (eg after updatedb).
Greets,
RJW
Signature · 3 lines
- Would you tell me, please, which way I ought to go from here? - That depends a good deal on where you want to get to. -- Lewis Carroll "Alice's Adventures in Wonderland"
Quoted 10 lines · Rafael J. Wysocki
Quoted 4 lines · William Wolf
Is this supposedly something new in rc4-mm1? I have been having the same problems since around 2.6.8.1, though i havent gone through every single -mm patch, i have tried at least one in every -rcx candidate, and they have all done this same thing.
This may be for another reason. I generally test all of the -rc and -mm patches on an AMD64 box and apparently 2.6.9-rc4-mm1 is the first one that has the problem I was talking about. AFAICT, the other kernels may fail in a similar way if memory is stuffed with something (eg after updatedb).
Hmmm, ok, well I can boot into other -rcx-mmx kernels and get my output if that would help any. Usually when i test, i try it immediately after booting and logging into a console (no X running), so it would be tough for the memory to be stuffed.