Suspend to ram broken since 2.6.22-13

I tried using ubuntu (gnome-power-manager) and five suspend in a row went fine ...
I used kubuntu before

I think i am closing this bug, till a can reproduce it with ubuntu - if not i am filing against kubuntu power stuff

I have this same problem with an X61s, but it works about 50% of the time. And with the acpi_sleep=s3_bios kernel parameter I can then see that same yellow INU. Without I only see a black screen (since it does not turn on the backlight). And this is in Ubuntu 7.10 (fresh install) NOT kubuntu.

Bug is hitting me again - i second the 50% and set to "confirmed", because 2 users are hitten ...

I tried compiling the Ubuntu kernel myself (from the package linux-source-2.6.22 in 7.10). I created two versions: one without any changes, and one where I had reverted the two following changes, which apparently came in 2.6.22-13 where it seems that the error started to appear, and both concern suspending:

http://kerneltrap.org/mailarchive/linux-kernel/2007/9/22/272672
http://kerneltrap.org/mailarchive/linux-kernel/2007/9/22/272673

With the first kernel I got the same problem as before (after my third or forth try it hanged), but with the second kernel I have now suspended it and resumed many times (at least 20-30 times) without any problems. It seems that I have managed to narrow down the bug to those two changes. However, I will still keep using this kernel for some time to see if it's really working or just luck :)

Unfortunately I did not yet manage to include Ubuntu's restricted drivers, so wireless and sounds are not working with this kernel. (But since this is the case with both self-compiled kernels and one of them hangs I can be sure that is not this exclusion that causes it to work...)

Should I report this to some kernel bug-forum, or what is the correct procedure?

Hi, I have recompiled the 2.6.22-14-generic sources and reverting the patches you mentioned above, before.
I used dpkg-buildpackage to build the generic flavour.

I successfully use my kernel image und the lum modules from the rep. The update manager wants to install a newer 2.6.22-14-generic version (which is the same installed ?!?), but this way, you would have sound and wireless.

You can get the kernel over here, (i installed lum, headers from the rep before) and overwrote the whole kernel with:
sudo dpkg -i --force-all linux-image-2.6.22-14-generic_2.6.22-14.46_i386.deb

http://www.stud.uni-karlsruhe.de/~unatk/linux-image-2.6.22-14-generic_2.6.22-14.46_i386.deb

Please report back, considering the suspend issue

Yes, I managed to get my modules working as well. Simply by copying them to the correct place, analogous to what's explained here:
http://ubuntuforums.org/showthread.php?t=337799

I haven't tried your kernel, but it should be the same - except for the copying of the modules.

I have now been running this system for almost a week, suspending and resuming many times a day without any problems. So I am now very confident that the problem is with one or both of those patches mentioned above. As I said I tried with exactly the same setup, and a self-compiled kernel, but _without_ reverting the patches and that hung the system after 3-4 suspend-resume tries.

I tried Peter's kernel, but suspend still doesn't work. With the default /boot/grub/menu.1st, no video comes back at all; if I add the acpi_sleep=s3_bios kernel parameter I can then see that same yellow INU as Mats. This is with an X61s, just delivered this past week, BIOS revision 1.06.

I should add my product ID: 7668CTO. Sounds like the specific hardware used in the same Lenovo model can vary by product ID.

Hi Brian,

I will upload a 2.6.23.1 kernel, if I come home later. Till now, i can say: the ubuntu kernel without the two above mentioned patches crashes less, but it did not work perfect - so I compiled a vanilla kernel version, with latest thinkpad-acpi and this one never failed.

But! vanilla 2.6.23.1 kernel includes these 2 patches above, so I think something other in ubuntu kernel is the cause for this problem, but "more often triggered" if these patches are included.

Peter

PS: I think there is a newer bios revision 1.08 ...

Do you need wireless to work? this is the only modul not included in my kernel and compiled afterwards, because not in mainline ...

Was happy too early,

Suspended my laptop > 12 hours and the resume failed - also with a vanilla 2.6.23.1 kernel - so, im totally clueless what to do

...

Ironically, just after reading your messages, resuming from suspend failed for me for the first time since starting to use the changed kernel. But it had worked consistently before that for an entire week. This would perhaps support the theory that the problem is elsewhere, but the removal of those patches causes it to be triggered less. Or then I have just been incredibly lucky up till now.

The only thing that I can think of that differentiates this failed resume-from-suspend from other successful ones is that I had an external USB CD/DVD-drive connected when suspending which I removed before resuming. I have no idea if that is relevant or not.

This bug is really hard to isolate since it seems to occur so randomly...

On Sun, 4 Nov 2007, Peter Frühberger wrote:
> PS: I think there is a newer bios revision 1.08 ...

Indeed there is, updatable as a bootable CD, so I'll pull that down.

> Do you need wireless to work? this is the only modul not included in my
> kernel and compiled afterwards, because not in mainline ...

Wireless worked with the stock 2.6.22-14 kernel that came with the 7.10
install for me, it's an Atheros a/b/g. I do need it to work, yep. Like
others have reported, sound works, but the sound buttons don't control its
volume. I'd love hibernate to work too (same problems as suspend) but
don't need it. Other than these issues it's a dream machine!

  Brian

Yes, i know.

I just wanted to ask you to test my 2.6.23.1 kernel version, but iwl4965 is not in stable mainline till now (only included in 2.6.24-rc1), but since my kernel crashed this morning after resume, i am not very confident ...

So let`s see, what the kernel team can do

I am assigning this bug to the 'ubuntu-kernel-team' per their bug policy. For future reference you can learn more about their bug policy at https://wiki.ubuntu.com/KernelTeamBugPolicies .

I have also had this. It seems to be prevalent on the 32-bit kernel rather than 64-bit. Could there be a substantial difference between the two kernel builds to cause this (i.e. tickless kernel)?

I just upgraded my X61s (7669-7DM) from gutsy to hardy (32-bit). Previously, hibernate worked but suspend did not. Now, suspend works fine, and hibernate fails.

On hardy it reproducibly hangs at "trying to resume from ..."

I'm having problems with suspend using Lenovo Thinkpad X61s. When I try to wake up the computer on battery power, it hangs with blank screen until I plug in the AC, after which it continues as it should.

Same problem X61 [no s]. I guess Im going to hope hardy solves the problem. Maybe Ill give 64bit hardy a spin. I also have iwl4965, and I hate the bloody thing. Long story, anwyas, I havnt tried plugging in an AC when it the screen hangs on resume, has anyone other than Tero had that work for them??

Hardy works fine for me - without suspend to ram problems :-)
Wait for a week and give it a try.

If you did not know: if your usb is dead after resume, this was fixed within a bios upgrade from lenovo.

#Begin off topic:
Only stuff in hardy, that does not work so far: hdaps (workaround using tp_smapi)
WLAN LED: install linux-backport-modules
Brightness levels only 8: thinkpad-acpi also generetes an brightness event (so you have 2 events every keypress) 16 /2 = 8. Workaround easylisy possible, while editing hotkey-setup oder ibm brightness script.
#end off topic

Did not test suspend to disk so far - but this could be the best release ever ;-) - the first time, i could stick with the distribution kernel since ever.

Fresh 8.04 Hardy install: after a fresh boot, suspend/resume works the first time, sometimes even the second time, but then fails to come back the second or third time. System will wake up but screen will be blank. Alt-fn-f1 doesn't wake it up. Pressing lots of combinations of other keys did, not sure which one caused it, but what came back was a black screen with just the mouse pointer, which could be moved around, but like before, unresponsive to any other input. I added

SUSPEND_MODULES="button ehci_hcd"

to /etc/pm/config.d/config as suggested by some reports on launchpad, but that didn't seem to make a difference. Have not yet tried adding acpi_sleep=s3_bios as a kernel parameter yet but am happy to try.

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. 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.

Actually, for me the problem is completely gone in Hardy with 2.6.24 series kernels. Suspend to RAM works 100% reliably.

I concur. This bug seems to be addressed by the hardy kernels (I'm
currently using linux-image-2.6.24-19-generic/2.6.24-19.36 as a reference
point).

--
- Gus

Thanks for the feedback. Based on the previous comments as well as the comment from Peter (the original bug reporter) - https://bugs.edge.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/153545/comments/19 I'm going to mark this "Fix Released" for Hardy. For anyone still experiencing issues, if you could please open a new bug report we can try to narrow this down specifically for you hardware. Thanks.

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.