Failing to resume from suspend/standby

[olof]

Fails to resume from suspend/standby for an Acer Aspire E1-772G. When trying to resume there is a black blank screen with a white underscore in the top left corner.

This worked in 13.10 but is broken in 14.04 and 14.10.

Suspend triggered by inactivity.
---
ApportVersion: 2.14.7-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: olof 2115 F.... pulseaudio
 /dev/snd/controlC0: olof 2115 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 14.10
HibernationDevice: RESUME=UUID=b6bc9763-31e8-4c3f-a81e-3f9fe461a134
InstallationDate: Installed on 2015-03-29 (3 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
MachineType: Acer Aspire E1-772G
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-33-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.16.0-33.44-generic 3.16.7-ckt7
RelatedPackageVersions:
 linux-restricted-modules-3.16.0-33-generic N/A
 linux-backports-modules-3.16.0-33-generic N/A
 linux-firmware 1.138.1
Tags: utopic
Uname: Linux 3.16.0-33-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 10/11/2013
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.00
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: EA70_HW
dmi.board.vendor: Acer
dmi.board.version: Type2 - Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.00:bd10/11/2013:svnAcer:pnAspireE1-772G:pvrV1.00:rvnAcer:rnEA70_HW:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: Aspire E1-772G
dmi.product.version: V1.00
dmi.sys.vendor: Acer

[olof (olof-baah)]

cat /proc/acpi/wakeup > wakeup

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1439418

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[olof (olof-baah)]

apport information

[olof (olof-baah)]

apport information

[olof (olof-baah)]

apport information

[olof (olof-baah)]

apport information

[olof (olof-baah)]

apport information

[olof (olof-baah)]

apport information

[olof (olof-baah)]

apport information

[olof (olof-baah)]

apport information

[olof (olof-baah)]

apport information

[olof (olof-baah)]

apport information

[olof (olof-baah)]

apport information

[olof (olof-baah)]

apport information

[olof (olof-baah)]

apport information

[olof (olof-baah)]

apport information

[olof (olof-baah)]

apport information

[olof (olof-baah)]

apport information

[olof (olof-baah)]

Hi

Updating the BIOS didn't change anything. Still blank black screen with a blinking underscore in upper right corner when resuming from standby.

olof@olof-Aspire-E1-772G:~$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
[sudo] password for olof:
V1.03
01/28/2014

[penalvch (penalvch)]

olof, could you please test the latest upstream kernel available from the very top line at the top of the page (the release names are irrelevant for testing, and please do not test the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue.

If the test did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to 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 by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-3.XY-rcZ

Where XY and Z are numbers corresponding to the kernel version.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-3.XY-rcZ

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.

[olof (olof-baah)]

Tested with 4.0.0-040000rc6. On resume it displays my desktop but then freezes (no reaction to mouse or keyboard). Hence the feature (resume from standby) doesn't work but should it be reported as another bug since the behavior is different?

[penalvch (penalvch)]

olof, could you please provide the missing information following https://wiki.ubuntu.com/DebuggingKernelSuspend ?

[olof (olof-baah)]

That is quite difficult for me since the keyboard doesn't work with 4.0.0-040000rc6 and I don't have a second computer with which I can ssh into my laptop. I might be able to borrow one later this week. Would the same information for kernel 3.16.0-33-generic (that's the version which I detected the error on) be of any use?

[penalvch (penalvch)]

olof, given the keyboard issue, would a slightly earlier version of the mainline kernel allow you use of the keyboard (ex. 4.0-rc5)?

[olof (olof-baah)]

I tried to follow the instructions at https://wiki.ubuntu.com/DebuggingKernelSuspend, section "resume-trace" debugging procedure for finding buggy drivers, for 4.0-rc5 but I'm not quite sure that it worked since I found only one "hash matches" in dmesg and the RTC seems ok. Attached anyway.

[penalvch (penalvch)]

olof, would 4.0-rc7 allow you use of your keyboard?

[olof (olof-baah)]

I tried to follow the instructions at https://wiki.ubuntu.com/DebuggingKernelSuspend, section "resume-trace" debugging procedure for finding buggy drivers, for 4.0-rc7 but I'm not quite sure that it worked since I found only one "hash matches" in dmesg and the RTC seems ok. Attached cat proc/apci/wakup and dmesg.txt anyway.

[olof (olof-baah)]

I'm sorry but this doesn't make sense to me.

According to https://wiki.ubuntu.com/SaucySalamander/ReleaseNotes the kernel version in 13.10 is 3.11. Resume works in this release.

According to https://wiki.ubuntu.com/TrustyTahr/ReleaseNotes the kernel version in 14.04 is 3.16. Resume does _not_ work in this release.

From that I would guess that one needs to bisect between kernel 3.11 & 3.16? Why between 3.11 and 3.13?

Anyway I tested with 3.13.11-03131111 and resume does work in that release. Wouldn't the next step be to check 3.14 or 3.15?

[penalvch (penalvch)]

olof:
>"I tested with 3.13.11-03131111 and resume does work in that release. Wouldn't the next step be to check 3.14 or 3.15?"

Yes.

[olof (olof-baah)]

It works in v3.14.39-utopic but is broken in 3.15-rc1-trusty.

[Launchpad Janitor (janitor)]

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