Hm, sadly it's not that stable yet: there are at least three ways it
can break currently:
(- processes can't be stopped: that's the known "problem" with swsusp
I've read about, someone seems to have worked out a scheme to find
out the hierarchy of system calls to stop the processes in the right
order to make it more stable. In my case, about every second time I
suspend while xmms is running, it complains about 1 process not being
stopped and that's xmms; I've also seen one of the multiple xmms
threads being T the others not, funny. Note that xmms is always
inactive (it has the audio device closed) in those cases. Anyway,
maybe it's because xmms is threaded, maybe because I've running it
higher prio, or whatever else. It's not tragical, since pmdisk
cancels supsension in this case and one can try it a second time. I
also just kill xmms beforehand now.)
- during suspension, it takes a veeeerryy long time to write
processes to disk (iirc), I see the dots coming up one about every 20
seconds or so. I give up and just reset the machine.
- another time, suspension worked but it took a long time in the
"waiting phase" between writing processes to disk and writing the
rest to disk (as far as I understand that). It took about a minute
just waiting iirc. Then it finished. Resume first seemed to work, but
then it will (just before switching the console to the old state)
just sit there and do nothing. After about 3 minutes I gave up and
did reset the machine.
It would help if someone explained the different phases, when happens
what. Should I try to do that (begin something like a howto)?.
What should I look out for in such failure cases? How can I help the
developers?
(Hm, should I have cross posted this to linuxppc-devel?)
Christian.
