Black Screen After A Few Minutes

[jonas]

Edit 1:
- added "installing mainline linux kernel v4.3.6-wily/" to things I tried

I first encountered the issue on Kubuntu 18.04 when I removed my 2nd monitor, the screen went black after 5-30 seconds, forcing me to shutdown the PC by pressing the power button. I tried the following to resolve the black screen issue:
- disconnecting the 1st instead of the 2nd monitor
- using Ubuntu 18.04 (not Kubuntu)
- using Wayland
- installing the latest mainline linux kernel 4.19rc4
- installing mainline linux kernel v4.3.6-wily/

The only things that worked so far are:
- Having both Monitors connected
- nomodeset or recovery mode
- using Ubuntu Gnome 16.04
- login via tty/terminal

When the PC was turned off for a while, I have to wait for a few minutes or start lots of applications for the black screen to occur. If the PC was restarted several times due to this bug, a blank screen may occur as soon as I see the login screen.
The issue also occurs during installation when autodetecting the keyboard type or after selecting the installation type (Minimal Installation or Normal Installation etc.)

My Hardware:
- ASRock H87 Pro4
- Intel i5-4570
- AMD Radeon R9 390
- 1st Monitor connected via DisplayPort to HDMI adapter cable (or DVI-D)
- 2nd Monitor connected via DVI-D cable
- Windows 10 is installed on a separate SSD and is working just fine (Although Windows 10 is doing some kind of boot repair when switching from Ubuntu to Windows)

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-29-generic 4.15.0-29.31
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ubuntu 2031 F.... pulseaudio
 /dev/snd/controlC1: ubuntu 2031 F.... pulseaudio
CasperVersion: 1.394
CurrentDesktop: ubuntu:GNOME
Date: Sun Sep 23 06:03:27 2018
LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=C.UTF-8
 SHELL=/bin/bash
ProcFB:

ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- nomodeset keyboard-configuration/layoutcode=de
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-29-generic N/A
 linux-backports-modules-4.15.0-29-generic N/A
 linux-firmware 1.173.1
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/03/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P2.20
dmi.board.name: H87 Pro4
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.20:bd08/03/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH87Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

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.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'.

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.19-rc5

[jonas (alljonasneeds)]

Thank you for looking into this.

The issue still exists when using mainline kernel v4.19-rc5 or v4.3.6-wily.

I did not upgrade my Ubuntu installation. However the black screen occurs using the Ubuntu 18.04.1 live image, too. But the black screen did not occur using the latest Ubuntu 16.04 live image. With "live image" I am refering to "installation media" / "startup disk".

The only "upgrade" I did was removing my secondary display.

[jonas (alljonasneeds)]

I just did a reinstall using nomodeset. Afterwards I gathered some log files out of /var/log/ in the hopes that they may be of some help.

After the installation I booted up and logged into my fresh installation without nomodeset, which soon after resulted in a black screen. So I had to hold down the power button to shut down the PC. That was at about 10:26 in the logs.

After that I booted up with nomodeset and gathered the log files.

[jonas (alljonasneeds)]

A couple lines in kern.log stood out to me:

Oct 3 10:24:50 jonas-gnome-desktop kernel: [ 8.512815] kauditd_printk_skb: 12 callbacks suppressed
Oct 3 10:25:00 jonas-gnome-desktop kernel: [ 18.583233] kauditd_printk_skb: 67 callbacks suppressed
Oct 3 10:25:05 jonas-gnome-desktop kernel: [ 23.630424] kauditd_printk_skb: 62 callbacks suppressed
Oct 3 10:25:10 jonas-gnome-desktop kernel: [ 28.761586] kauditd_printk_skb: 66 callbacks suppressed
Oct 3 10:25:16 jonas-gnome-desktop kernel: [ 34.908337] radeon_dp_aux_transfer_native: 494 callbacks suppressed
Oct 3 10:25:34 jonas-gnome-desktop kernel: [ 53.172346] radeon_dp_aux_transfer_native: 620 callbacks suppressed

I don't have much knowledge about the kernel, so these lines may be insignificant. But the last "callbacks suppressed" line is the last thing logged to kern.log before the logs begin where I started the PC with nomodeset.

[jonas (alljonasneeds)]

I found this ArchWiki page which has a section about my GPU: https://wiki.archlinux.org/index.php/AMDGPU#R9_390_series_Poor_Performance_and.2For_Instability
After setting "radeon.cik_support=0 amdgpu.cik_support=1 amdgpu.dpm=1 amdgpu.dc=1" as kernel parameters, I did not get a black screen (yet).
So it seems, I am having the same issue as in this bug report: https://bugs.freedesktop.org/show_bug.cgi?id=91880

[Logan Keating (besselfunct)]

I created an account to chime in here and say I'm having basically the exact same issue. I can't boot into the live USB without setting a nomodeset flag. I can then install, but I can't boot into the actual OS without setting nomodeset. I've tried several workarounds, but nothing has been successful.