S3 suspend fails once in a while (Thinkpad T60, Ubuntu 6.06)

[Sanjoy Mahajan]

Binary package hint: linux-image-2.6.15-25-386

Hardware: Thinkpad T60, SATA hard drive, AHCI mode, Intel wireless, Intel graphics (so no binary-only modules).

Software: Ubuntu 6.06

Suspend to RAM (S3) fails maybe once every 10 or 20 cycles, with the same failure mode during the suspend: The screen blanks, and it looks like it's asleep with the half-moon LED light on, but the battery LED light doesn't turn off (even with the AC unplugged) and the battery area stays very warm. The only fix is to power down with the power switch and reboot (to keep from losing files, I have the suspend script do a 'sync' before suspending).

There's nothing in the logs, sadly, and the machine has no serial port, so I'm not sure what to do next to debug it.

[Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount)]

Thank you for your bug report. Do you still have this issue with the latest release of Ubuntu ?

[Sanjoy Mahajan (sanjoy)]

> Do you still have this issue with the latest release of Ubuntu ?

I haven't seen that particular hang (of the warm battery) with the
most recent one or two kernel packages. Right now I am using the
linux-image-2.6.20-16-generic package on feisty.

Once in a while, with previous kernels, the system would fail to
suspend and the half-moon LED would keep flashing. But that's rare
(maybe 1% of suspends).

More common, perhaps 5%, is that it won't wake from S3. I haven't
seen any S3 problems with this latest package, perhaps because I've
been running it for only a couple days.

But the failure to wake happened two days ago with the previous kernel
package, which I guess is linux-image-2.6.20-15-generic. I had to
hold down the power switch until it shut down hard, then rebooted. I
rebooted into the new kernel package (-16), which had been installed
via 'apt-get upgrade', and I've been running this one since then.

-Sanjoy

[Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount)]

Ok please do the following :

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 "lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.

And the next time it fails to resume/hibernate/suspend follow this : https://wiki.ubuntu.com/DebuggingKernelSuspend

[Sanjoy Mahajan (sanjoy)]

> Please include the output of the command "uname -a" in your next response.

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

> https://wiki.ubuntu.com/DebuggingKernelSuspend

If I enable the PM_TRACE feature, does that mean the RTC will be
messed up after every resume (even the ones that work, which is most
of them)?

[Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount)]

I have no idea.

[Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount)]

But if you disable it after proceeding the debugging procedure, it won't hurt anything.

[Sanjoy Mahajan (sanjoy)]

I've just attached the lspci and dmesg outputs. Here again is uname:

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

This kernel just failed to resume for the first time today. I hadn't
yet enabled the pm_trace, so I enabled it. By suspending and resuming
about 12 times, the failure happened again while pm_trace was active.

The symptom of this failure is that the laptop suspends with the half
moon on (and, correctly, the battery light is off). But it will not
wake up when I open the lid or press Fn (either way usually works) or
the power switch.

The disk light doesn't even flicker. So I don't know whether the
resume path is even activated, and whether the pm_trace info is useful
and from this cycle. But here it is:

magic 0:798:560
1st hash line in the dmesg : resume.c:46
2nd (and final) hash line : device ptya6

[Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount)]

Ok thank you.

[Leann Ogasawara (leannogasawara)]

The Hardy Heron Alpha series is currently under development and contains an updated version of the kernel. It would be helpful if you could test the latest Hardy Alpha release: http://www.ubuntu.com/testing . You should be able to then test the new kernel via the LiveCD. Please note you can only test Suspend using the LiveCD, not Hibernate. If you can, please verify if this bug still exists or not and report back your results. We'll keep this report open against the actively developed kernel bug against 2.6.20 this will be closed. Thanks.

[Leann Ogasawara (leannogasawara)]

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.

[Jean-Baptiste Lallement (jibel)]

Unfortunately this bug report is being closed because we received no response to the last inquiry for information. However, the Intrepid Ibex 8.10 Beta release was most recently announced - http://www.ubuntu.com/testing/intrepid/beta . If you are able to confirm this is still an issue with this most recent release please feel free to reopen this report. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New".

Thanks,

[Launchpad Janitor (janitor)]

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.