swsusp is not reliable. Face it. [was Re: [Swsusp-devel] Re: swsusp problems]
From: Pavel Machek
Date: Thu Mar 25 2004 - 17:22:31 EST
> >>Well, not all printks() are errors this hard. And at some points, it
> >>is no longer possible to abort (after pagedir is on disk, its okay to
> >>panic (machine will resume normally after that), but its not okay to
> >>simply return. You could fix signature then return, but it would be hard).
> It is _utterly_ unacceptable to fail during suspend. You might as well take
> a sledge hammer to kill the box!
Okay, so bring me the sledgehammer.
> Suspend is a mechanism to suspend the system transparently and
> _NOT_EVER_ impairing the system. There can be NO_COMPROMISE and
> NO_EXCUSE. I walk out of my office suspending the machine and resuming it
> in front of my client it can't ever fail, or am I an idiot to advocate
> If I would be willing to accept failure I would not spend my time here and
> utilize M$'s incarnation of an architectural idiocy.
You are wrong.
swsusp1 fails your test, swsusp2 fails your test, and pmdisk fails it,
too. If half of memory is used by kmalloc(), there's no sane way to
make suspend-to-disk working. And swsusp does not. Granted, half
of memory kmalloc-ed is unusual situation, but it can theoreticaly
happen. Try mem=8M or something.
So stop spreading nonsense about "NO COMPROMISES" and stop comparing
me to Mickey$oft. Thanks.
> Right, because nobody pays attention. If you step on the brake pedal driving
> your car these brakes better work or you may be well worse of than dead
> ... just in case you ran over a kid...
So don't put swsusp into car-braking system.
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/