Kernel 4.10+ regression: blackscreen when trying to resume from suspend

Bug #1676918 reported by Daniel Holz on 2017-03-28
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-power-manager (Ubuntu)
Undecided
Unassigned
linux (Ubuntu)
Medium
Unassigned
systemd (Ubuntu)
Undecided
Unassigned

Bug Description

When trying to resume after suspending my Lenovo Yoga 3 11, sometimes the screen remains black. The power LED switches from blinking to continuous light like it should but nothing else happens. The system does not react to anything. I tried to find something in the logs, but at least kern.log syslog and xorg.log never have any entries from this event.

This problem appeared with Ubuntu 16.04 and 17.04 with Xorg and Wayland.

I'm currently testing Kernel 4.8 from the mainline ppa because of this other suspend resume bug, that appeared only with 17.04:

https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1676912

Update: So far I did not encounter any issues with suspend/resume with Kernel 4.8 and 4.9. This seems to be a regression in 4.10.

---
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
DistroRelease: Ubuntu 17.04
InstallationDate: Installed on 2017-03-24 (4 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
Package: systemd 232-19
PackageArchitecture: amd64
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
Tags: zesty wayland-session
Uname: Linux 4.8.17-040817-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1676918/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
affects: ubuntu → linux (Ubuntu)

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

apport-collect 1676918

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.

Changed in linux (Ubuntu):
status: New → Incomplete

apport information

tags: added: apport-collected wayland-session zesty
description: updated

apport information

description: updated

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

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/v4.11-rc4

Changed in linux (Ubuntu):
importance: Undecided → Medium
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
status: Confirmed → Incomplete
Daniel Holz (daniel-holz91) wrote :

Trying Kernel 4.11 since yesterday. So far no blackscreens but I think I should test it for a longer duration. Unfortunately Kernel 4.11 is no real solution for me because of another suspend/resume bug that as far as I can tell at the moment might exist since Kernel 4.9.

Daniel Holz (daniel-holz91) wrote :

Got a blackscreen with Kernel 4.11. Unfortunately kern.log and syslog don't have any entries about it.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
summary: - blackscreen when trying to resume from suspend
+ Kernel 4.10+ regression: blackscreen when trying to resume from suspend
description: updated
dino99 (9d9) wrote :
Changed in systemd (Ubuntu):
status: New → Invalid
Changed in linux (Ubuntu):
status: Confirmed → Invalid
Changed in gnome-power-manager (Ubuntu):
status: New → Invalid
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1676918

tags: added: iso-testing
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers