[Acer Aspire V5-573G] suspend/resume failure

Bug #1416557 reported by Valeriy Mironov
46
This bug affects 9 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Low
Unassigned

Bug Description

Black screen on resume after suspend

ProblemType: KernelOops
DistroRelease: Ubuntu 15.04
Package: linux-image-3.18.0-12-generic 3.18.0-12.13
ProcVersionSignature: Ubuntu 3.18.0-12.13-generic 3.18.4
Uname: Linux 3.18.0-12-generic x86_64
Annotation: This occured during a previous suspend and prevented it from resuming properly.
ApportVersion: 2.15.1-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: lightdm 1668 F.... pulseaudio
                      valeronm 2143 F.... pulseaudio
 /dev/snd/controlC0: lightdm 1668 F.... pulseaudio
                      valeronm 2143 F.... pulseaudio
Date: Fri Jan 30 23:39:37 2015
DuplicateSignature: suspend/resume:Acer Aspire V5-573G:V2.29
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=2b5c8acc-3a16-4e7f-97ba-5f4d5d564e7c
InstallationDate: Installed on 2015-01-30 (0 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150130)
InterpreterPath: /usr/bin/python3.4
MachineType: Acer Aspire V5-573G
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-12-generic.efi.signed root=UUID=eca5cdef-c2d4-4af6-a5e2-a11289cc9cfc 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.18.0-12-generic N/A
 linux-backports-modules-3.18.0-12-generic N/A
 linux-firmware 1.141
SourcePackage: linux
Title: [Acer Aspire V5-573G] suspend/resume failure
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 06/05/2014
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V2.29
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Dazzle_HW
dmi.board.vendor: Acer
dmi.board.version: Type2 - A01 Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.29:bd06/05/2014:svnAcer:pnAspireV5-573G:pvrTBDbyOEM:rvnAcer:rnDazzle_HW:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: Aspire V5-573G
dmi.product.version: TBD by OEM
dmi.sys.vendor: Acer

Revision history for this message
Valeriy Mironov (valeronm) 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 → Critical
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

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

Changed in linux (Ubuntu):
importance: Critical → Medium
status: Confirmed → Incomplete
tags: added: kernel-bug-exists-upstream
Revision history for this message
Valeriy Mironov (valeronm) wrote :
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a kernel version where you were not having this particular problem? This will help determine if the problem you are seeing is the result of a regression, and when this regression was introduced. If this is a regression, we can perform a kernel bisect to identify the commit that introduced the problem.

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org.

Once this bug is reported upstream, please add the tag: 'kernel-bug-reported-upstream'.

[0] https://wiki.ubuntu.com/Bugs/Upstream/kernel

Changed in linux (Ubuntu):
status: Incomplete → Triaged
Revision history for this message
Valeriy Mironov (valeronm) wrote :

Resume was works fine in 14.04 and doesn't work in 14.10. May you please describe how to do a kernel bisect?

penalvch (penalvch)
tags: added: bios-outdated-2.30 regression-release utopic
Changed in linux (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Valeriy Mironov (valeronm) wrote :

Thanks for notice about new BIOS.
I updated all OS packages and updated BIOS to 2.30 version.

There is output of 'sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date' command:
V2.30
01/12/2015

But resume after sleep still doesn't work.

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

Valeriy Mironov, could you please test for this via the latest mainline kernel (4.0-rc2) and advise to the results?

tags: added: latest-bios-2.30
removed: bios-outdated-2.30
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Valeriy Mironov (valeronm) wrote :

I checked kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0-rc2-vivid/
I have got black screen again on resume.

Revision history for this message
penalvch (penalvch) wrote :

Valeriy Mironov, the next step is to fully commit bisect from kernel 3.13 to 3.16 in order to identify the last good kernel commit, followed immediately by the first bad one. This will allow for a more expedited analysis of the root cause of your issue. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

Please note, finding adjacent kernel versions is not fully commit bisecting.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

tags: added: kernel-bug-exists-upstream-4.0-rc2 needs-bisect
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
Revision history for this message
bp0 (bullet-proof-0) wrote :

I've done a bit more narrowing down on this and found that the problem occurs between kernel 3.14.51 and kernel 3.15.0-RC1. I know this isn't kernel bisecting (haven't done this before so will give it a go but not sure whether I'll be successful).

Oddly, in Ubuntu 14.10, I can suspend/resume fine with kernel 3.16.0-38, but this doesn't work in 15.04. Odd.

Revision history for this message
bp0 (bullet-proof-0) wrote :

So I've comprehensively failed to git bisect what is apparently neither a mainline kernel version (mainline only has 3.14, not 3.14.51, and I can't figure out how to get around the lack of a debian.master/changelog file) nor available in the utopic repository (which has 3.13 and 3.16 kernels, but neither of the ones I'm interested in). I've also never built a kernel before so don't have enough baseline knowledge to go beyond copy and pasting commands which I don't really understand.

I suspect that the resume problem has something to do with the changes made in https://01.org/suspendresume/blogs/tebrandt/2013/hard-disk-resume-optimization-simpler-approach. These were made between 3.14.51 and 3.15.0-RC1, I think. Unfortunately, I have no idea how to revert just these patches to test them individually.

Any help appreciated.

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

bp0, it will help immensely if you filed a new report via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

Revision history for this message
Maxim Kizub (mkizub) wrote :
Revision history for this message
Maxim Kizub (mkizub) wrote :

A temp fix is to add acpi_osi="!Windows 2013" to boot kernel params.

Revision history for this message
Sandeep Kumar (sandeepkumar-india) wrote :

the temp fix by Maxim is working for me

Thanks a lot Maxim for suggestion!

I updated /etc/default/grup and added acpi_osi=\"!Windows 2013\" after the last parameter. Did an update-grub, rebooted and is working fine.

Revision history for this message
bp0 (bullet-proof-0) wrote :

The temp fix by Maxim is also working for me - hooray! Thanks so much Maxim!

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
Revision history for this message
bp0 (bullet-proof-0) wrote :

Just to add: I upgraded to 16.04 and I can no longer resume from suspend - everything is frozen. I tried removing the acpi_osi=\"!Windows 2013\" boot parameter and this causes ubuntu suspend, immediately resume, then freeze.

penalvch (penalvch)
Changed in linux (Ubuntu):
importance: Medium → Low
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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