[ASRock N68C-GS FX] suspend/resume failure

[paregistrase]

computer doesn't recover from suspend

ProblemType: KernelOops
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-13-lowlatency 3.13.0-13.33
ProcVersionSignature: Ubuntu 3.13.0-13.33-lowlatency 3.13.5
Uname: Linux 3.13.0-13-lowlatency x86_64
Annotation: This occured during a previous suspend and prevented it from resuming properly.
ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: ruben 2263 F.... pulseaudio
 /dev/snd/controlC0: ruben 2263 F.... pulseaudio
Date: Wed Feb 26 02:04:16 2014
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=8c36e8e0-c964-4d5c-ba2c-bad380a91842
InstallationDate: Installed on 2013-12-20 (67 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
InterpreterPath: /usr/bin/python3.4
IwConfig:
 eth0 no wireless extensions.

 lo no wireless extensions.
Lsusb:
 Bus 001 Device 004: ID 0bda:0111 Realtek Semiconductor Corp. RTS5111 Card Reader Controller
 Bus 001 Device 003: ID 07ca:a835 AVerMedia Technologies, Inc.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 002: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for Bluetooth
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-13-lowlatency root=UUID=4c60bb71-7633-49c5-a615-c16182697c70 ro persistent radeon.dpm=1 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-13-lowlatency N/A
 linux-backports-modules-3.13.0-13-lowlatency N/A
 linux-firmware 1.125
RfKill:

SourcePackage: linux
Title: [To Be Filled By O.E.M. To Be Filled By O.E.M.] suspend/resume failure
UpgradeStatus: Upgraded to trusty on 2014-01-02 (54 days ago)
UserGroups:

dmi.bios.date: 10/31/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.40
dmi.board.asset.tag: BC5FF4813CA6
dmi.board.name: N68C-GS FX
dmi.board.vendor: ASRock
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.:bvrP1.40:bd10/31/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68C-GSFX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

[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.13 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-rc4-trusty/

[paregistrase (paregistrase)]

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14-rc4-trusty/ doesn't resolve the issue

[penalvch (penalvch)]

paregistrase, did this problem not occur in a release prior to Trusty?

[penalvch (penalvch)]

paregistrase, please stop removing the tags:
amd64 apport-kerneloops package-from-proposed resume suspend third-party-packages trusty

[paregistrase (paregistrase)]

In Saucy the suspend funtion works.
The problem arose during Trusty development cycle.

[penalvch (penalvch)]

paregistrase, the next step is to fully commit bisect from Saucy to Trusty, in order to identify the offending commit. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

[paregistrase (paregistrase)]

With a recent update, kernel 3.13.0-20-lowlatency, suspend/resume is working again!!!

[paregistrase (paregistrase)]

But kernel 3.14 still gets frozen after resuming...
I hope this will be helpfull, the commit bisect is a bit out of my range.

[penalvch (penalvch)]

paregistrase, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1284909/comments/10 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.