[MSI MS-7346] suspend/resume failure

[szu]

the screen turned off (dpms-like), the computer remained powered-up but did not respond to mouse/keyboard

ProblemType: KernelOops
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-19-generic 3.13.0-19.39
ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6
Uname: Linux 3.13.0-19-generic x86_64
Annotation: This occured during a previous suspend and prevented it from resuming properly.
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: sz 1879 F.... pulseaudio
 /dev/snd/controlC0: sz 1879 F.... pulseaudio
CurrentDmesg:
 [ 47.322892] type=1400 audit(1395526856.902:68): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=2105 comm="apparmor_parser"
 [ 47.322901] type=1400 audit(1395526856.902:69): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=2105 comm="apparmor_parser"
 [ 47.323333] type=1400 audit(1395526856.902:70): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=2105 comm="apparmor_parser"
Date: Sat Mar 22 23:20:31 2014
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=4084a9ca-831b-44dc-8245-aea2e8b8e4f1
InstallationDate: Installed on 2014-03-22 (0 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140321)
InterpreterPath: /usr/bin/python3.4
IwConfig:
 eth0 no wireless extensions.

 lo no wireless extensions.
MachineType: MSI MS-7346
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-19-generic root=UUID=2ad58448-4856-492d-b367-c37475ea07c8 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-19-generic N/A
 linux-backports-modules-3.13.0-19-generic N/A
 linux-firmware 1.126
RfKill:

SourcePackage: linux
Title: [MSI MS-7346] suspend/resume failure
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 04/13/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V1.0
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: MS-7346
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.0:bd04/13/2007:svnMSI:pnMS-7346:pvr1.0:rvnMSI:rnMS-7346:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: MS-7346
dmi.product.version: 1.0
dmi.sys.vendor: MSI

[Brad Figg (brad-figg)]

This change was made by a bot.

[szu (szulat)]

ubuntu 10.10 is able to suspend/resume the same machine when using nvidia drivers (but it fails when using vesa).
ubuntu 14.04 fails in both cases.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.14 kernel[0].

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'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14-rc7-trusty/

[szu (szulat)]

finally, i found some time, and tried suspending with the most recent mainline kernel for trusty (which at this time is http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.15-rc2-trusty/ ) and it behaves the same (except that it is not compatible with nvidia drivers from xorg edgers so i can't test if nvidia is better than vesa in this case)

i also did the same starting in recovery mode, then from the root promot (staying in text mode) removed most kernel modules and called pm-suspend - and the result was still the same.