[MSI MS-7693] suspend/resume failure

Bug #1437100 reported by John Stevens
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

During the system tests the computer went into suspension and it didn't resume.

ProblemType: KernelOops
DistroRelease: Ubuntu 15.04
Package: linux-image-3.19.0-10-generic 3.19.0-10.10 [modified: boot/vmlinuz-3.19.0-10-generic]
ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
Uname: Linux 3.19.0-10-generic x86_64
Annotation: This occured during a previous suspend and prevented it from resuming properly.
ApportVersion: 2.16.2-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: lightdm 993 F.... pulseaudio
                      reaperofshred 1762 F.... pulseaudio
 /dev/snd/controlC0: lightdm 993 F.... pulseaudio
                      reaperofshred 1762 F.... pulseaudio
Date: Fri Mar 27 01:03:18 2015
DuplicateSignature: suspend/resume:MSI MS-7693:V2.6
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=a64a8a9c-aad8-4a37-a1dd-74dfe4f05caf
InstallationDate: Installed on 2015-03-27 (0 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
InterpreterPath: /usr/bin/python3.4
MachineType: MSI MS-7693
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic root=UUID=eefdb7e3-3eaa-4b3f-8e22-cdeb5e869ba1 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.19.0-10-generic N/A
 linux-backports-modules-3.19.0-10-generic N/A
 linux-firmware 1.143
SourcePackage: linux
Title: [MSI MS-7693] suspend/resume failure
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 10/08/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V2.6
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: 970A-G46 (MS-7693)
dmi.board.vendor: MSI
dmi.board.version: 2.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 2.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.6:bd10/08/2013:svnMSI:pnMS-7693:pvr2.0:rvnMSI:rn970A-G46(MS-7693):rvr2.0:cvnMSI:ct3:cvr2.0:
dmi.product.name: MS-7693
dmi.product.version: 2.0
dmi.sys.vendor: MSI

Revision history for this message
John Stevens (reaperofshred) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Changed in linux (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.0 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/v4.0-rc5-vivid/

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-unable-to-test-upstream
Revision history for this message
John Stevens (reaperofshred) wrote :

I'm pretty new to this, but I had issues with linux-headers-4.0.0-040000rc5-generic. I'm willing to help if anything else.

Revision history for this message
penalvch (penalvch) wrote :

John Stevens, could you please test the next latest upstream kernel available from the very top line at the top of the page (the release names are irrelevant for testing, and please do not test the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue.

If the test did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-3.XY-rcZ

Where XY and Z are numbers corresponding to the kernel version.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-3.XY-rcZ

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results.

Thank you for your understanding.

tags: added: latest-bios-2.6 needs-upstream-testing
removed: kernel-unable-to-test-upstream
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

No need to install the -headers .deb package. Only the linux-image package for your arch. The 4.0-rc7 kernel is now out, so we might as well test that one.

It can be downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0-rc7-vivid/

The specific .deb file name is: linux-image-4.0.0-040000rc7-generic_4.0.0-040000rc7.201504061936_amd64.deb

Revision history for this message
John Stevens (reaperofshred) wrote :

Thank you for that information. I'm sorry, but because of a malfunction of my wireless usb adapter, I had to get a new one. Well, it's not exactly supported and I learned that the drivers (with a patch needed for recent kernels) were in Arch's User Repository. I'm unable to test because I can't get the rt5592 driver to work with Ubuntu.

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.