An additional detail is that apparently: echo 0 > /sys/power/image_size
Makes things work... I haven't tested enough to confirm though, neither I would know what exahustive kind of test would be required, but from couple of trials, it seems to work. Thanks to Ben Livengood who e-mailed me to try this... I still don't understand why the issue given that /sys/power/image_size controls the image size to be restored (best effort to try to keep it as small as indicated, though if not possible it'll be bigger). By default it's set to 500 MB... What is not clear to me if this setting helps as it seems, is why if the size is limited to 500 MB or a bit more, that would represent a problem given the swap space available? Now if the logic to apply is different, like as the RAM is 512 MB, perhaps it doesn't fit into 500 MB limit, which might be the case, but the documentation indicates it's best effort, meaning it can get bigger if it's not possible to make it fit, and even if a bit bigger, then there's plenty of swap in comparison. Any ways, with those questions at hand, then even if 500 MB is the default value for linux, why not making it 0 the default for debian? As I see it 0 doesn't hurt, and it's the more secure value, since it will always tend to minimize the image sizze to be restored, which in turns might also accelerate resume time... Thanks, -- Javier. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
