Suspend and hibernation don't work.

inux pornographik-mediacenter 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686 GNU/Linux

Thank you for your bug report. Could you please follow the https://wiki.ubuntu.com/DebuggingKernelSuspend procedure ?

As asked, i followed the procedure.

The dmesg is in attach.

Thank you.

Thanks,

I extracted the needed infos :

[ 1.328276] Magic number: 0:798:917
[ 1.328279] hash matches drivers/base/power/resume.c:46

Is this possibly duplicate of the #33372 and #36937?

Ubuntu 7.10b1, notebook HP Compaq nx6310:

[ 8.338809] Magic number: 11:476:840
[ 8.338903] hash matches device ptyu6

Ubuntu 7.04, notebook HP Compaq nx9105:

[ 16.454513] Magic number: 11:50:573
[ 16.454611] hash matches device ptyb5

On my Dell Inspirion e1505 suspends and hibernates but I am unable to wake the computer using any method.

Following the instructions in the https://wiki.ubuntu.com/DebuggingKernelSuspend procedure gives the following messages and errors:

# sync; echo 1 > /sys/power/pm_trace; /etc/acpi/sleep.sh force
ifdown: interface ath0 not configured
ifdown: interface eth0 not configured
ifdown: interface wifi0 not configured
 * Shutting down ALSA... [ OK ]
Ignoring unknown interface eth0=eth0.
Ignoring unknown interface wifi0=wifi0.
SIOCADDRT: No such process
Failed to bring up ath0.
 * Setting up ALSA... [ OK ]
FATAL: Module acpi_sbs not found.
FATAL: Module acpi_sbs not found.
root@macbook:~# rm: cannot remove `/var/lock/acpisleep': No such file or directory

I was having this problem with a DELL Inspiron 2650 (nvidia chipset). The problem started when I enabled the proprietory nvidia driver, and stopped when I disabled it.

P.S. uname -r gives:
2.6.20-16-386

Hardy Alpha 5
 Manufacturer: ASUSTeK Computer Inc.
 Product Name: A6U
 Version: 1.0

[ 19.194662] Magic number: 0:716:379
[ 19.194665] hash matches /build/buildd/linux-2.6.24/drivers/base/power/main.c:97

When I try to start after suspending, the screen gets covered in a rainbow of thick vertical bars, the hard drive led flashes momentarily, and then the caps lock led flashes on and off forever.

Hi All,

The symptom of this particular bug, failure to Suspend or Hibernate, is specific to the hardware used. So while many of you may have the same symptom they really should be different bugs. It would be helpful if everyone were to test with a Hardy Alpha build, http://www.ubuntu.com/testing/ . However, note that you can only test Suspend using the LiveCD, not Hibernate. If this issue still exists and you have hardware which differs from the original bug reporter, please open a separate bug report for your hardware using "linux" as the package. Additionally, it would be great if you made the titles of your new bug report contain information about your system. I apologize for any inconvenience this might cause but appreciate your cooperation.

pornographik, since you are the original bug reporter, care to comment if this is still an issue with the latest Hardy Alpha release. Also, we'll keep this report open against the actively developed kernel bug against 2.6.20 and 2.6.22 this will be closed. Thanks.

This is still a problem with the latest alpha release. If there's a way to get the version info I can post that. Otherwise, it's from kubuntu-8.04-rc-alternate-amd64.iso

The problem is still present in the release candidate, kubuntu-8.04-rc-alternate-amd64.iso

The kernel info is Linux 2.6.24-16-generic #1 SMP x86_64

Hibernation seems to not work at all, the machine stays on, along with the screen's light, and then after a few seconds, the fan starts revving up till it hits full speed, CPU seems to get *really* hot. The screen is blank, though, and the machine does not seem to respond to any keyboard or mouse activity.

Hibernate causes the CPU to run full speed once the lid is closed. It does not appear to slow down once the lid is opened, nor does it come back out of hibernation. I accidentally left a macbookpro in this state for about 30 minutes and the unit was painfully hot to the touch and started to smell burned. This is easily a hazard to the machine and quite likely a fire hazard.

Hi Lars,

Can you attach the output of 'sudo lspci -vvnn' . Also, care to confirm this is still an issue with the latest Alpha for the upcoming Intrepid Ibex 8.10. You should be able to test Suspend (not Hibernate) via a LiveCD - http://www.ubuntu.com/testing . Please let us know your results. Thanks.

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.

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

*This is an automated response*

This bug report is being closed because we received no response to the previous request for information. Please reopen this if it is still an issue in the actively developed pre-release of Jaunty Jackalope 9.04 - http://cdimage.ubuntu.com/releases/jaunty . To reopen the bug report simply change the Status of the "linux" task back to "New".