[jaunty] Crash during test-suspend first step

[syldeb35]

suspend always crash.
try the script found here:
https://wiki.ubuntu.com/KernelTeam/SuspendResumeTesting
this is the result.

ProblemType: KernelOops
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/share/apport/apportcheckresume
FlagFile: suspend
InterpreterPath: /usr/bin/python2.5
NonfreeKernelModules: nvidia
OopsText: Suspend/Resume or hibernate problem

Originator: Steve Conklin <email address hidden>
Package: linux-image-2.6.28-7-server 2.6.28-7.20
ProcAttrCurrent: unconfined
ProcCmdLine: User Name=UUID=aaa4d0c3-cab9-47fa-9ed7-b75d019c9a8d ro quiet splash
ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.28-7.20-server
SourcePackage: linux
Tags: suspend resume hibernate
Title: Suspend/Resume or hibernate problem
UserGroups:

[Andy Whitcroft (apw)]

Could you please let us know the type of machine this is (make and model). When you suspended did the machine break while going to sleep, or while coming back from sleep? Is this reproducible say over 10 cycles. Has suspend ever worked in the past, if so which kernel release (cat /proc/version_signature)? Please include any information as to the circumstances leading up to this failure. Did the machine lock up, did any messages come out? If it is reproducible could you try the suspend from VT1, press ctrl-alt-F1, login, and run pm-suspend there. If you could test and report back here that would be helpful.

[syldeb35 (sylvain-debray)]

Hi,
The machine is an Acer Aspire 9805WKHi
the problem is when it come back from suspend. I see the HDD led blinking for 2 sec. then, nothing else. The keyboard did not response and the screen remain black...
The suspend never work before. I just try with 7.04 live CD and the response was "can not enter suspend..."
With kernel 2.6.27-11-generic: same result
when running pm-suspend same thing append.
I also try with driver "nv" in xorg.conf: same result.

[Alex Denvir (coldfff)]

We are closing this bug report because it has not been updated for some time. Please reopen it if you have more information to submit, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!