Announce: swsusp 1.1rc9.

Hi everyone.

Software Suspend 1.1rc9 is now being uploaded to swsusp.sf.net.

Changes since rc8:
- This release includes the fixing of two small but significant bugs
which seriously hampered the reliability of the rcs. Lord willing, we're
only a couple of weeks tops away from 1.1 and the beginning of serious
work on updating the port to kernel 2.6.

- The freezer has been seriously reworked. It is now much more reliable,
but not yet perfect. See below for the one remaining known bug in the
core swsusp code.

- Removed the Nosave pageflag. This is now implemented in the same
fashion as swsusp's other page flags - using a dynamically allocated
bitmap.

- New expected_compression functionality. When using compression, you
can now put an expected compression saving into
/proc/swsusp/expected_compression. This number will be used to adjust
calculations for the amount of swap needed. As a result, you no longer
need to have an amount of swap equal to the uncompressed image size.
Note that if your expected compression ratio is not attained, you will
need to adjust (decrease) the value and try again. The value is the
savings you expect to achieve. Thus, if your image is about 100MB and
you expect it to compress to 60MB, you should put 40 (or better, 35) in
the proc entry. An example from the debug info:
- Image compression option compiled in.
- Compression ratio achieved: 40519 pages -> 13221 written = 67%%
compression.
- Expected compression: 60.

- Fixes to configuration and security when debugging is not compiled in.
(Previously, /proc/sys/kernel/swsusp would allow you to set options not
accessible via /proc/swsusp. These settings are now ignored or compiled
out when debugging is disabled).

- Config.in code disables swsusp compilation and shows an appropriate
message when Experimental is deselected or SMP is selected.

- Keep image functionality (Experimental). This compile time option &
new proc entry are for use where the entire filesystem is read-only.
They allow a suspend image to be retained and reused. After the first
suspend, subsequent attempts simply power down the machine. Reloading
the image at boot can be cancelled with the noresume option, or the
swsusp_act parameter can be used to specific that the image should be
discarded (like normal) once loaded.

- Miscellaneous other cleanups and bug fixes.

Known bugs:

- The refrigerator is not yet perfect. It is possible for it to hang
with the message 'Syncing remaining I/O'. If you get this message, you
can press escape twice to attempt to cancel the suspend. This is a
temporary measure while we find a good, permanent solution. Please don't
use press escape twice at other stages in suspending or resuming. You
may cause an oops or corruption of your filesystem.

- Hardware support is still far from complete. Please see swsusp.sf.net
and the mailing list referenced there for help with hardware specific
issues.

Requests:
- If the above refrigerator bug occurs, please check your logs for
messages that might be helpful. In particular, we are after traces of
the processes running at the time. These will be recorded in your
/var/log/messages file. You may want to increase the printk buffer size
in kernel/printk.c to ensure nothing is lost.

- Reports of other bugs we haven't yet seen.

As always, I look forward to your feedback.

Nigel
-- 
Nigel Cunningham
495 St Georges Road South, Hastings 4201, New Zealand

You see, at just the right time, when we were still powerless,
Christ died for the ungodly.
	-- Romans 5:6, NIV.



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
swsusp-devel mailing list
swsusp-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/swsusp-devel