Kernel Summit 2006: Software suspend
Posted Jul 18, 2006 11:37 UTC (Tue) by bojan
In reply to: Kernel Summit 2006: Software suspend
Parent article: Kernel Summit 2006: Software suspend
> One thing that should be added is that part of the reason that swsup2 works well, at least as suspected by some KS attendees, is that it has a huge list of modules to unload before suspend, so that any driver bugs are hidden.
That certainly isn't true any more. It is true that Suspend2 used to carry some driver fixes a while back, which are now merged into mainline, AFAIK. Suspend2 and swsusp use more or less the same machinery to do things. So, as both Pavel and Nigel point out, if one solution fails, the other one is likely to fail too.
What makes Suspend2 better these days is what I mentioned in my first post:
- requires little setup
- looks pretty
- is very fast to suspend and resume
- leaves the machine in responsive state
- can suspend to swap partitions, swap and regular files or combo thereof
BTW, all of these features (minus the "little setup") will eventually pop up in uswsusp. So, it's not like the are useless.
Driver issues are a completely different problem - a shared problem between all suspend solutions. Blacklisting modules is a necessity until the drivers get fixed. Otherwise, many machines would not be able to suspend or resume.
to post comments)