resuming from suspend-to-ram doesn't work sometimes

[ubuntu_demon]

Resuming from suspend-to-ram doesn't work sometimes. So I can't rely on suspend-to-ram.
hibernate seems to work always but I'm not sure yet (need to test more).

I'm running Gutsy fully updated and installed from Tribe 3.

#uname -a
Linux T-2500 2.6.22-8-generic #1 SMP Thu Jul 12 15:59:45 GMT 2007 i686 GNU/Linux

#cd /var/lib/acpi-support/ ; grep . -r *-*
bios-version:1.01
system-manufacturer:American Megatrends Inc
system-product-name:M31EI Series

some installed kernel packages (dpkg -l) :
ii linux-generic 2.6.22.8.8 Complete Generic Linux kernel
ii linux-headers-2.6.22-8 2.6.22-8.18 Header files related to Linux kernel version
ii linux-headers-2.6.22-8-generic 2.6.22-8.18 Linux kernel headers for version 2.6.22 on x
ii linux-headers-generic 2.6.22.8.8 Generic Linux kernel headers
ii linux-image-2.6.22-8-generic 2.6.22-8.18 Linux kernel image for version 2.6.22 on x86
ii linux-image-generic 2.6.22.8.8 Generic Linux kernel image
ii linux-restricted-modules-2.6.22-8-generic 2.6.22.2-8.4 Non-free Linux 2.6.22 modules on x86/x86_64
ii linux-restricted-modules-common 2.6.22.2-8.4 Non-free Linux 2.6.22 modules helper script
ii linux-restricted-modules-generic 2.6.22.8.8 Restricted Linux modules for generic kernels
ii linux-ubuntu-modules-2.6.22-8-generic 2.6.22-8.20 Ubuntu supplied Linux modules for version 2.
ii powertop 1.7~svn-r227-1 linux tool to find out what is using power o

my laptop (the page is a bit outdated) : https://wiki.ubuntu.com/LaptopTestingTeam/AhtecStyleX30Duo

I'm aware of https://wiki.ubuntu.com/DebuggingKernelSuspend
I haven't been able to pinpoint any module using this guide.

"hash matches" I found :

[ 19.719256] Magic number: 15:40:276
[ 19.719271] hash matches device ttyy4
[ 19.719460] hash matches device tty13

[ 11.187655] Magic number: 0:35:917
[ 11.187658] hash matches /build/buildd/linux-source-2.6.22-2.6.22/drivers/base/power/resume.c:57

The system clock changed one time. I didn't find any "hash matches" that time.

[ubuntu_demon (ubuntu-demon)]

I'm using xserver-xorg-video-intel for my GMA 945/950

[ubuntu_demon (ubuntu-demon)]

On the first boot after a failed resume from suspend-to-ram :

[ 11.378811] Magic number: 15:599:29
[ 11.378817] hash matches device ttydc

also attaching dmesg, syslog and kern.log.0 from this session.

[ubuntu_demon (ubuntu-demon)]

Any other information needed ?

[ubuntu_demon (ubuntu-demon)]

Sometimes resuming from suspend-to-ram works. Other times it doesn't work. So I can't rely on suspend-to-ram.

When resuming from suspend-to-ram doesn't work :
* power LED flashes slowly indicating the laptop is sleeping
* I press my power button to try to resume from suspend-to-ram
* power LED stays on and disk activity LED comes on briefly indicating resume has begun
* Nothing happens. My screen remains black (without backlight),
* external monitor doesn't show anything either. laptop unreachable from network. resume has completely failed.

[ubuntu_demon (ubuntu-demon)]

my older Edgy hibernate/suspend bug report (probably not relevant) : https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.17/+bug/68328

[Oleksij Rempel (olerem)]

try to disable "Execution Disable Bit" or "CPU Security option" in your BIOS.

[ubuntu_demon (ubuntu-demon)]

Thanks for your suggestion. My BIOS doesn't have such an option. Is there some way to find out whether the BIOS has set such an option (by default without giving me the choice) ?

[Oleksij Rempel (olerem)]

I have ASUS P5LD2-VM with Pheonix BIOS. On such system it will be:
Advanced > CPU Configuration > Execute Disable Funktion ( should be set
to disable )

[Oleksij Rempel (olerem)]

just cone other suggestion ,

please try this
cat /proc/timer_list | grep "Clock Event Device"

if you have "Clock Event Device: hpet", try add to your boot option hpet=disable
it can fix your problem.

[ubuntu_demon (ubuntu-demon)]

Thanks for the suggestion but HPET is not enabled.

[ubuntu_demon (ubuntu-demon)]

fishor :

Do you happen to know the command for writing away any data to the disk that still has to be written away ? I generally don't test suspend often because I'm afraid that failing to resume and having to do a hard shutdown might mess up my filesystem.

[Oleksij Rempel (olerem)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

ubuntu_demon schrieb:
> fishor :
>
> Do you happen to know the command for writing away any data to the disk
> that still has to be written away ?

sync

this two post are the best place to begin searching your problem.
https://wiki.ubuntu.com/UnderstandingSuspend
https://wiki.ubuntu.com/DebuggingKernelSuspend

try to boot with:
clocksource=tsc

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHQ1EVVVCoNUmKuAcRAiFhAKDVAKFICiLzor6i60uXJ+mgvUQSkQCfXBX4
CkaowsDxFmMJniRnQ4Ynj84=
=qCb8
-----END PGP SIGNATURE-----

[ubuntu_demon (ubuntu-demon)]

to fishor :

Thanks for your help. I'll report on the progress.

A bit offtopic :
This might make debugging suspend problems easier in the future :
http://kerneltrap.org/Linux/Testing_Suspend_and_Hibernation

[Oleksij Rempel (olerem)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

gutsy with new kernel provide dyntics capability wich can be the reason
of hangups too. try boot with nohz=disable
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHRJuYVVCoNUmKuAcRAl8RAJ4q5uJrB7Gy6Pn4HdV2mPcqNKRuqwCeMk3r
pZE/IWmYR2PS53eI7hyFAto=
=JoKy
-----END PGP SIGNATURE-----

[ubuntu_demon (ubuntu-demon)]

Thanks for the suggestion. Disabling dynticks probably won't work because I have always had this problem of suspend-to-ram working sometimes and sometimes not (I have run Edgy,Feisty and now Gutsy on this laptop). Sorry for forgetting to mention this.

The bug I reported against edgy :
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.17/+bug/68328

I have to test hibernate some more to know whether it works reliably or not.

[Oleksij Rempel (olerem)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

@ubuntu_demon
at this point i can't help you any more. it seems to be upstream bug and
should be handled by acpi developers.
It will be more useful if you take git version of vanilla kernel and
reports this bug to bugzilla.kernel.org , so i don't need to be a person
of the middle ;)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHRKVqVVCoNUmKuAcRAv3NAKCevXSjYwCCMvpuLYoltdp2GPA4JgCgs5ZT
8Kbpz6xdRUF6Pjy69JgX9Mo=
=XaCz
-----END PGP SIGNATURE-----

[ubuntu_demon (ubuntu-demon)]

Thanks for all your help. I will try some more and report here. If I can't solve it I will report it to bugzilla.kernel.org using a vanilla kernel

[Leann Ogasawara (leannogasawara)]

Hi ubuntu_demon,

Just curious if this is still an issue with the Hardy Heron Alpha release? The Hardy Heron Alpha series was recently released which contains an updated version of the kernel. You can download and try the new Hardy Heron Alpha release from http://cdimage.ubuntu.com/releases/hardy/ . You should be able to then test the new kernel via the LiveCD. Please note you can only test Suspend-to-ram from the LiveCD, not hibernate (suspend-to-disk). If you can, please verify if this bug still exists or not and report back your results. General information regarding the release can also be found here: http://www.ubuntu.com/testing/ . Thanks.

[ubuntu_demon (ubuntu-demon)]

resuming from suspend-to-ram doesn't work using the Hardy live cd.

[Amit Tendulkar (amit-tendulkar-gmail)]

I am facing the same issue with Hardy Heron on my HP laptop (Compaq nx6120). The suspend works properly, however, resume sometimes don't work. I have run Edgy, Feisty, Gutsy on my same laptop with the same BIOS settings and it is only happening in Hardy (so a regression bug).

Some debugging information,
$ cat /proc/timer_list | grep "Clock Event Device"
Clock Event Device: hpet
Clock Event Device: lapic

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

Let me know whether I need to add a new bug for this.

[Oleksij Rempel (olerem)]

I found on some sustems i have access to, strange suspend bug. It depend on SMP and amount of memory. If you use smp sustem ( dual/qudro core/precessor ) and abot 2 GB of RAM try this kernel option: nosmp and/or mem=1024M

[Leann Ogasawara (leannogasawara)]

Hi ubuntu_demon,

Can you attach your dmesg output after an attempted Suspend/Resume cycle as outlined here: https://wiki.ubuntu.com/DebuggingKernelSuspend . I'm also curious if you were able to test the upstream kernel and if this was still an issue there and if you happened to report this upstream at bugzilla.kernel.org? 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.

[Leann Ogasawara (leannogasawara)]

*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".