Ubuntu
linux package

Suspend is not working on Nvidia hardware

Bug #936545 reported by Nicolás Abel Carbone on 2012-02-19

This bug affects 5 people

Affects		Status	Importance	Assigned to	Milestone
	linux (Ubuntu)	Invalid	Medium	Unassigned

Bug Description

I installed Ubuntu 12.04 alpha 2 amd64 from scratch and suspend is broken. It was working fine in Ubuntu 11.04.

When choosing to suspend, the process is started, and the PC, apparently, does suspend for a fraction of a second. Then it resumes immediately. When displaying the desktop after this process, the launcher is corrupted, but this is solved by hovering with the mouse over it.

Also, and maybe related, when the OS is doing the transition between LightDM and the the Unity desktop, instead of showing a black screen, a lot of garbage is shown. Sometimes, some textures of windows opened in the previous sessions are showed.

I also tested Ubuntu 12.04 in another PC, with a notebook with Intel integrated video card and it suspends and restores fine and no garbage is shown between LightDM and the desktop.

I am using a Nvidia GeForce GTX550Ti, in a Nvidia-based motherboard (Nvidia 520 chipset) with a AMD Athlon 64 x2 CPU.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-17-generic 3.2.0-17.26
ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: nicolas 1873 F.... pulseaudio
/dev/snd/controlC0: nicolas 1873 F.... pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Card0.Amixer.info:
Card hw:0 'NVidia'/'HDA NVidia at 0xfbdf8000 irq 20'
   Mixer name : 'Realtek ALC888'
   Components : 'HDA:10ec0888,10ec0888,00100001'
   Controls : 49
   Simple ctrls : 22
Card1.Amixer.info:
Card hw:1 'NVidia_1'/'HDA NVidia at 0xfeb7c000 irq 16'
   Mixer name : 'Nvidia GPU 15 HDMI/DP'
   Components : 'HDA:10de0015,10de0101,00100100'
   Controls : 24
   Simple ctrls : 4
Date: Sun Feb 19 18:33:28 2012
HibernationDevice: RESUME=UUID=6ba7a62d-8120-4f3f-9f02-922fb2829603
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120211)
IwConfig:
lo no wireless extensions.

eth0 no wireless extensions.
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
LANGUAGE=es_AR:es:en
PATH=(custom, no user)
LANG=es_AR.utf8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-17-generic root=UUID=c00ec9f3-2df1-47a1-bcea-979cd2de71e1 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.2.0-17-generic N/A
linux-backports-modules-3.2.0-17-generic N/A
linux-firmware 1.69
RfKill:

SourcePackage: linux
UpgradeStatus: Upgraded to precise on 2012-02-16 (3 days ago)
dmi.bios.date: 05/07/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.40
dmi.board.name: ALiveNF5-eSATA2+
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd05/07/2007:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvn:rnALiveNF5-eSATA2+:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

Tags:

Revision history for this message

Nicolás Abel Carbone (nicocarbone) wrote on 2012-02-19:

AcpiTables.txt Edit (95.8 KiB, text/plain; charset="utf-8")
AlsaDevices.txt Edit (1.0 KiB, text/plain; charset="utf-8")
AplayDevices.txt Edit (948 bytes, text/plain; charset="utf-8")
ArecordDevices.txt Edit (647 bytes, text/plain; charset="utf-8")
BootDmesg.txt Edit (53.0 KiB, text/plain; charset="utf-8")
Card0.Amixer.values.txt Edit (4.5 KiB, text/plain; charset="utf-8")
Card0.Codecs.codec.0.txt Edit (14.3 KiB, text/plain; charset="utf-8")
Card1.Amixer.values.txt Edit (499 bytes, text/plain; charset="utf-8")
Card1.Codecs.codec.0.txt Edit (1.3 KiB, text/plain; charset="utf-8")
Card1.Codecs.codec.1.txt Edit (1.3 KiB, text/plain; charset="utf-8")
Card1.Codecs.codec.2.txt Edit (1.3 KiB, text/plain; charset="utf-8")
Card1.Codecs.codec.3.txt Edit (1.3 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (2.5 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (1.9 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (12.7 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (483 bytes, text/plain; charset="utf-8")
PciMultimedia.txt Edit (1.7 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.5 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.7 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (3.6 KiB, text/plain; charset="utf-8")
PulseSinks.txt Edit (4.1 KiB, text/plain; charset="utf-8")
PulseSources.txt Edit (4.5 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (146.7 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (304.8 KiB, text/plain; charset="utf-8")
WifiSyslog.txt Edit (127.6 KiB, text/plain; charset="utf-8")

Brad Figg (brad-figg) on 2012-02-19

Changed in linux (Ubuntu):
status:	New → Confirmed

Revision history for this message

Brad Figg (brad-figg) wrote on 2012-02-25: Test with newer development kernel (3.2.0-17.27)

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

sudo apt-get update
sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

Thank you for your help, we really do appreciate it.

Changed in linux (Ubuntu):
status:	Confirmed → Incomplete
tags:	added: kernel-request-3.2.0-17.27

Revision history for this message

Nicolás Abel Carbone (nicocarbone) wrote on 2012-02-25:

Tested in kernel 3.2.0-17.27. Bug still exist. Changed status to confirmed.

Changed in linux (Ubuntu):
status:	Incomplete → Confirmed

Revision history for this message

Joseph Salisbury (jsalisbury) wrote on 2012-02-27:

Would it be possible for you to test the latest upstream kernel? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.3 kernel[1] (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed by the mainline kernel, please add the following tag 'kernel-fixed-upstream-KERNEL-VERSION'. For example, if kernel version 3.3-rc5 fixed the issue, the tag would be: 'kernel-fixed-upstream-v3.3-rc5'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[1] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.3-rc5-precise/

Changed in linux (Ubuntu):
importance:	Undecided → Medium
tags:	added: needs-upstream-testing
Changed in linux (Ubuntu):
status:	Confirmed → Incomplete

Revision history for this message

Nicolás Abel Carbone (nicocarbone) wrote on 2012-02-27:

Well, I tested with v3.3.0rc5 kernel, and I have some problems.

First of all, when installing the 3.3 kernel, the Nvidia dkms module fails to build, so I can't have the new kernel and Nvidia proprietary driver together. I submitted a bug report for this: bug #942167

Nevertheless, I tried suspending the PC with the new kernel. It does suspend, but it can't resume. After resuming, the PC got stuck and the system speakers emits a constant beep.

Seeing this, I tried the precise kernel without the Nvidia proprietary driver. It does not suspend for a fraction of second (as it does with the Nvidia driver), but can't properly resume after this and the PC got stuck, but without the beeping this time (with the Nvidia driver it resumes fine after the failed suspend).

Please, if there is anything else I can do to help solving this issue, let me know.

Changed in linux (Ubuntu):
status:	Incomplete → Confirmed
tags:	removed: needs-upstream-testing precise

Revision history for this message

Nicolás Abel Carbone (nicocarbone) wrote on 2012-04-21:

I am still having this issue.

I tested with the last 3.3 kernel in the precise mainline and the bug is still happening.

Is there anything else I can do to help solve this problem?

Revision history for this message

Nicolás Abel Carbone (nicocarbone) wrote on 2012-04-26:

Solved the issue. It wasn't related to the Nvidia card. My apologies, I'll set this bug to invalid.

For the record, the problem was that an unidentified USB device was awaking the PC immediately after suspend. I solved the problem by disabling the wake on USB for this devices with this lines on rc.local:

echo USB0>/proc/acpi/wakeup
echo USB2>/proc/acpi/wakeup

Changed in linux (Ubuntu):
status:	Confirmed → Invalid

Revision history for this message

Felix Griewald (tiiunder) wrote on 2012-04-28:

I upgrade to Precise Pangolin.

Standby and hibernation doesn't work. The system wakes up immediately. I tried to use pm-utils and uswsusp

The solution of nicocarbone doesn't solve the problem.

Revision history for this message

Nicolás Abel Carbone (nicocarbone) wrote on 2012-04-28:

@Felix: Maybe the devices waking your PC are different than me. Put this command in the terminal to see which devices can wake the system:

cat /proc/acpi/wakeup

The ones that say "*enabled" are the suspects. Try disabling them individually and test suspend until you found the guilty device. To disable it in the session, without modifying the rc.local file, you must go into a root session by typing this in the terminal:

sudo su -

Then, disable the device wake up with:

echo [device]>/proc/acpi/wakeup

Filling [device] with the 4 o 3 character identifier appearing in the cat command. Then you can add this lines to rc.local to make changes permanent.

Revision history for this message

Felix Griewald (tiiunder) wrote on 2012-04-29:

#10

@Nicolás

I disabled wake-up of all devices, but the problem still exists

Revision history for this message

Piotr Roszatycki (dexter) wrote on 2012-05-02:

#11

20_acpi_wakeup_usb_suspend Edit (428 bytes, text/plain)

/proc/acpi/wakeup hack and disabling all usb devices works for me (Asus 1201N with Nvidia).

I've prepared suspend script in /etc/pm/sleep.d directory and now the notebook suspends correctly.

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

Bug watches keep track of this bug in other bug trackers.

Ubuntulinux package

Suspend is not working on Nvidia hardware

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
linux package