Comment 0 for bug 329645

Revision history for this message
René Kliment (renekliment) wrote :

If I try to suspend my system(to RAM), it seems, that it is suspended correctly(according to behavior in "Windows(R) beta 7" after suspend - blinking LEDs, etc). However, when I press any key to wake up my system, It will start trying to wake up, but after a few seconds, my laptop will shutdown and after more few second start/wake up/switch on/whatever again, but with black screen and absolutely no control - not responding to key pressing - in my opinion - kernel panic. I have to do "hard" shutdown of my laptop. Same behavior in Arch Linux, kernel 2.6.28, but older versions of kernel, or any other package does the same error :-(

My laptop is MSI EX600X-074CZ. Current Ubuntu: 9.04 some latest alpha.
I hope, Ubuntu automatic reporting system provided so much informations as needed, if not, I can send you anything you want :-)

By the way, when pushed the button Report the problem, it opened link in web browser "file:///ubuntu/+source/linux/+filebug/xQfNWvFcA4EUB34An4w9bxyLsWr", there is missing http://launchpad.net . It will be better to add it there :-)

Thank you very much, if you will be occupied with my bug, it could really help me, thanks.

ProblemType: KernelOops
Architecture: amd64
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-generic 2.6.28-7.20
ProcAttrCurrent: unconfined
ProcCmdLine: User Name=UUID=386150e0-a37d-482c-a790-21fb2ff41816 ro quiet splash
ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.28-7.20-generic
SourcePackage: linux
StressLog: Error: [Errno 2] No such file or directory: '/var/lib/pm-utils/stress.log'
Tags: suspend resume hibernate
Title: Suspend/Resume or hibernate problem
UserGroups: