Suspend-to-disk (hibernate) and suspend-to-ram do not work anymore
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
linux-source-2.6.20 (Ubuntu) |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
I experience problems with suspend-to-disk (hibernate) and suspend-to-ram. I use an IBM Thinkpad T41p. Originally I had installed Kubuntu 6.10 where both features worked fine. After upgrading to Kubuntu 7.04 (Feisty Fawn) I am not able to suspend or hibernate, I can only shutdown regular.
$ uname -a
Linux hugomobil 2.6.20-16-generic #2 SMP Wed May 23 01:46:23 UTC 2007 i686 GNU/Linux
I have installed all upgrades as of today, May 29th.
Example with suspend-to-disk, whatever I use (KDE icons or /etc/acpi/
The screens is getting screwed up (like a TV during a biiiig storm), I can only see black with some colored whirled stripes. Mouse and keyboard are not working anymore. The LED lights of SHIFT-LOCK (CAPS-LOCK?) and this "half-moon" are blinking. There is no activity on the hard-disk. This doesn't change and the system seems to be frozen, so I have to do a hard switch off of my laptop.
After restarting the laptop KDE seems to load the last session where I made a regular shutdown (which still works fine), but not of the session I had as I tried to suspend.
With suspend-to-ram is the same problem.
Both suspend-features worked great in Kubuntu 6.10 (including loading the image from disk/ram).
Changed in linux-source-2.6.20: | |
assignee: | brian-murray → ubuntu-kernel-team |
importance: | Undecided → Medium |
status: | Needs Info → Confirmed |
Thanks for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description doesn't yet have enough information. /wiki.ubuntu. com/KernelTeamB ugPolicies . Thanks in advance!
Please include as attachments the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command 'uname -a' in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command 'dmesg > dmesg.log' and attach the resulting file 'dmesg.log' to this bug report.
3. Please run the command 'sudo lspci -vvnn > lspci-vvnn.log' and attach the resulting file 'lspci-vvnn.log' to this bug report.
For your reference, the full description of procedures for kernel-related bug reports is available at https:/