I can confirm this using Hardy on a Presario c700. I have this behavior with kernels 2.6.24-16, -17, -18, and -19, and with the 2.6.25-2-686 kernel from packages.debian.org. It exists in single-user mode. The first attempt to suspend to ram after a reboot works perfectly; the second one fails on resume, and the log files of the suspend process show nothing after the line "ACPI: PCI interrupt for device 0000:02:01.0 disabled", just before the system should sync disks. When the power button is pressed after the failed suspend, the system lights and fan come on, but there is no hard drive activity; it does not unfreeze even after an hour. It takes a hard reset.
I'm not running any restricted modules at this time (I took ath_pci/ath5k out to make sure it wasn't the issue). My feeling is that since it works once after each reboot, the suspend/resume process isn't cleaning up after itself properly and some setting wedges the process the second time around... I don't know the suspend/resume mechanisms well enough to figure out specifics. Hibernation to disk seems to work with a few tiny quirks (like telling me it failed, after resuming successfully). I'm attaching my copy of /var/log/syslog, which contains a shutdown, restart, successful suspend, successful resume, unsuccessful suspend, and the subsequent reboot, separated by a few blank lines at key points (no deleted lines). lsmod and dmesg files will follow. [EMAIL PROTECTED]:~$ uname -a Linux markanav 2.6.24-17-generic #1 SMP Thu May 1 14:31:33 UTC 2008 i686 GNU/Linux Thanks. ** Attachment added: "syslog_08061001.txt" http://launchpadlibrarian.net/15201448/syslog_08061001.txt -- Can't suspend twice on Hardy kernel version 2.6.24-16 https://bugs.launchpad.net/bugs/217400 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
