[MSI MS-7798] suspend/resume failure

[Otus]

Resuming from suspend doesn't work in saucy. I'm fairly sure it used to work in quantal and/or raring on this system.

ProblemType: KernelOops
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-12-generic 3.11.0-12.19
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic x86_64
Annotation: This occured during a previous suspend and prevented it from resuming properly.
ApportVersion: 2.12.5-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: jan 2244 F.... pulseaudio
 /dev/snd/controlC0: jan 2244 F.... pulseaudio
Date: Thu Oct 24 09:50:00 2013
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=e0277693-525b-4851-972b-251b4a765c6d
InstallationDate: Installed on 2012-11-10 (347 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
InterpreterPath: /usr/bin/python3.3
MachineType: MSI MS-7798
MarkForUpload: True
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=1c693e72-bdec-48cc-9dc7-fc690466dc38 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding.
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-12-generic N/A
 linux-backports-modules-3.11.0-12-generic N/A
 linux-firmware 1.116
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: yes
  Hard blocked: no
SourcePackage: linux
Title: [MSI MS-7798] suspend/resume failure
UpgradeStatus: Upgraded to saucy on 2013-10-18 (5 days ago)
UserGroups:

dmi.bios.date: 07/30/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V1.3
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B75MA-P45 (MS-7798)
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: MSI
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.3:bd07/30/2012:svnMSI:pnMS-7798:pvr1.0:rvnMSI:rnB75MA-P45(MS-7798):rvr1.0:cvnMSI:ct3:cvr1.0:
dmi.product.name: MS-7798
dmi.product.version: 1.0
dmi.sys.vendor: MSI

[Brad Figg (brad-figg)]

This change was made by a bot.

[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.12 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.12-rc6-saucy/

[Otus (jan-varho)]

Suspend works fine with the latest mainline PPA kernel:
$ uname -a
Linux freyja 3.12.0-031200rc6-generic #201310191635 SMP Sat Oct 19 20:36:43 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

[penalvch (penalvch)]

Otus, as per http://www.msi.com/product/mb/B75MA-P45.html#/?div=BIOS an update is available for your BIOS (1.9). If you update to this following https://help.ubuntu.com/community/BiosUpdate , does it change anything?

If not, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful.

For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette .

Thank you for your understanding.

[Otus (jan-varho)]

I'm not going to risk a BIOS update, when the motherboard used to work fine. Whether a BIOS update would fix the issue or not, this is a regression in Ubuntu.

[penalvch (penalvch)]

Otus, regarding your comments https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1244079/comments/6 :
>"Whether a BIOS update would fix the issue or not, this is a regression in Ubuntu."

That's not how it works. If you have buggy and outdated BIOS, this wouldn't be considered a regression in Ubuntu.

Thank you for your understanding.

[Otus (jan-varho)]

I'm not going to fight over your decision to mark this as incomplete, but a regression is a regression and there's no evidence a BIOS update would even fix this.

[Launchpad Janitor (janitor)]

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

[Otus (jan-varho)]

I'm now on Trusty and latest BIOS and it still doesn't work, so I'm setting this back to confirmed.

[Otus (jan-varho)]

$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
V1.9
09/30/2013

[penalvch (penalvch)]

Otus, could you please test the latest mainline kernel via http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.15-rc7-utopic/ and advise to the results?

[Launchpad Janitor (janitor)]

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