[] suspend/resume failure [non-free: nvidia]

[David Gomez]

I tried to suspend the system, but when i was going to resume it, crashed...

ProblemType: KernelOops
Annotation: This occured during a previous suspend and prevented it from resuming properly.
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
InterpreterPath: /usr/bin/python2.6
MachineType:

NonfreeKernelModules: nvidia
Package: linux-image-2.6.28-11-generic 2.6.28-11.39
ProcAttrCurrent: unconfined
ProcCmdLine: root=UUID=6ca8654a-9a0a-4596-a653-b32b5f5a2361 ro quiet splash
ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.28-11.39-generic
SourcePackage: linux
Tags: resume suspend
Title: [] suspend/resume failure [non-free: nvidia]
UserGroups:

[Colin Ian King (colin-king)]

I'd like to get a little more information about the suspend kernel oops. So that we can see if we can capture any kernel panic messages can you do the following:

1. When you boot, add the following setting to the kernel boot parameters:

no_console_suspend=1

2. After the system has booted, press CTRL-ALT-F1 to switch to a console and login

3. At the console, set the console with small fonts so we can more of the kernel console messages:

consolechars -f /usr/share/consolefonts/Uni1-VGA8.psf.gz

4. Go into suspend and see if you get any kernel panic messages, using:

pm-suspend

5. If you get any kernel panic messages, please take a digital photo of the messages and attach it to the bug report.

Thanks

[Colin Ian King (colin-king)]

This bug report was marked as Incomplete a while ago and has not had any feedback to provide the requested information. As a result this bug is being closed. Please reopen if this is still an issue in the latest Karmic 9.10 Alpha release http://cdimage.ubuntu.com/releases/karmic/ . 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.