kohsuke
November 27th, 2010, 09:29 PM
I have a desktop system (P55-USB3 + Core i7 + Ubuntu 10.10) that fails to suspend/resume from memory. So I'm trying to diagnose the problem.
The first obstacle was easy enough --- when I put the system to sleep to memory, the computer comes back alive right away. A look at /var/log/kern.log revealed that one USB device (usb10) failed to suspend, and from there I was able to pin it down to the USB3 controller in the BIOS. Disabled that and this problem disappeared.
Now, I'm stuck with the second obstacle. The computer successfully goes into the suspend mode, but it hangs during resume. The monitor doesn't get any video signal, and it fails to respond to ping (netconsole doesn't work either.) After a forced reboot (that involves unplugging the power cable), /var/log/kern.log doesn't contain any interesting entries.
All the pm_test modes from freezer to core succeed (I followed http://www.mjmwired.net/kernel/Documentation/power/basic-pm-debugging.txt)
I've also tried pm_trace (https://wiki.ubuntu.com/DebuggingKernelSuspend) but again kern.log nor dmesg contains anything after the suspend. Either the write didn't survive the forced power off, or the resume is failing even before that.
The motherboard doesn't have a serial port nor firewire, so getting kernel logs through them is not a possibility, either.
How do you go about diagnosing any further? Any help would be greatly appreciated.
The first obstacle was easy enough --- when I put the system to sleep to memory, the computer comes back alive right away. A look at /var/log/kern.log revealed that one USB device (usb10) failed to suspend, and from there I was able to pin it down to the USB3 controller in the BIOS. Disabled that and this problem disappeared.
Now, I'm stuck with the second obstacle. The computer successfully goes into the suspend mode, but it hangs during resume. The monitor doesn't get any video signal, and it fails to respond to ping (netconsole doesn't work either.) After a forced reboot (that involves unplugging the power cable), /var/log/kern.log doesn't contain any interesting entries.
All the pm_test modes from freezer to core succeed (I followed http://www.mjmwired.net/kernel/Documentation/power/basic-pm-debugging.txt)
I've also tried pm_trace (https://wiki.ubuntu.com/DebuggingKernelSuspend) but again kern.log nor dmesg contains anything after the suspend. Either the write didn't survive the forced power off, or the resume is failing even before that.
The motherboard doesn't have a serial port nor firewire, so getting kernel logs through them is not a possibility, either.
How do you go about diagnosing any further? Any help would be greatly appreciated.