Suspend to ram occasionally not resuming on HP nc6120 with Ubuntu 8.04

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description does not yet have enough information.

Please include the following additional information, if you have not already done so (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" after a fresh boot 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!

hp1:~$ uname -a
Linux hp1 2.6.24-16-generic #1 SMP Thu Apr 10 13:23:42 UTC 2008 i686 GNU/Linux

I have an HP nc6120 as well and can can confirm this behaviour.

Linux Loki-laptop 2.6.24-16-generic #1 SMP Thu Apr 10 13:23:42 UTC 2008 i686 GNU/Linux

Maybe this one http://bugzilla.kernel.org/show_bug.cgi?id=9839 but upstream said it's solved in .24.stable so Ubuntu's kernel should already be patched ...

Franck & sonofawolf, please can you attach the file /var/log/kern.log just after the problem occurs ?

We also have instructions on debugging this type of problem at https://wiki.ubuntu.com/DebuggingKernelSuspend

Thanks.

I found something similar in /var/log/messages.

Could you please download the latest Alpha CD image of Intrepid and test this particular bug just using the Live CD? You can find the latest image at http://www.ubuntu.com/testing .

Thanks for your help.

I have used the live CD to test Suspend to RAM.
It worked for 2 times.
Then on resume I saw a blank screen again. I assumed seeing the same problem as before and while I was getting my other computer ready to test the network the resume succeeded.
The long resume times happen about every 3rd time.
The Errors I see on the screen are:

ACPI: EC: CPE storm detected, disabling EC GPE
:
ACPI: EC: acpi_ec_wait timeout, stats=0x09, event="b0=1"
ACPI: EC: read timeout, command=130
BUG: soft lockup - CPU#0 stuck for 136s [pm-suspend: 11273]
:
ipw2200: Unable to load ucode: -22
ipw2200: Unable to load firmware: -22
ipw2200: Failed to up device
:

Finally the laptop froze on a later suspend, which did not succeed. The screen was still showing the error messages above but the laptop did not go to sleep within 20 minutes.

The previous test was done with a DVD+RW and the crash might have been related to read errors.
Therefore I repeated the test with a CD-RW and now the laptop does not crash any more, but the original problem still seems to exist.
However, I noticed that the laptop always resumes, but this can take about five minutes. Before, I assumed the laptop had crashed. To test this hypothesis I ran the older 8.04 live CD and confirmed that the laptop always resumes from suspend but sometimes takes more than five minutes.
Below I attach the syslog and messages logs from the 8.10 alpha4 live CD.
Unfortunately I can not reproduce the error with my installed 8.04 system, since it does not suspend at all. There I am running the 2.6.24-18-generic kenerl. Maybe this is the problem.

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.

I have a very similar issue on a Toshiba P100 laptop (PSPA3E): 2 suspends to ram work (no sound at resume, but it has always be an issue on this machine), third does not resume.

So maybe this bug is duplicate with this one?
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/230184

Concerning the slow resume, if you have a manual networks configuration (or inherited from a dist-upgrade instead of clean install) and use wifi, maybe you should have a look at this:
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/236066

It's a pity that the main response we get from this kind of bug is "try next version"... If I only install LTS versions, it's to be able to upgrade only on a 2/3 years rate which is a good new feature attraction/annoying process! These ones, corporate oriented, should also be more stable...

I have done a test with the latest ubuntu boot cd: Intrepid Ibex Alpha 5.
The same problem was found.

This bug report was marked as Triaged a while ago but has not had any updated comments for quite some time. Please let us know if this issue remains in the current Ubuntu release, http://www.ubuntu.com/getubuntu/download . If the issue remains, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

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!

I have reopened the bug again, because you don't have any indication that the bug is fixed.
If you want to close a bug please fix it first. This is the only possible way to close a bug.
Everything else wastes time and looks bad.
Sorry that I can't provide the information you want, but my time is too limited to allow for a testing of every single new release which lacks serious work dedicated to my problem.
If I find time I will test the latest release again, but you will have to wait.
A bug report is valid until proven otherwise.
Please take bug reports more serious in the future!

Ok, here is the good news:
Finally I tested ubuntu-9.10-desktop-i386 and it seems like the problem disappeared.
I suspended and resumed about 20 times and 2x10 times without intermediate shutdown successfully.
Remaining bugs are #511232 and #231562.

A last comment: to avoid this sort of hardware problems in the future I switched to running my Linux system in the virtual machine of VMware. This worked very well for me and I can recommend this solution to work around most hardware problems of Linux.