Dimitrios Symeonidis, I am currently unable to suspend at all, so I can't really confirm at this point.
Normal suspend just blanks the screen, and the computer never goes into suspend mode (fans are still blowing, the power light stays solid on instead of flashing like it usually does). I've attached the log file which appears to have been created when it suspended. It seems to indicate that suspend was successful, but no amount of key presses brings it back, and pressing the power button doesn't do anything(except turn it off, if you hold it). Pressing alt+SysRq+B reboots the computer, so apparently the kernel is still functional. My bios has an option to choose S1, S3, or both for suspend; I'm not sure which I should choose. I tried uswsusp's s2ram again, and that got further if I did `s2ram -f --acpi_sleep 1` with the bios set to S3, but that would hang on resume with the power light still flashing and the kernel unresponsive. I'll try modifying the file and attempting suspend again, and see if that works. ** Attachment added: "suspend log" http://launchpadlibrarian.net/26488142/pm-suspend.log -- vbetool 100% cpu usage on resume https://bugs.launchpad.net/bugs/130979 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
