suspend/resume failure during second suspend [non-free: nvidia] and free xorg

[Martin Mai]

I followed https://wiki.ubuntu.com/KernelTeam/SuspendResumeTesting and the test failed.

>>> Did the machine break while going to sleep or waking up?
When I have started my computer and try to suspend it, suspending and resuming works for the first time. If I then try to suspend another time, the computer is not able to suspend. The monitor suspends, but the computer is running as if it was working normally.

>>> Is it reproducible?
This behavior is 100% reproducible for me since Ubuntu 8.10 (before that I wasn't even able to suspend once).

>>> Did it work before?
I think with Ubuntu 7.10 I was able to suspend (but I am not sure how often)

>>> Do you end up with flashing caps-lock or similar?
No, nothing special is happening. It is just making sounds as if running normal, but the monitor is suspended.

I will provide further information after some testing.

ProblemType: KernelOops
Annotation: This occured during a previous suspend and prevented it from resuming properly.
Architecture: amd64
CurrentDmesg:
 [ 32.888018] eth0: no IPv6 routers present
 [ 82.108036] Clocksource tsc unstable (delta = -249872836 ns)
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
InterpreterPath: /usr/bin/python2.6
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 002: ID 045e:0040 Microsoft Corp. Wheel Mouse Optical
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: System manufacturer System Product Name
NonfreeKernelModules: nvidia
Package: linux-image-2.6.28-11-generic 2.6.28-11.38
ProcAttrCurrent: unconfined
ProcCmdLine: root=UUID=52dee6b6-89ab-4480-90f4-bca5553f8e45 ro quiet splash
ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.28-11.38-generic
SourcePackage: linux
Tags: resume suspend
Title: [System manufacturer System Product Name] suspend/resume failure [non-free: nvidia]
UserGroups:

[linuxuser600 (linuxuser600)]

Suspend doesn't work at all for me

[Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount)]

Now I followed https://wiki.ubuntu.com/DebuggingKernelSuspend because https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume gave nothing useful. I think the important lines from "dmesg" are:

>> First suspend and resume (successful)
[ 4.889816] Magic number: 1:835:174
[ 4.889870] acpi device:0a: hash matches

>> Second suspend (suspend fails, have to restart computer)
[ 4.889812] Magic number: 0:81:349
[ 4.889814] hash matches /build/buildd/linux-2.6.28/drivers/base/power/main.c:390

I attached both dmesg outputs.

[Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount)]

I followed http://ubuntuforums.org/showthread.php?t=505890 and added a "set -x" to the file "/etc/acpi/sleep.sh"; then I ran the command "cd /etc/acpi/ ; ./sleep.sh force" and saved the output in a file (one for the first and one for the second suspend).

The first suspend log is longer than the second and covers some error messages, which are not present in the second log because the suspend is not going that far (it doesn't suspend fully).

I attached the two logs and the diff, which covers the lines that are not present in the second log and the mentioned errors (apart from these lines, the logs are equal.

[Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount)]

(Just to mention it)

I deactivated the restricted nvidia driver before running "sleep.sh force", but since it still doesn't work and everything is as before, the driver should not have any impact on the suspend.

[fredichkou (fredichkou)]

The suspend to ram function isn't avalable for me. And when I tried to to the test https://wiki.ubuntu.com/KernelTeam/SuspendResumeTesting It always failed.

[nemtudom (nemtudom74)]

if I execute "sync" before pressing the suspend button it helps for me. (don't know why)

[Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount)]

Hi nemtudom and thank you for your idea, but even though standby is not working for me.

[Jim Lieb (lieb)]

Can you confirm this issue exists with the most recent Karmic Koala 9.10 Beta release? ISO CD images are available at http://cdimage.ubuntu.com/releases/karmic/ . If the issue remains with Karmic it would be great to then also test the latest upstream mainline kernel available. This will allow additional upstream developers to examine this issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Thanks in advance.

[Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount)]

Thanks for your reply. At the moment I have no access to the hardware, but I hope I can test it later with the final release of Karmic. Maybe the hal deprecation for karmic makes it better. Thanks.

[equon (eliot-quon)]

I have this problem with Karmic and the problem is reproducible. First suspend and resume works, second suspend results in services stopping but the computer not entering sleep. The only option is to kill the power.

By Nemtudom's suggestion, I tried executing "sync" before suspend and found that sync works before the first suspend, but hangs before the second suspend.

In addition, my kernel log shows numerous messages saying:
  INFO: task sync:##### blocked for more than 120 seconds
This message appears regardless of whether I manually run sync or not.

Please help!

Thanks

[Steve Farthing (s-farthing)]

Looks like I also have this problem with U 10.04

[Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount)]

As the original reporter, I was able to test this with Ubuntu 10.04 and it still fails to sleep a second time on the given hardware.

[Steve Farthing (s-farthing)]

This bug is now fixed for me with the following kernel! Thank you!

-Version-
Kernel : Linux 2.6.32-24-generic (i686)
Compiled : #40~pre201008060902-Ubuntu SMP Fri Aug 6 09:27:20 UTC 2010
C Library : GNU C Library version 2.11.1 (stable)
Default C Compiler : GNU C Compiler version 4.4.3 (Ubuntu 4.4.3-4ubuntu5)
Distribution : Linux Mint 9 Isadora
-Current Session-
Computer Name : mint-desktop
User Name : user (user)
Home Directory : /home/user
Desktop Environment : GNOME 2.30.2
-Misc-
Uptime : 10 minutes
Load Average : 2.47, 2.13, 1.04

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu development release http://cdimage.ubuntu.com/daily-live/current/ . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]