swsusp with 2.5.33

Hi there,

lately I observed problems with swsusp. Only if I am suspending from
console right after the boot there are enough pages free....I did some
research on the net and found that the rmap things does not free enough
pages. 

AFAIU when suspending to disk the kernel (respective the vm) is asked to
swap as many pages out as possible and creates an image from the remaining
pages and writes that to disk. While that seems to be at first a great
idea it depends - by design - upon the ability to free more than half of
the ram. Why can one not stop all processes, lock the kernel, and write
all pages to an image in swap space? 

Though I am by no means into kernel internals I would really like to
understand why the above assumption is wrong.

Can someone help me out? 

-Knut



-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone?  Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390