Suspend to ram erratic latest gutsy 09/17/2007

[Matthew Tighe]

Binary package hint: gnome-power-manager

Suspend is very flaky under latest gutsy release. Previous release reset X, but latest updates have made suspend extremely erratic.

uname -a
Linux laptop-laptop 2.6.22-11-generic #1 SMP Fri Sep 7 05:07:05 GMT 2007 i686 GNU/Linux

[Matthew Tighe (tighem)]

lscpi -vvnn output

[Matthew Tighe (tighem)]

This is still a problem as of 10/08/2007. Actually, it no longer suspends or hibernates. It appears to do it, but then automatically resumes.

[Matthew Tighe (tighem)]

Found the following script in the forumes (slightly modified by me). This gets suspend working on a D820 under gutsy:

#!/bin/sh

# discover video card's ID
ID=`lspci | grep VGA | awk '{ print $1 }' | sed -e 's@0000:@@' -e 's@:@/@'`

# securely create a temporary file
TMP_FILE=`mktemp /var/tmp/video_state.XXXXXX`
trap 'rm -f $TMP_FILE' 0 1 15

# switch to virtual terminal 1 to avoid graphics
# corruption in X
chvt 1

# write all unwritten data (just in case)
sync

# dump current data from the video card to the
# temporary file
cat /proc/bus/pci/$ID > $TMP_FILE

# suspend
echo -n mem > /sys/power/state

# restore video card data from the temporary file
# on resume
cat $TMP_FILE > /proc/bus/pci/$ID

# switch back to virtual terminal 7 (running X)
chvt 9

# remove temporary file
rm -f $TMP_FILE

[Matthew Tighe (tighem)]

replacing this line:

echo -n mem > /sys/power/state

with this:

echo -n disk > /sys/power/state

in the hibernate script fixes hibernation, too.

[Matthew Tighe (tighem)]

I may have spoken too soon. This appears to only work when dual-monitors are attached. Single monitor I have to change to terminal screen 7.

Argh.

[Matthew Tighe (tighem)]

Suspend is not working again, tried the original hal script and that does not work. The terminal simply locks when suspend is checked.

[Matthew Tighe (tighem)]

Ok, found the solution in the forums. Sync to Vblank must be off in compiz. So suspend is working again with above script. Hibernate seems to be working with standard hal script.

[Matthew Tighe (tighem)]

Oh yes, I've also made the changes recommended here to my xorg.conf and acpi-support files:

http://koon.fr/wiki/suspend_to_ram_on_the_dell_d820_proprietary_nvidia_drivers_under_ubuntu_gutsy

/etc/default/acpi-support:

SAVE_VBE_STATE=false #ex-true
POST_VIDEO=false #ex-true
USE_DPMS=false #ex-true
LOCK_SCREEN=false #ex-true

/etc/X11/xorg.conf

Section "Device"
        Identifier "nVidia Corporation G72M [GeForce Go 7400]"
        Driver "nvidia"
        Busid "PCI:1:0:0"
        Option "UseEDIDDpi" "False"
        Option "AddARGBVisuals" "True"
        Option "AddARGBGLXVisuals" "True"
        Option "NoLogo" "True"
        Option "NvAGP" "1"
EndSection

[Matthew Tighe (tighem)]

Suspend seems to have two issues on the Latitude D820, Nvidia drivers and Compiz running.

The workaround is as follows:

1) sudo gedit /etc/X11/xorg.conf and make sure the following lines are there or match:

Section "Device"
        Identifier "nVidia Corporation G72M [GeForce Go 7400]"
        Driver "nvidia"
        Busid "PCI:1:0:0"
        Option "UseEDIDDpi" "False"
        Option "AddARGBVisuals" "True"
        Option "AddARGBGLXVisuals" "True"
        Option "NoLogo" "True"
        Option "NvAGP" "1"
EndSection

2) sudo gedit /etc/default/acpi-support and make sure the following are changed:

SAVE_VBE_STATE=false #ex-true
POST_VIDEO=false #ex-true
USE_DPMS=false #ex-true
LOCK_SCREEN=false #ex-true

3) gedit /etc/acpi/suspend.d/03-kill-compiz.sh

killall compiz.real

4) chmod 755 /etc/acpi/suspend.d/03-kill-compiz.sh

5) gedit /etc/acpit/resume.d/99-restore-compiz.sh

su - <your-user-name> -c "compiz --replace gconf"

6) chmod 755 /etc/acpi/resume.d/99-restore-compiz.sh

And that should do it. Of course, your could just disable desktop affects, but that wouldn't be any fun.

[Nanley Chery (nanoman)]

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 didn't include enough information.

Please include the information requested at [WWW] https://wiki.ubuntu.com/DebuggingACPI as separate attachments.

[Leann Ogasawara (leannogasawara)]

Hi Mathew,

I'm curious if you'd be willing to test the latest Hardy Alpha release for us. 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. 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.

[Matthew Tighe (tighem)]

I've been running Hardy since A3. Still no dice. Pretty sure it's the Nvidia driver. I haven't tried the latest (169.12) driver yet, though.

[Leann Ogasawara (leannogasawara)]

Hi Mathew,

Care to attach your dmesg output after an attempted suspend/resume cycle as outlined here: https://wiki.ubuntu.com/DebuggingKernelSuspend . We'll keep this report open agains the actively developed kernel but against 2.6.22 this will be closed. Thanks.

[Matthew Tighe (tighem)]

Well guys, lo and behold suspend is working for me again under Hardy Beta (-16 kernel). I sometimes get the whitescreen on resume, but I can still type my password and get in. I believe the whitescreen is a known nvidia bug.

[Daniel T Chen (crimsun)]

Needs quirks.

[Martin Pitt (pitti)]

If you still have the problem on current intrepid or jaunty, please run through http://people.freedesktop.org/~hughsient/quirk/quirk-suspend-debug.html to find out which quirks you need for your machine. Please also submit the output of "lshal" and which X.org driver you are using. There isn't much we can do if you use the proprietary nvidia driver, I'm afraid.

[Martin Pitt (pitti)]

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!