[LUCID] Resume Failure after (apparently) successful suspend

Bug #503474 reported by Noel J. Bergman
42
This bug affects 7 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Incomplete
Medium
Unassigned

Bug Description

Host: Thinkpad T61p 6457-7WU

When running with Karmic and the nvidia driver I can suspend and resume (so long as there isn't an SD card mounted in the reader). With Lucid and the same driver, the computer appears to suspend successfully, but it fails to resume. Upon resume, the display is corrupt, I cannot switch to a VT (I have verified that in lieu of suspend/resume, switching to a VT works), and I have to power off to recover.

ProblemType: Bug
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
   Subdevices: 2/2
   Subdevice #0: subdevice #0
   Subdevice #1: subdevice #1
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: noel 1777 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfe220000 irq 17'
   Mixer name : 'Analog Devices AD1984'
   Components : 'HDA:11d41984,17aa20bb,00100400'
   Controls : 29
   Simple ctrls : 18
Date: Tue Jan 5 13:14:09 2010
DistroRelease: Ubuntu 10.04
InstallationMedia: Error: [Errno 13] Permission denied: '/var/log/installer/media-info'
MachineType: LENOVO 64577WU
NonfreeKernelModules: nvidia
Package: linux-image-2.6.32-9-generic 2.6.32-9.13
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: root=UUID=ae69c138-346e-459a-857a-fc78e1bf34e9 ro quiet splash
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-9.13-generic
Regression: Yes
RelatedPackageVersions: linux-firmware 1.28
Reproducible: Yes
SourcePackage: linux
Tags: lucid needs-upstream-testing regression-potential
TestedUpstream: No
Uname: Linux 2.6.32-9-generic x86_64
dmi.bios.date: 05/11/2009
dmi.bios.vendor: LENOVO
dmi.bios.version: 7LETC6WW (2.26 )
dmi.board.name: 64577WU
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr7LETC6WW(2.26):bd05/11/2009:svnLENOVO:pn64577WU:pvrThinkPadT61p:rvnLENOVO:rn64577WU:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 64577WU
dmi.product.version: ThinkPad T61p
dmi.sys.vendor: LENOVO

Revision history for this message
Noel J. Bergman (noeljb) wrote :
Revision history for this message
Noel J. Bergman (noeljb) wrote :
Revision history for this message
Noel J. Bergman (noeljb) wrote :
Revision history for this message
Andy Whitcroft (apw) wrote :

Can you confirm which driver you are using for your nvidia graphics card? If it is the binary one can you confirm if the issue occurs without it and report back here. Thanks.

Changed in linux (Ubuntu):
status: New → Triaged
status: Triaged → Incomplete
importance: Undecided → Medium
Revision history for this message
Noel J. Bergman (noeljb) wrote :

Andy,

Of course I'm using the nvidia driver -- the same one that works with karmic and earlier builds -- I want my video to work!

Which of nv or nouveau do you want for me to try? Does nv support suspend/resume now? And I understand that the Ubuntu release of nouveau is significantly useless except for testing. But if it will help distinguish where to look, I'll be happy to temporarily replace the video driver with something that helps you debug.

Revision history for this message
Noel J. Bergman (noeljb) wrote :

Update: after the recent batches of Lucid updates, I tried again today. Still using nvidia-current as the driver (again, please advise as to which other driver you'd like tested).

The system suspends nicely, and appears to resume quickly, except that the video is corrupt, appearing with a blocky, VGA, random characters in memory sort of look. The system did not appear to respond to key strokes, e.g., CAPS-LOCK did not toggle the LED. However, after another minute or so, it appeared to respond to CTRL-ALT-F1 (although the display was still dead), and CTRL-ALT-F7. That appeared to wake something up such the X display came up, although with the desktop full of random patterns. Toggling the theme caused the final refresh, and all appears well.

Hope that this helps.

Revision history for this message
Noel J. Bergman (noeljb) wrote :
Revision history for this message
Noel J. Bergman (noeljb) wrote :
Revision history for this message
Clarke Brunsdon (crimson-uvic) wrote :

I'm in the same boat with a different nvidia card:
  01:00.0 VGA compatible controller: nVidia Corporation G84 [GeForce 8600M GT] (rev a1)

Revision history for this message
Noel J. Bergman (noeljb) wrote :

Andy, I am not reproducing this when booting without the nvidia driver. And at the moment, I cannot get the nvidia-current driver to work properly with 2.6.32-12, although it works with 2.6.32-11.

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.