[Acer AO 751h] Laptop requires a hard reset to recover from suspend state

Bug #1358921 reported by Gonmator
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

Description: Ubuntu 14.04.1 LTS
Release: 14.04

Since update to Lubuntu 14.04.1 from lubuntu 13.10, the laptop is not able to resume from suspend anymore. I've checked this happens runing lubuntu 14.04.01 LiveCD too (but not with the LiveCD of previous version of Lubuntu). If I start the OS with the previous kernel 3.11.0-26 I have not the problem. But starting with kernel 3.13.0-32 or 3.13.0-34 it is there.

If I suspend the laptop closing the lid, or from the menu, pressing the power button (to show the exit menu) or running sudo pm-suspend, the laptop get suspended, the screen will off, and the power button led blinks as expected. But then it is not possible to awake again neither pressing a key or pressing the power button. If in that state I try to power off keeping pressed the power button, that still does not work: the blink led still blinks and nothing happens. The only way to recover the system is removing the battery and turning on again.

That I expect:
After suspend the laptop, I am able to resume it again, just pressing a key, or pressing the power button.

I've tried starting with "acpi_osi=linux" but didn't help. (anyway, that was not necessary with the previous kernel/OS version).

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-34-generic 3.13.0-34.60
ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
Uname: Linux 3.13.0-34-generic i686
ApportVersion: 2.14.1-0ubuntu3.3
Architecture: i386
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No existe el archivo o el directorio: 'iw'
CurrentDesktop: LXDE
Date: Tue Aug 19 22:26:06 2014
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=25620b94-5943-42f1-8b93-c4922fd4ceb1
Lsusb:
 Bus 001 Device 002: ID 0c45:62c0 Microdia Sonix USB 2.0 Camera
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Acer AO751h
ProcFB: 0 psbdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic root=UUID=0e9dd9a1-128b-47a7-bd68-575ef7fb2073 ro quiet splash acpi_osi=linux vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-34-generic N/A
 linux-backports-modules-3.13.0-34-generic N/A
 linux-firmware 1.127.5
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/27/2009
dmi.bios.vendor: Acer
dmi.bios.version: V0.3202
dmi.board.name: JV11-ML
dmi.board.vendor: Acer
dmi.board.version: Not Applicable
dmi.chassis.type: 1
dmi.chassis.vendor: Acer
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAcer:bvrV0.3202:bd04/27/2009:svnAcer:pnAO751h:pvrNotApplicable:rvnAcer:rnJV11-ML:rvrNotApplicable:cvnAcer:ct1:cvrN/A:
dmi.product.name: AO751h
dmi.product.version: Not Applicable
dmi.sys.vendor: Acer

Revision history for this message
Gonmator (gonmator) wrote :
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
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 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-rc1-utopic/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Gonmator (gonmator) wrote :

Reproduced in latest upstream kernel too.
Thanks!

tags: added: kernel-bug-exists-upstream
removed: needs-upstream-testing
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
penalvch (penalvch)
tags: added: bios-outdated-3212
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Gonmator (gonmator) wrote :

I've updated the BIOS as indicated, but nothing changed:

When I suspend the netbook, closing the lid, fom the exit menu option or typing "sudo pm-suspend", the netbook become suspended (no activity, power button blinking) but there are no way to resume it again: neither pressing a key, neither pressing power button. Even holding the power button pressed down by more or 4 seconds nothing change (the netbook do not become to power-off state). the only way to use the system again is removing the battery and starting again.

The output of the commands:
V0.3212
02/26/2010

Thanks!

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Gonmator, could you please test the latest upstream kernel available from the very top line at the top of the page (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine 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:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested exactly shown as:
kernel-fixed-upstream-3.17-rc3

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

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-3212
removed: bios-outdated-3212
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Gonmator (gonmator) wrote :

Tested with latest upstream: kernel 3.17-rc4.
The bug is not fixed. Exactly the same behaviour as before.

Thanks!

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
tags: added: kernel-bug-exists-upstream-3.17-rc4
penalvch (penalvch)
tags: added: regression-release
Revision history for this message
penalvch (penalvch) wrote :

Gonmator, the next step is to fully commit bisect the kernel in order to identify the fix commit. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Gonmator (gonmator) wrote :

Done. The first "bad" version was Ubuntu-3.13.0-1.16 and the last "good" Ubuntu-3.12.0-8.16. Because the non linear commits, I made bisect using upstream kernel from v3.12 to v3.13-rc1. That was the result:
"
6bfd1e63de34a278d67db32e3644340838308252 is the first bad commit
commit 6bfd1e63de34a278d67db32e3644340838308252
Author: Johannes Thumshirn <email address hidden>
Date: Wed Oct 23 13:31:00 2013 +0200

    mfd: lpc_sch: Ignore resource conflicts when adding mfd cells

    Currently probe of lpc_sch fails on Intel Poulsbo because of ACPI resource
    conflicts. A solution is to set the ignore_resource_conflicts flag in the mfd cells.

    Tested-by: Andreas Werner <email address hidden>
    Signed-off-by: Johannes Thumshirn <email address hidden>
    Signed-off-by: Lee Jones <email address hidden>

:040000 040000 e393ef7b37769bbe4001356fc2863f57c5ebba71 2e439cd11f370712886ec3fe9c72811a971c88b2 M drivers
"
I think Poulsbo driver is the one used for gma500 hardware in my laptop, so it makes sense.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Gonmotor, lastly could you please test for this in the latest mainline kernel via http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.17-rc7-utopic/ and advise to the results?

tags: added: bisect-done
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Gonmator (gonmator) wrote :

Tested. Still failing in the same way.

Thanks!

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
tags: added: kernel-bug-exists-upstream-3.17-rc7
Revision history for this message
penalvch (penalvch) wrote :

Gonmator, the issue you are reporting is an upstream one. Could you please report this problem through the appropriate channel by following the instructions _verbatim_ at https://wiki.ubuntu.com/Bugs/Upstream/kernel ?

Please provide a direct URL to your e-mail to the mailing list once you have made it so that it may be tracked.

Thank you for your understanding.

Changed in linux (Ubuntu):
status: Confirmed → Triaged
tags: removed: kernel-bug-exists-upstream-3.17-rc4
Revision history for this message
Gonmator (gonmator) wrote :

Re-tested in lastest latest mainline kernel (while preparing information to report following above indications) and still failing.
Tags updated.

tags: added: kernel-bug-exists-upstream-3.17
removed: kernel-bug-exists-upstream-3.17-rc7
Revision history for this message
Gonmator (gonmator) wrote :

Following the instructions, I couldn't identify any mailing list to send the bug report, so I email it to the maintainer of the presumable affected module who suggested me to report it to the Kernel Bug Tracker:

https://bugzilla.kernel.org/show_bug.cgi?id=86031

Revision history for this message
wavesailor (wavesailor) wrote :

Does anyone know if there are there any work arounds to solve this issue?

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.