suspend/resume failure [non-free: nvidia]

[K8BeBop]

System was I guess in suspend mode, although can't ever remember when I ever had suspend activated. I usually have my system set up to be on forever.

The keyboard was on (because indicator lights where on), but everything I did, pressing keys on keyboard, and moving the mouse did not return the system to "live" mode. The monitor was also off. I pressed the power button, but since under the power management=>General, it says when power button is pressed "Ask Me", since the monitor was off, I could not see the ask me dialog.

So I pressed the power button down all the way to do a hard reset. When it came back up, I got this error. There should be an option, for when you hit the power button, instead of asking me, it should just come out of suspend.

ProblemType: KernelOops
Annotation: This occured during a previous suspend and prevented it from resuming properly.
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ken 1879 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Live'/'SB Live! Value [CT4780] (rev.7, serial:0x80221102) at 0xfa00, irq 18'
   Mixer name : 'Cirrus Logic CS4297A rev 4'
   Components : 'AC97a:43525914'
   Controls : 221
   Simple ctrls : 42
Date: Mon Nov 2 23:19:42 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=45734954-e896-4214-b781-16ce9d0be535
InterpreterPath: /usr/bin/python2.6
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.

 eth1 no wireless extensions.
NonfreeKernelModules: nvidia
Package: linux-image-2.6.31-14-generic 2.6.31-14.48
ProcCmdLine: root=UUID=9fedd576-9c6c-415b-bcda-871c227e3761 ro quiet splash
ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-14-generic N/A
 linux-firmware 1.24
RfKill:

SourcePackage: linux
Tags: resume suspend
Title: suspend/resume failure [non-free: nvidia]
Uname: Linux 2.6.31-14-generic x86_64
UserGroups:

WpaSupplicantLog:

dmi.bios.date: 03/07/2006
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: KV2
dmi.chassis.type: 3
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd03/07/2006:svn:pn:pvr:rvn:rnKV2:rvr:cvn:ct3:cvr:

[Jeremy Foshee (jeremyfoshee)]

Hi K8BeBop,

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? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

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

apport-collect -p linux 472163

Also, if you could 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.]

[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 release http://www.ubuntu.com/getubuntu/download . 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.]