Sleep and Hibernate issues in Gutsy on Thinkpad x41

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.

1. Please run the command "dmesg > dmesg.log" after a fresh boot and attach the resulting file "dmesg.log" to this bug report.
2. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.
3. Please try to hibernate/suspend and then restart the system and attach /var/log/kern.log.0.

For your reference, the full description of procedures for kernel-related bug reports is available at [WWW] http://wiki.ubuntu.com/KernelTeamBugPolicies. Thanks in advance!

Here are the requested files

launchpad is refusing to let me upload any more files it keeps telling me "Cannot upload empty file.". The kern.log.0 is NOT empty it is 916KB big! How can I get this file to you?

You can maybe retry tomorrow, I'm only a bug triager so I don't need that file eprsonally, it's for the devs.

here it is

Thank you, I'm assigning this to the kernel team.

I'm getting (ostensibly) the exact same bug on my R61 running up to date Gutsy.

Should I upload the files detailed above too?

Yep, I think it would be great.

Thank you.

The only other thing that I think I have to add to this is that when I resume from suspend or try and hibernate my suspend/hibernate activity light (which looks like a crescent moon) starts flashing and doesn't stop until I restart.

I have filed a separate bug here which may or may not turn out to be duplicate:

https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/136603

I am also having a similiar problem with Gutsy running the latest updated on a Thinkpad T60. The problem here is when I suspend the screen goes blank. The hard drive light flicks for a few seconds. Then the caps lock and num lock flash. Then it sits at the flashing cresent moon. Never goes past that. In feisty it worked great and at this point I would get the beep and the moon would go solid. I've attached the same files as request above in case it helps.

I have a Thinkpad T60 as well and I get the same behavior as phlegm above.

I reported the T60p bug on a other bug report ( #147379 ) it's very similar but because is not exactly the same model and effect I open a new one.... it's a duplicate?

Just as an update, I am still having the same issues with the beta release! :(

Also still having the problem with the latest beta.

Hello,

I'm having the same problem on my Gutsy Athlon 64 machine. When it goes to sleep from inactivity, the screen won't come back. The power light remains steady and I can open and close the CD /DVD drive and the optical mouse remains lit, but I cannot get the screen back. I am attaching copies of the log files. I did not have this problem with Feisty. I have had a really difficult time getting the NVIDIA drivers to function correctly (e-GeForce 7300 GT). Also, I am relatively new to Ubuntu / Linux.

Thanks!

Dan Murano

Sorry. only one of the files seems to have attached in the earlier message. Also, this is a Desktop machine.
Here is the other log file.

I get the same problem described by DanM for "sleep", and the same problem described in the original post for hibernation (screen flicks on an off). Hibernate worked fine in feisty. I'm running a realtime kernel, but I was in feisty as well, and didn't have this problem.

dell d410, kubuntu gutsy.
Linux naught-laptop 2.6.22-14-rt #1 SMP PREEMPT RT Wed Oct 10 08:24:17 GMT 2007 i686 GNU/Linux

will restart and post a dmesg log

Any further info on this bug? seems important, but still isn't working in gutsy final

I've noticed that I can hibernate fine with "sudo hibernate", but not with the logout>hibernate button. Anyone know how I can find out why? I've looked at dmesg and Xorg.0.log, and couldn't find anything relevant when I tried..

The name should be changed, since this affects my dell d410 too (problem exactly as described, in kubuntu 7.10).

I don't know is a configuration problem, or if something's compiled incorrectly, but I just dpkg-reconfigured:
xserver-xorg-video-intel, 915resolution, acpi, acpid, acpidump, acpi-support, acpitool and suspend2-userui
and I got no change.

Attached is the "tail -f /var/log/syslog" from an idle point, through attempted hibernate, and back to an idle state.

below is the "tail -f /var/log/Xorg.0.log" for the same period:

(II) intel(0): Output VGA is connected to pipe none
(II) intel(0): Output LVDS is connected to pipe B
(II) intel(0): Output TMDS-1 is connected to pipe none
(II) intel(0): Output TV is connected to pipe none
(II) intel(0): [drm] dma control initialized, using IRQ 16
Synaptics DeviceOn called
(--) Synaptics Touchpad auto-dev sets device to /dev/input/event3
(**) Option "Device" "/dev/input/event3"
(--) Synaptics Touchpad touchpad found
(II) Configured Mouse: ps2EnableDataReporting: succeeded
Synaptics DeviceOff called
(II) AIGLX: Suspending AIGLX clients for VT switch
(II) intel(0): xf86UnbindGARTMemory: unbind key 0
(II) intel(0): xf86UnbindGARTMemory: unbind key 1
(II) intel(0): xf86UnbindGARTMemory: unbind key 2
(II) intel(0): xf86UnbindGARTMemory: unbind key 3
(II) intel(0): xf86UnbindGARTMemory: unbind key 4
(II) Open ACPI successful (/var/run/acpid.socket)
(II) AIGLX: Resuming AIGLX clients after VT switch
(II) intel(0): xf86BindGARTMemory: bind key 0 at 0x007bf000 (pgoffset 1983)
(II) intel(0): xf86BindGARTMemory: bind key 1 at 0x01838000 (pgoffset 6200)
(II) intel(0): xf86BindGARTMemory: bind key 2 at 0x01c00000 (pgoffset 7168)
(II) intel(0): xf86BindGARTMemory: bind key 3 at 0x02000000 (pgoffset 8192)
(II) intel(0): xf86BindGARTMemory: bind key 4 at 0x04400000 (pgoffset 17408)
(II) intel(0): Output configuration:
(II) intel(0): Pipe A is off
(II) intel(0): Display plane A is now disabled and connected to pipe A.
(II) intel(0): Pipe B is on
(II) intel(0): Display plane B is now enabled and connected to pipe B.
(II) intel(0): Output VGA is connected to pipe none
(II) intel(0): Output LVDS is connected to pipe B
(II) intel(0): Output TMDS-1 is connected to pipe none
(II) intel(0): Output TV is connected to pipe none
(II) intel(0): [drm] dma control initialized, using IRQ 16
Synaptics DeviceOn called
(--) Synaptics Touchpad auto-dev sets device to /dev/input/event3
(**) Option "Device" "/dev/input/event3"
(--) Synaptics Touchpad touchpad found
(II) Configured Mouse: ps2EnableDataReporting: succeeded

also dpkg-reconfigured linux-image-2.6.22.14-generic, linux-restricted-modules-2.6.22-14-generic, and linux-ubuntu-modules-2.6.22-14-generic, as well as hibernate. No change.

have a feeling that this may actually be three bugs:
 - Scott Hilleard's one, which a number of other people, including myself, are experiencing (Intel)
 - Tom Vetterlein's one, which Plegm is also experiencing (intel)
 - DanM's one, which is on a different video card (nvidia)

Is the video card relevant? I was using the i810 driver in fiesty, and it was working, I'm now using the intel driver, and it doesn't work, but neither does the gutsy i810 driver.

I'm seeing a similar problem since the gutsy upgrade that would kind of support the video thesis of naught101.
I have not tried suspend yet but hibernate has been consistent. Appeared to work shutting everything down then failed on resume with the regular "hibernate failed" dialog box and network cards errors out with "no such device"

This is an old HP/Compac nx9000.
The only non-standard addition is ndiswrapper for a wireless card, which since upgrade is unusable anyway.

i've to report another 'no suspend' on t60 with Ati X1400 after feisty upgrade using fglrx...

here's the output from
/etc/acpi/hibernate.sh force
which (I think), is the script called to by kmenu > Log out > hibernate.

lots of errors!

I have a vague feeling that this problem would disappear if I fresh-installed, but my d410 doesn't have a cd drive, so it's a bit of a pain.

i have exactly the same problem here on my x41. i really need supsend to ram. if i only had read this here before updating... now i have to reinstall feisty :\

Olaf,

(and anyone else who has run into this bug)

You probably don't need to reinstall Feisty. Since this is a kernel
issue, if you start Gutsy with the old kernel (2.6.20.16), hibernate and
suspend should work (hibernate does for me; I don't use suspend). I did
a vanilla upgrade, so I'm pretty sure that the old kernel is still
available by default (although if Ubuntu is your only OS, I think it's
configured to skip the grub boot screen so you may need to do some grub
editing to start the old kernel).

On Tue, 2007-11-06 at 18:56 +0000, Olaf Lüke wrote:
> i have exactly the same problem here on my x41. i really need supsend to
> ram. if i only had read this here before updating... now i have to
> reinstall feisty :\
>
> ** Attachment added: "dmesg.log"
> http://launchpadlibrarian.net/10293449/dmesg.log
>

Here is another user of DELL D410 with same problem with Sleep. The Hibernate seems to work though. But some times when the machine comes back from hibernate, the NetworkManager process appears to take 100% CPU and the whole machine slows down.

I just found this thread and didn't know this is a known issue with Gutsy. BTW, for some reason my Ubuntu partition has become unusable since last night. Now GRUB fails with Error 17. So I booted using USB flash drive and ran e2fsck. It displayed a huge list of problems with inodes and HTREE and many other directories. Not sure what can corrupt the partition like this? Installing Ubuntu seems to be the only option now.

Sleep and Hibernate did not work well in Feisty. I had done SOMETHING to make Hibernate work in Feisty.
Since upgrading to Gutsy, neither works no matter who's instructions I follow in attempt to make it work. Sleep never resumes and hibernate hangs with a black screen. Gutsy is always kept up to date on my PC.
This machine DID have an issue with S3 in Windows, however, S1 worked perfectly, and hibernate also worked perfectly in Windows.

Feisty fails to sleep on my other PC as well. Seems to be a Ubuntu issue, not so much a hardware issue.

I have a Dell Latitude D600 with Radeon 9000 IGP and am also having problems. When Gutsy resumes from sleep (successfully), an error message appears saying that sleep was unsuccessful. Then some of the time, at that point, it will immediately hibernate the system without my asking. I have to power the system back on, then it resumes to the same place, and another error appears saying that hibernate failed (which is quite untrue, but I don't want it to suddenly decide to hibernate to begin with after I resume).

I had no issues of this sort with Feisty. I wiped Feisty to install Gutsy and haven't done anything crazy with it.

As a workaround to this (at least on my X41) was using the hibnerate scripts.

Changing the line in /etc/hibernate/hibernate.conf to first try ram.conf, than tell gnome-power-manager to use hibernate and it works. But i hope suspend-to-ram will work using the "normal" acpi soon again!

Thanks Blitz, I'll give that a try on my X41! :)

My laptop Ubuntu 7.10 computer MD97600 shows similar symptoms as that of Scott Hilleard:
Gnome main menu > Quit > Hibernate creates a black screen with a dialog where I could remove password barring. Entering my user password removes the barring and restores the Ubuntu screen without LAN access. A tooltip appears: "Problem with the Suspend mode. The change to Hibernation failed..." In /var/log/syslog I find a line; "gnome-power-manager: (detlef) hibernate failed." In Feisty s2disk worked all right though.
uname -a; Linux MD97600 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux
cat /proc/version_signature; Ubuntu 2.6.22-14.46-generic

the fglrx driver has a similar bug.
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.22/+bug/121653

This is caused by a move from CONFIG_SLAB=y to CONFIG_SLUB=y in kernel 2.6.22+. I have no idea what this means, but am wondering if it has anything to do with this bug. Might the intel driver have similar problems?

I've also thought that my hibernate problem might be caused by having too little swap space - I have about 1GB Swap, and 1.2GB RAM. I realise this shouldn't work in theory, however it always worked fine in feisty in reality. could something have changed in gutsy that would use more swap space on hibernate?

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 which is set to come out around Dec 20. However, here are the instructions to install if you choose to do so, otherwise just wait for Alpha2 to come out:

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!

Having the same problems on a T42, I downloaded the 2.6.24-2 kernel as suggested and I was able to enter suspend mode and to resume. However I had other problems, probably due to not downloading all that is necessary to allow my system to function with this kernel version, such as wireless networking.

Thanks for testing KamleshUbuntu. The Hardy Heron Alpha2 release will be coming out soon which should allow you to test but also provide you better functionality for your system. It would be great if you could test with the LiveCD for this new release and let us know your results. I'll be sure to update this report when Alpha2 is available. Thanks!

Using the 2.6.24-2 kernel, I just tried hibernate from the shut down screen and I believe it was successful. The moon light slowly blinked, and the disk light was active right before the system powered down. To resume, I pressed the power button, and selected the test kernel. It seemed to take a long time resuming, about as long as it would to boot. Also the moon light did not blink while the computer was resuming. When the system resumed, the output from some commands were still on a terminal window, so it appears that it did resume.

KamleshUbuntu, thanks for the update. This sounds promising for you. However, I do want to note that you have a different system than the original bug reporter so I'd still like to hear back from him before we officially close this report. Thanks!

Hi, I have just tested and sleep and hibernate with the 2.6.24-2-generic image and sleep appears to be working fine (yay!). Hibernate however appears to go through all the process of hibernating successfully (which didn't happen before) however when I turn the machine back on it just boots normally and does not resume from the hibernated state.

Further testing seems to show that hibernating is actually corrupting my swap partition as once the system has booted back up after failing to resume from its hibernated state swap is not enabled. Any attempt to manually enable it results on the following message:

# swapon -a
[74.904000] Unable to find swap-space signature
swapon: /dev/sda5: Invalid argument

I am forced to run mkswap on /dev/sda5 to get swap working again. This seems to happen every time I hibernate with the 2.6.24 kernel :(

Hi Scott,

Thanks for the update. It seems things are better (ie suspend works), but definitely not perfect yet. Do you see any interesting error messages in either dmesg or maybe /var/log/kern.log.0 after you come back from Hibernation? If so, please attach. Thanks!

I have had a look through my kern.log and can't see any obvious attempt being made by the kernel to restore its state from the swap partition after a hibernate. Not even an error message relating to it. I can see various mentions of uswusp, which I have installed (although its not used by the ubuntu sleep and hibernation scripts by default). I'll upload my kern.log in case some one finds the information helpful in trying to determine why it doesn't even seem to be attempting to restore its hibernated state after hibernation.

sorry that should have read uswsusp (user space software suspend) in the previous post.

after further experimenting I have found that manually adding "resume=/dev/sda5" to the grub boot options after hibernating allows my machine to successfully resume from a hibernate with the 2.6.24 kernel, which is great. So it seems sleep and hibernate work great on my laptop with the 2.6.24-2-generic kernel. The problem seems to be that the kernel is not automatically detecting it went in to a hibernate state on resume (hence why it then thinks the swap partition is corrupt and won't mount it as it contains a dump of memory from the hibernate). I can temporarily fix this for now by manually adding "resume=/dev/sda5" to grubs /boot/grub/menu.lst file, but it would be nice to get to the bottom of why it can't figure out where to resume from itself. Any suggestions?

I'm confirming that this bug is currently fixed in hardy. Mmmm.... hibernation.

Naught101, thanks for testing and the feedback. I'm glad to hear things are working for you now. Scott, since you are the original bug reporter, care to test the latest Ubuntu kernel release for Hardy Alpha (2.6.24-10) and verify if this is resolved for you as well? Thanks.

I will give it a try asap! :)

Just adding a note we'll keep this open against the actively developed kernel but against 2.6.22 this will be closed. Thanks.

Apologies for not having tested yet... I have been pretty busy and use my laptop for work stuff, so have not had a chance to test latest kernel yet!

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 bug report is being closed because we received no response to the previous inquiry for information. Please reopen if this is still an issue in the current Ubuntu release, Jaunty Jackalope 9.04. To reopen the bug, click on the current status, under the Status column, and change the status back to "New". Thanks.