[MICRO-STAR INT'L CO.,LTD. MS-1034][MSI M662] suspend/resume failure. Black Screen. Intel GMA 950. Ralink RT73 Wlan

[Das Auge]

This bug-report belongs to Bug #357258.
First Apport did not file the bug, now it did. So here is the collected information.

 I tried the suspend stress test and it failed at the first resume. It restartet after suspend, but the backlight did not turn on.
The problem occurrs everytime I try to go to standby.
 With Jaunty standby mode never worked, but I think I remember, with a prior version it did. Maybe with gutsy. Can't remember exactly.
 Hibernate works fine.
 "sync; echo 1 > /sys/power/pm_trace; pm-suspend" gives me just a "0" after the freeze with black screen.

ProblemType: KernelOops
Annotation: This occured during a previous suspend and prevented it from resuming properly.
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
InterpreterPath: /usr/bin/python2.6
MachineType: MICRO-STAR INT'L CO.,LTD. MS-1034
Package: linux-image-2.6.28-11-generic 2.6.28-11.40
ProcAttrCurrent: unconfined
ProcCmdLine: root=UUID=7aa9ed17-60dd-41c3-b9f0-601b47fae855 ro quiet splash
ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.28-11.40-generic
SourcePackage: linux
StressLog: Error: [Errno 2] No such file or directory: '/var/lib/pm-utils/stress.log'
Tags: resume suspend
Title: [MICRO-STAR INT'L CO.,LTD. MS-1034] suspend/resume failure
UserGroups:

[Ian Corne (icorne)]

I too suffer from this bug. I think it has to do with the intel graphics driver.

[Das Auge (0815jo)]

I am using the actual januty release, and the problem ist still there.
I cannot resume after suspend.

[Das Auge (0815jo)]

Sorry, I forgot to say: I have a dual boot system with Debian Lenny and Ubuntu Jaunty. With Lenny the suspend/resume works out of the box.

So it should not be impossible to resolve this problem.

[Das Auge (0815jo)]

Now the Notebook M662 passes the suspend/resume test completely, so we can close this bug.

[StoatWblr (stoatwblr)]

It's happening in Karmic too. Alpha4 clean install and updated.

[JohnnyRico (jonny245)]

Same problem with Karmic!

:(

[LVU (valentin-lavrinenko)]

My M662 with Karmic has this problem too

[Sava (slava-shklyar)]

The same bug in Lucid.

[Das Auge (0815jo)]

I can't suspend in Precise. So I reopened the bug.

[StoatWblr (stoatwblr)]

Ditto. :(

[penalvch (penalvch)]

Das Auge, 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? If so, could you please provide the information following https://wiki.ubuntu.com/DebuggingKernelSuspend ? As well, 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 in the development release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

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.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.

Please let us know your results. Thanks in advance.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]