Hi Brian. You might also carefully examine your system after the first cycle. This sort of behaviour is always the result of some driver properly saving and restoring its state (or not saving/restoring at all), and often results in the relevant hardware not working perfectly after the first cycle as well as dying properly on the second attempt at suspending/hibernating.
I'd therefore also suggest that you try building as much as possible as modules, and try to rule things out by suspending a couple of times without the appropriate module loaded. Hopefully you'll get to a point where you can say "if I suspend with module X loaded, it hangs". Start with testing after booting from init S, just in case it's something that's still built in after you've done the modularising-as-much-as-possible. Regards, Nige _______________________________________________ Pm-utils mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/pm-utils
