TTY non-functional after Resume from Suspend

Bug #1577797 reported by Patrick Gillespie
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

After Resume from Suspend, TTY 1-6 is non-functional.

Sometimes I can see text but no prompt or cursor and no way to interact with the prompt.

Sometimes the screen is blank.

Reproducible: Always

Steps to reproduce:

1.) Suspend
2.) Resume
3.) CTRL+ALt+F1-6

Results:

Blank or non-functional screen.

System Information:

Kernel: 4.4.0-21-generic x86_64 (64 bit) Desktop: KDE Plasma 5.5.5
           Distro: Ubuntu 16.04 xenial
Machine: System: LENOVO (portable) product: 20428 v: Lenovo Yoga 2 11
           Mobo: LENOVO model: VIUU4 v: 31900058WIN Bios: LENOVO v: AACN21WW date: 01/30/2015
CPU: Dual core Intel Core i3-4012Y (-HT-MCP-) cache: 3072 KB
           clock speeds: max: 1500 MHz 1: 1500 MHz 2: 1499 MHz 3: 1500 MHz 4: 1500 MHz
Graphics: Card: Intel Device 0a1e
           Display Server: X.Org 1.18.3 drivers: intel (unloaded: fbdev,vesa) Resolution: 1366x768@60.00hz
           GLX Renderer: Mesa DRI Intel Haswell GLX Version: 3.0 Mesa 11.2.0

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

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/1577797/+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
tags: added: xenial
Revision history for this message
Patrick Gillespie (vermontpoet) wrote :

I may have discovered a work-around. I installed the Intel Graphics Linux Installer **for Ubuntu 15.10** onto 16.04 using the instructions found here:

https://allanbogh.com/2016/01/05/ubuntu-16-04-installing-the-intel-graphics-drivers-using-the-intel-graphics-installer-for-linux/

And here:

http://ubuntuhandbook.org/index.php/2015/11/install-intel-graphics-installer-in-ubuntu-15-10/

After several suspend and resumes, I haven't been able to reproduce the bug. During the course of normal usage, and if anything changes, I will add another note.

Revision history for this message
Patrick Gillespie (vermontpoet) wrote :

Scratch that last workaround.

After leaving the computer running, without suspend, for an hour or so and returning, the TTY's were no longer responsive.

Revision history for this message
Paul White (paulw2u) wrote :

According to https://wiki.ubuntu.com/Bugs/FindRightPackage#Suspend_and_Hibernate, refiling this report against the kernel is the way to go for now.

affects: ubuntu → linux (Ubuntu)
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

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

apport-collect 1577797

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
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 v4.7 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.7-rc6-yakkety/

Changed in linux (Ubuntu):
importance: Undecided → Medium
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
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.