Notices

There are tons of user cases where s2ram is useful even though there is electricity somewhere. Even though you're in an environment with electricity that doesn't mean you are able to allowed to use it. Besides, during the time you are plugging in the NIT it isn't a mobile device anymore while being mobile is one of the characteristics of the NIT or any other small mobile device.

Here are some examples:

1) You go on survival tour for a few days and wish to use your NIT as backup GPS in case you get lost, or need to save battery life because you'd like to read your e-mail on day 2 of 3 because you expect an important e-mail.
2) You are travelling by plane or train in non-business class therefore with no electricity at hand.
3) You are in an environment where you don't have the correct loader.
4) You don't like to reload your NIT (or phone, DAP, PDA, laptop, or...) every day for practical reasons.
5) You like to be kind to your lithium ion sweetie.

I have no doubt s2ram is essential for any mobile device, and I'm very happy with this project! I'm about to give 1.11 a go again

Well, as already explained, in normal case when the device is idle (=no buggy software hogging cpu) it goes into same mode as s2ram automatically so you won't gain much with explicit s2ram. Many other devices implementing 'real suspend' won't last even 30 days suspended like N810 does when idle.

Also since the watchdog cannot be stopped you need to wake up once per 63 seconds anyway so real (=uninterrupted) suspend is hard to do.

BTW, maybe instead of pausing kernel for 60 seconds it could be enough to send SIGSTOP/SIGCONT on device lock/unlock to all PIDs not on some whitelist (or at least on some black list - browser and hildon-desktop are good candidates). That could have similar effect without some ill effects of suspending kernel.

version 1.0.11 "eat" 100% CPU after suspend/resume

What you state is only true for real embedded devices. Yes, its more useful on a laptop, but that doesn't mean its useless on a tablet.

If one is running buggy software which drains the battery the user is going to be in disadvantage in several ways: 1) general decrease in performance 2) lower battery life. Suspend-To-RAM has nothing to do with that.

Some of the buggy software eating CPU resour ces is 1) part of maemo 2) may run only when the device is in use which is not 24/7 while putting the device on and off uses more resources.For example, many people won't need to have the NIT on while asleep, therefore it isn't necessary to have applications like applets or Modest using CPU resource. I'm certainly not using my NIT 24/7... besides that, some software isn't buggy; it simply uses quite some resources.

Same here. Is there anything we can do to help track this down? Create crash dumps?

Here it doesn't always eat 100%. The hardware keyboard sometimes stop functioning though (including all other hardware buttons).