[Acer AO722] suspend/resume failure

[Artemgy]

Lubuntu 14.10 Beta 2 newly installed
* Close laptop lid to put system into suspend mode and power indicator changes from blue to slow flashing orange, indicating that hardware has entered suspend mode.
* Reopen laptop lid and press a key to wake up, power indicator changes back to steady blue indicating that system is coming back up into full power state.

HOWEVER screen remains completely blank (no backlight) and system appears totally unresponsive (although difficult to tell with no screen).

* Attempted to use hardware function keys to activate screen - nothing.
* Tried ALT-CTRL-F1 then ALT-CTRL-F7 to wake up X, still no display.
* Attempted single press of power button to initiate "Shutdown" - no respone
The only way to procede was to hold the power button for four seconds to kill power and start cold

ProblemType: KernelOops
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-17-generic 3.16.0-17.23 [modified: boot/vmlinuz-3.16.0-17-generic]
ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3
Uname: Linux 3.16.0-17-generic x86_64
Annotation: This occured during a previous suspend and prevented it from resuming properly.
ApportVersion: 2.14.7-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: art 1956 F.... pulseaudio
 /dev/snd/controlC0: art 1956 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory: 'iw'
Date: Mon Sep 29 09:07:32 2014
DuplicateSignature: suspend/resume:Acer AO722:V1.11
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=b164d5a4-08fb-4a10-b285-e36f3997aeae
InstallationDate: Installed on 2014-09-26 (2 days ago)
InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140923)
InterpreterPath: /usr/bin/python3.4
MachineType: Acer AO722
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-17-generic root=UUID=bf9f8de0-2b70-4f49-85ee-54f7d94a6508 ro
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.16.0-17-generic N/A
 linux-backports-modules-3.16.0-17-generic N/A
 linux-firmware 1.134
SourcePackage: linux
Title: [Acer AO722] suspend/resume failure
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 09/25/2012
dmi.bios.vendor: Acer
dmi.bios.version: V1.11
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: JE10-BZ
dmi.board.vendor: Acer
dmi.board.version: Base Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.11
dmi.modalias: dmi:bvnAcer:bvrV1.11:bd09/25/2012:svnAcer:pnAO722:pvrV1.11:rvnAcer:rnJE10-BZ:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.11:
dmi.product.name: AO722
dmi.product.version: V1.11
dmi.sys.vendor: Acer

[Artemgy (artemgy)]

Adding other output requested during bug submission...

[Brad Figg (brad-figg)]

This change was made by a bot.

[Artemgy (artemgy)]

Finished uploading additional info requested at https://wiki.ubuntu.com/DebuggingKernelSuspend
Please advise if you require further info.
Thanks, Artemgy

[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.17 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.17-rc7-utopic/

[Artemgy (artemgy)]

Tagged kernel-fixed-upstream after testing with generic_3.17.0-031700rc7.201409281835
Suspend now works most times, and when it does fail the symptoms differ from those described in this report

[penalvch (penalvch)]

Artemgy, given the scope of this report is suspend, we can say it would be fixed if it suspend works everytime. If it is determined that multiple root issues arise requiring different driver fixes, we can parse the scope down further then.

Hence, did this problem not occur in a release prior to 14.10?

[Artemgy (artemgy)]

Although I do recall suspend issues on this hardware with 14.04, I no longer have any installations prior to 14.10 on which to test. Therefore I am not sure if I can help with regression. However I would be happy to assist with parsing the scope down to determine if there are driver fixes that could resolve this issue 100% of the time on 14.10.

Christoper (or colleagues), could you please advise where I can find instructions to help me do this. Thanks, Artemgy

[penalvch (penalvch)]

Artemgy, one may test prior releases in a live environment via http://releases.ubuntu.com/ .

[Launchpad Janitor (janitor)]

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