Ubuntu 18.04 Video Crash on Suspend/Hibernate

Bug #1807264 reported by EDEMPCO
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

After updating to 18.04 when the system automatically suspends/hibernates after non-use, the screen goes black, but will not wake up by taping the space bar, nor does it display the hibernation screen. Additionally, I'm using two screens the laptop and an external monitor connected with the Mini Display port. When required to come out of suspend, each screen behaves differently. The laptop screen flashes while the external monitor may show any of these: 1) background screen image with no tool bars or menu; 2) remains black; or 3) shows a gray image. The only way to recover is to reboot, either by holding the power button or Ctrl-F1 to log back into the system and use the reboot command; only the external monitor will recover to a terminal screen.

Upgrading the kernel from 4.15 thru 4.19 does not change the suspend/hibernation issue. It seems to be video related issue, since HDMI port reacts differently than the Mini Display port, in that device settings do not operate the same and changing the settings can cause the same type of screen crash. Additionally, trying NVIDIA drivers will help with the suspend/hibernation problem and allows the hibernation screen to show, but is not a cure. Sometimes the NVIDIA drivers will allow it to come back from hibernation and sometimes not. My suspicion is that the drivers are not correct for the Intel video card.

I am also flummoxed by the fact that I cannot control suspend/hibernation. There is no obvious way to keep the system from suspending. Screen lock is OFF. Automatic suspend is OFF. Power button suspend is OFF. There needs to be more control; the ability to eliminate any and all suspend operations is a must! With this type of control, I could have kept if from suspending until a fix is generated.

Reports are as follows:

- lspci:
00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 09)
00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 09)
00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 09)
00:04.0 Signal processing controller: Intel Corporation Haswell-ULT Thermal Subsystem (rev 09)
00:14.0 USB controller: Intel Corporation 8 Series USB xHCI HC (rev 04)
00:16.0 Communication controller: Intel Corporation 8 Series HECI #0 (rev 04)
00:1b.0 Audio device: Intel Corporation 8 Series HD Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 1 (rev e4)
00:1c.3 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 4 (rev e4)
00:1d.0 USB controller: Intel Corporation 8 Series USB EHCI #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation 8 Series LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 8 Series SATA Controller 1 [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 8 Series SMBus Controller (rev 04)
00:1f.6 Signal processing controller: Intel Corporation 8 Series Thermal (rev 04)
02:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb)

- ubuntu-bug linux: Problem in linux-image-4.19.17-041907-generic cannot be reported, this report is about a package that is not installed

- cat /proc/version_signature > version.log: cat: /proc/version_signature: No such file or directory
- sudo lspci -vnvn > lspci-vnvn.log: (no response)

- lsb_release -rd: Ubuntu 18.04 LTS

- apt-cache policy pkgname: N: Unable to locate package pkgname

- sudo lshw -C display; uname -a; lsb_release -a; sudo dmidecode -t 1:
  *-display
       description: VGA compatible controller
       product: Haswell-ULT Integrated Graphics Controller
       vendor: Intel Corporation
       physical id: 2
       bus info: pci@0000:00:02.0
       version: 09
       width: 64 bits
       clock: 33MHz
       capabilities: msi pm vga_controller bus_master cap_list rom
       configuration: driver=i915 latency=0
       resources: irq:42 memory:f7800000-f7bfffff memory:e0000000-efffffff ioport:f000(size=64) memory:c0000-dffff
Linux tablet3 4.19.7-041907-generic #201812052010 SMP Wed Dec 5 20:11:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
LSB Version: core-9.20170808ubuntu1-noarch:printing-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch
Distributor ID: Ubuntu
Description: Ubuntu 18.04 LTS
Release: 18.04
Codename: bionic
---
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2014-10-31 (1497 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
Package: linux (not installed)
Tags: bionic
Uname: Linux 4.19.7-041907-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo video
_MarkForUpload: True

Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1807264

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
tags: added: bionic
Revision history for this message
EDEMPCO (edemco) wrote : ProcCpuinfoMinimal.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
EDEMPCO (edemco) wrote : ProcEnviron.txt

apport information

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

apport-collect 1807264: data was gathered and sent.

Revision history for this message
Charles Evans (crtiger) wrote :

Very similar to kubuntu 16.04.1 with kernel 4.4.0-41

Revision history for this message
EDEMPCO (edemco) wrote :

Can we start with a logical first step?
Is there a solution for preventing/eliminating hibernation?

Revision history for this message
EDEMPCO (edemco) wrote :

I've degraded the kernel from 4.19.8 back to 4.14.41. This was suggested by several people and for them, it fixed the problem. With the degraded kernel I am able to suspend, but not hibernate. If the computer is left unattended and hibernates, the same response is seen as described above.

Still not able to find a way to turn off suspend and hibernation permanently.

Revision history for this message
EDEMPCO (edemco) wrote :

I'm not getting any help, suggestions, hints, or anything with this problem. I't seems that I'm alone and the only one with this problem. So, if you are looking at this, there are no experts assisting, but I've been experimenting ...

If the computer goes into hibernation and any input device (keyboard, mouse, touch pad, etc) is manipulated, the video crashes. What this means is explained above, but to reiterate, the main screen flashes and noting can be done except to reboot. BUT, if the second screen is inplugged from either the screen port or the HMDI connector AND THEN the space bar is touched, the main screen recovers. After the main screen recovers, the second screen can be plugged in and the system is working.

I believe that if I could turn off hibernation completely, I would be free of the problem. All of the settings have been turned off and it still goes into hibernation!

Revision history for this message
EDEMPCO (edemco) wrote :

BTW: Two things: 1)inplugged is misspelled and should be unplugged; 2) I've been continuously upgrading the kernel, but still no fix. The kernel is now V4.20.7.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Please try mainline kernel.
Also, what's the last working kernel?

Revision history for this message
EDEMPCO (edemco) wrote :

You asked the same questions I did, but the answer doesn't help. 16.04 was the last version and it's kernel was 4.10.0.27.30. Going back, doesn't help. There is something in the 18.04 version that overrides the kernel. Read my responses above. I've used almost every kernel in between and currently, I'm using 5.0.10. I may jump to the most recent at this writing, 5.1.14, just to see what happens.

Brad Figg (brad-figg)
tags: added: cscc
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.