Comment 3 for bug 182156

I found out that I had S3 Suspend to RAM disabled in the BIOS, so it was the S1 Standby state that I was having problems with.
Also, I could not find the pm_trace file mentioned in the wiki article, though I am using the latest kernel for Gutsy Gibbon.

I enabled S3 in my BIOS and tested that too. I had a slightly different set of problems waking up from that.
When it awoke I was given the virtual console with kernel messages rather than my desktop. I could manually switch to the virtual console X was running on, but I got only a blank white screen and a responsive mouse pointer. I could kill X with Ctrl+Alt+Backspace, so it was probably a bug caused by Compiz. But then I found my onboard network controllers were not enabled (no connectivity, not even listed in the Network configuration dialog in GNOME) until I reboot my computer, and my sound might not have been enabled either.
Should I file a separate bug for that, since it's waking from a different power state?

Also, my computer will wake fine from both S1 and S3 in Windows, so it shouldn't be a motherboard or BIOS problem.