Sleep cannot resume

This looks like a duplicate of Bug #117234 ...

There is difference between Sleep and Hibernate, isn't it?

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.
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://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks in advance!

$ uname -a
Linux Krum 2.6.20-16-generic #2 SMP Wed May 23 01:46:23 UTC 2007 i686 GNU/Linux

See https://wiki.ubuntu.com/LaptopTestingTeam/PackardBellENBU45

Hibernation works and all of the buttons works.

Hi Dilomo,

Can you comment if this is still an issue for you with the 7.10 Gutsy Gibbon release? You can download and try the new version of Ubuntu from http://www.ubuntu.com/getubuntu/download . Please report back your results. Thanks!

Ys it is still an issue on Ubuntu 7.10. Sleep and hybernate cannot resume with the glx-new drivers and compizF 0.6. I'm stuck with black screen.

Thanks Dilomo. The following wiki might be helpful with debugging:

https://wiki.ubuntu.com/DebuggingKernelSuspend

If you could attach the dmesg output as described in that wiki, it would be helpful. I've also tagged this report as 'hardy-kernel-candidate' to make sure we carry this forward to the upcoming 8.04 Hardy Heron kernel. Thanks!

The Hardy Heron kernel was recently uploaded for testing. We'd really appreciate it if you could try testing with this newer kernel and verify if this issue still exists. Unfortunately, the Hardy Heron Alpha1 LiveCD was released with the older 2.6.22 kernel. You'll have to manually install the newer Hardy Heron kernel in order to test. This should not be the case for Alpha2. However, here are the instructions to install (if you choose to do so):

1) edit the file /etc/apt/sources.list and add the following line:

deb http://archive.ubuntu.com/ubuntu hardy main restricted

2) sudo apt-get update
3) sudo apt-get install linux-image-2.6.24-1-generic
4) reboot and select the new kernel from the grub menu

After you've tested, please feel free to revert back - ie boot into the old kernel, sudo apt-get remove linux-image-2.6.24-1-generic, and remove the line from /etc/apt/sources.list . Please update this report with your results. Thanks in advance!

I have a PackardBell BU45-U-074, BIOS 206, which is virtually identical to Reinar's BU45 above (https://wiki.ubuntu.com/LaptopTestingTeam/PackardBellENBU45).

hardy linux-image-2.6.24-1-generic (2.6.24-1.1) does not work. That is, the same behavior as with the current gutsy 2.6.22-14.46, that the machine will apparently go down to sleep fine (the power light "sleeps"), but appears to freeze on resume. I never tested feisty on this machine.

I also tried the procedure described in https://wiki.ubuntu.com/DebuggingKernelSuspend, but to no avail - I found no obvious culprits. Attached is an example dmesg output from 2.6.22-14.46 after attempting pm_trace.

And from a session using 2.6.24-1.1...

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

Yes it is still not working for me. The Pc is the same only the OS is Ubuntu 8.04.

OK, since we are using a new kernel in Hardy, can you please (again) include the information requested at https://wiki.ubuntu.com/DebuggingACPI as separate attachments.
I am closing this bug against linux-source-2.6.22 (Ubuntu) since it is now filed under the development kernel. I will let the Kernel ACPI team handle linux-source-2.6.20 (Ubuntu) since they are already assigned to it.
The bug is marked as Triaged already for the development kernel, so they should already be able to work on this for you.
Thanks for following up!

I will attach only the half of the things now and the others when I press the sleep button and then restart.

$ uname -a
Linux Krum 2.6.24-21-generic #1 SMP Mon Aug 25 17:32:09 UTC 2008 i686 GNU/Linux

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

The 18 month support period for Feisty Fawn 7.04 has reached it's end of life - http://www.ubuntu.com/news/ubuntu-7.04-end-of-life . As a result we are closing the linux-source-2.6.20 task. I'm also setting the "linux" task to Incomplete until we get feedback regarding testing with Intrepid Ibex 8.10. Thanks.

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!