10de:1183 Suspend to RAM is broken

[Julien Aubin]

On my computer using nvidia 304.88 or nouveau, when I suspend the OS to RAM a blinking cursor appears but the process is halted and the computer does not respond until a hard reboot is performed. Also tested with kernel 3.9rc6 and same behavior happens, so it looks like an upstream bug. I think the regression actually occurred between Precise and Quantal, as under Precise things went smoothly while under Quantal behavior as above occurred.

WORKAROUND: Put in /etc/rc.d the following line before exit 0 :
echo 0 > /sys/power/pm_async

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: linux-image-3.8.0-19-generic 3.8.0-19.29
ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
Uname: Linux 3.8.0-19-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.9.2-0ubuntu8
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: julien 5770 F.... pulseaudio
 /dev/snd/controlC0: julien 5770 F.... pulseaudio
 /dev/snd/pcmC0D0p: julien 5770 F...m pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Date: Mon Apr 22 19:37:18 2013
HibernationDevice: RESUME=UUID=1e2e6306-5da1-44ae-98dd-d137e96a8425
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.

 eth1 no wireless extensions.
Lsusb:
 Bus 002 Device 002: ID 045e:0719 Microsoft Corp. Xbox 360 Wireless Adapter
 Bus 002 Device 003: ID 046d:0928 Logitech, Inc. QuickCam Express
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: System manufacturer System Product Name
MarkForUpload: True
ProcFB:

ProcKernelCmdLine: root=UUID=53dfbfeb-5955-48e2-9039-e6c3b9b219d0 ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-19-generic N/A
 linux-backports-modules-3.8.0-19-generic N/A
 linux-firmware 1.106
RfKill:

SourcePackage: linux
UpgradeStatus: Upgraded to raring on 2013-04-07 (14 days ago)
WifiSyslog:

WpaSupplicantLog:

dmi.bios.date: 10/02/2008
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: ASUS M2N-SLI DELUXE ACPI BIOS Revision 1701
dmi.board.name: M2N-SLI DELUXE
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 1.XX
dmi.chassis.asset.tag: 123456789000
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2N-SLIDELUXEACPIBIOSRevision1701:bd10/02/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N-SLIDELUXE:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org.

[0] https://wiki.ubuntu.com/Bugs/Upstream/kernel

[Julien Aubin (gojulgarbmail)]

Yes I'm also convinced it is an upstream bug. However I don't know which driver is faultly. I only know the following elements :
- NVidia binary driver is not faultly. (I could test the same driver on another NVidia card and suspend fully worked)
- None of my USB devices seem to be faultly (tried to unplug my webcam, but this did not change anything. Same thing with my Xbox controller)
- The HP print driver is not faulty, other computers I have with the same driver running do not have the problem.
- I suspect stg wrong with either the driver of my chipset, an NForce 570 SLI, or maybe the Sata controller driver, a JMicron XXX, as when I suspend the first hard disk (sda) is suspended but not the other ones. (I could test it with rebooting my computer and the first hard disk was not even recognized by my BIOS until I completely switched off the computer)

Could you help me on that point please ?

[Julien Aubin (gojulgarbmail)]

Found actual workaround there :
http://ubuntuforums.org/showthread.php?t=1978290

Maybe it should be included in the default pm-utils package, as it seems to be a fairly common issue.

[Dave Chiluk (chiluk)]

There seems to be two issues at play in that bug. Not sure how much they are related. One where people can get to the virtual consoles using ctrl+alt+f1 and one where they are not.

When my machine comes back from resume it does not take any input, but instead drops me at a black screen with a single underscore cursor. It is dead, and can not even be ssh'ed into.

[Dave Chiluk (chiluk)]

I think I discovered the difference between the above two situations.

In the case where the virtual consoles are reachable the nouveau driver is in use.

In the case where there is just a black screen with a cursor and no interactivity the nvidia drivers are in use.

[Julien Aubin (gojulgarbmail)]

Hi,

Actually this is corresponds to Kernel bug #48951.

Workaround is as follows :
- Put in /etc/rc.d the following line (before exit 0) :
echo 0 > /sys/power/pm_async

This works.

The issue is related to NVidia MCP55 chipset.

Rgds

[penalvch (penalvch)]

Julien Aubin, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

[Julien Aubin (gojulgarbmail)]

Hi,

With the workaround I provided the bug is not there, but without it it is still there.

Now as this bug has many duplicates you can close it, but please at least provide the workaround in Ubuntu release notes.

Rgds

[penalvch (penalvch)]

Julien Aubin, so in Trusty, the bug is still reproducible without the WORKAROUND correct?

As well, this bug has no duplicates, so it wouldn't be closed unless it's fixed or you say it's closed.

[Julien Aubin (gojulgarbmail)]

Hi Christopher,

Yes this is exactly the case, the bug is still not fixed. But in case you couldn't fix it until trusty release just publish the workaround as a release note, as it targets a rather old chipset model.

Rgds,

[penalvch (penalvch)]

Julien Aubin, would using nouveau provide a WORKAROUND as well?

[Julien Aubin (gojulgarbmail)]

Hi Christopher,

No, this is completely unrelated to NVidia graphics. My father uses an Intel Core i5 CPU with B75 chipset and the nvidia graphics blob, and he's not affected.

The culprit is the NForce driver, as explained in the kernel mailing list.

[penalvch (penalvch)]

Julien Aubin, just to clarify, regarding only the computer you filed against in this report, this problem is reproducible using nouveau as well correct (you originally reported this using the nvidia proprietary drivers)?

>"The culprit is the NForce driver, as explained in the kernel mailing list."

Could you please provide a direct URL to this discussion?

[Julien Aubin (gojulgarbmail)]

Hi,

So yes on the computer on which I reported the issue the issue is also reproducible with Nouveau driver.

Discussion URL (actually kernel bug) : https://bugzilla.kernel.org/show_bug.cgi?id=48951

Rgds,

[penalvch (penalvch)]

Julien Aubin, the next step is to fully commit bisect from Precise to Quantal, in order to identify the offending commit. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

[Ravenise (ravenise)]

I have not shut my computer off for 1.5 years non stop due to this bug. Both suspend to ram and hibernation freeze the kernel, leaving a backlit HDMI LCD monitor with blinking cursor. Computer fans remain running, power light remains steady, when should be blinking. Does not wake from this state. USB Keyboard and mouse unresponsive, leaving no way to access virtual consoles using ctrl+alt+f1. Hard reboot is necessary. Suspend worked fine for years with all the same hardware including two different ATI cards (ATI Radeon 4850 & 7850). After switching to an NVIDIA Geforce GTX 660 the kernel began to crash on suspend.
The model number of my card is similar, 10de:1183, though mine is not a TI. Suspend & hibernate fails across the board on Mint 13, 14, 15, 16, and 17 and latest Ubuntu development build. I've tried nearly everything, including the latest video drivers, custom suspend / hibernate executions. Changing every bios setting related to IRQ, power management, and "suspend." Switching between DVI and HDMI ports, etc.

I would like to try the workaround but I am using mint 17, and /etc/rc.d doesn't exist. Where would I place this in Mint 17? Please help.

[penalvch (penalvch)]

Ravenise, thank you for your comment. So your issue may be dealt with as soon as possible, and so your hardware may be tracked by having necessary debugging information automatically attached, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu repository kernel via:
ubuntu-bug linux

For more on why this is most helpful, please read the official Ubuntu documentation from the respective Ubuntu developer groups, and triage teams:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies
https://wiki.ubuntu.com/Kernel/Policies/DuplicateBugs
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.