KMS causes hibernate to hang on "GeForce Go 6800" (Dell Inspiron 9300)

Bug #558927 reported by Stephen Warren
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

When I attempt to hibernate my laptop using the Gnome menu item, there's a bunch of disk activity, the screen goes black but the backlight stays on, and then the system hangs; it never completes the hibernate process and never powers itself off.

If I switch to a "text-mode" VT and "sudo stop gdm" to kill the X server, then run "sudo pm-hibernate", I get the same behavior.

If I modify the kernel cmdline to remove "quiet splash" and add "nomodeset", then run "sudo pm-hibernate" from a text-mode VT, the hibernate process completes and the system powers off. However, when I start the system back up again (making the same kernel cmdline changes if it matters), the VTs aren't correctly restored; they're filled with odd colors and characters and don't get cleared up by typing or VT-switching. In this state, typing "sudo reboot" works OK.

WORKAROUND: Installing package nvidia-current, and using the binary NVIDIA driver solves this; I have hibernate/restore'd once now.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-19-generic 2.6.32-19.28
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-19-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: swarren 1743 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'ICH6'/'Intel ICH6 with STAC9750,51 at irq 16'
   Mixer name : 'SigmaTel STAC9750,51'
   Components : 'AC97a:83847650'
   Controls : 38
   Simple ctrls : 24
Date: Thu Apr 8 21:11:59 2010
HibernationDevice: RESUME=UUID=33208fbf-1a49-4198-a33b-d13d6dbe4d99
MachineType: Dell Inc. Inspiron 9300
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-19-generic root=/dev/mapper/vg_esk2-lv_root ro quiet splash
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.33
RfKill:
 0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
WpaSupplicantLog:

dmi.bios.date: 09/19/2005
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A05
dmi.board.name: 0MD541
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA05:bd09/19/2005:svnDellInc.:pnInspiron9300:pvr:rvnDellInc.:rn0MD541:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Inspiron 9300
dmi.sys.vendor: Dell Inc.

Revision history for this message
Stephen Warren (srwarren) wrote :
Revision history for this message
Stephen Warren (srwarren) wrote :

Attaching /var/log/pm-suspend.log, since I saw it requested in similar bug reports.

Revision history for this message
Stephen Warren (srwarren) wrote :

Note: Hibernate/resume worked fine under the latest Karmic kernel, although I wasn't using KMS there, and had the NVIDIA binary driver installed instead of nouveau.

Revision history for this message
Stephen Warren (srwarren) wrote :

I note this bug is tagged with needs-upstream-testing. https://wiki.ubuntu.com/KernelTeam/MainlineBuilds says to use http://kernel.ubuntu.com/~kernel-ppa/info/kernel-version-map.html to find the upstream version to test against. However, http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.32.10-lucid/ doesn't contain anything to test. Should I just test the latest version I can see there; http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.34-rc3-lucid/ (although since lucid appears to be targetting 2.6.32, I'm not sure what testing 2.6.34 would really tell us, except that something needs to be back-ported)

Revision history for this message
Andrei Bordei (andrei-bordei) wrote :

Same issue for me on HP 6715b.

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi Stephen,

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. 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. Please let us know your results.

Thanks in advance.

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

tags: added: kernel-hibernate
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Stephen Warren (srwarren) wrote :

The basic answer: Nothing is better with the various upstream kernels I tried.

Slightly more details: If KMS isn't active, hibernate/restore appears to work with upstream kernels. If KMS is active, hibernate hangs whether invoked by Gnome GUI or from a text VT with X stopped.

With upstream kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.32.12-lucid/, KMS doesn't work, so X won't start claiming that there are no DRI devices, and I get a low-resolution text VT. If I "sudo pm-hibernate" here, hibernate and restore work OK.

With upstream kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.33.3-lucid/, KMS and X work. Hibernate from X using Gnome GUI hangs. Hibernate from a (KMS) text console with X stopped hangs. If I boot with "nomodeset" (X won't start claiming that there are no DRI devices) then hibernate from a (low-resolution) text VT, hibernate and restore works OK.

With upstream kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.34-rc5-lucid/, KMS works, but X won't start, claiming that there are no DRI devices. Hibernate from a (KMS) text console hangs. If I boot with "nomodeset" then hibernate from a (low-resolution) text VT, hibernate and restore works OK.

Hopefully I didn't mix any of the above up...

Changed in linux (Ubuntu):
status: Incomplete → New
Revision history for this message
Stephen Warren (srwarren) wrote :

FYI, installing package nvidia-current, and using the binary NVIDIA driver solves this; I have hibernate/restore'd once now.

Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
tags: removed: regression-potential
Revision history for this message
G.C. Hassink (gchassink) wrote :

I have the same problem with my Toshiba Satellite L20-155, with build-in Ati Radeon Xpress200m.

Revision history for this message
penalvch (penalvch) wrote :

Stephen Warren, thank you for reporting this and helping make Ubuntu better. 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 provide the information following https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume ? As well, can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ . However, note you can only test Suspend, not Hibernate, when using a LiveCD. If the issue remains, 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 <BUGNUMBER>

Additionally, if you could try to reproduce this with the upstream mainline kernel that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. 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 in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

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'.

Please let us know your results. Thanks in advance.

description: updated
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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