Ubuntu 18.10 After Blank Screen System Won't Come Back (amdgpu kernel crash?)

[Ryan]

In Ubuntu 18.10 if the blank screen feature initiates (5 minutes default) the system will remain blank and there is no way to get the display back on without a hard reset. The video card I am using is a Vega 64. Other users who have Vega AMD GPU's are experiencing the same issue. This is only happening in Ubuntu 18.10. Does not occur in my Arch or Fedora installs.

To reproduce:
- Let 'Blank Screen' feature execute (5 min default)
- Screen will not come back

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: xorg 1:7.7+19ubuntu8
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 25 10:18:59 2018
DistUpgraded: Fresh install
DistroCodename: cosmic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XT [Radeon RX Vega 64] [1002:687f] (rev c1) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Vega 10 XT [Radeon RX Vega 64] [1043:04c4]
InstallationDate: Installed on 2018-10-19 (6 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
MachineType: Micro-Star International Co., Ltd. MS-7B78
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=21c08187-f134-41b4-b8e5-93bead748c4f ro quiet splash
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/24/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2.20
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: X470 GAMING PRO CARBON (MS-7B78)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.20:bd04/24/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B78:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnX470GAMINGPROCARBON(MS-7B78):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7B78
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

[Niels Roetert (nroetert)]

Similar to #1799965

[Cristian Aravena Romero (caravena)]

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

[Daniel van Vugt (vanvugt)]

Please reproduce the problem, do a hard reset and then run this command:

  journalctl -b-1 > prev_boot.txt

and send us the resulting file prev_boot.txt

[Niels Roetert (nroetert)]

Attached the output as requested by Daniel van Vugt.

[Daniel van Vugt (vanvugt)]

Thanks. That seems to show the 'amdgpu' kernel module crashing at the end so it sounds like a kernel bug.

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

This change was made by a bot.

[Ryan (dasgeek)]

Adding my output with the same issue in case it helps in investigation.
Attached the output as requested by Daniel van Vugt.

[Daniel van Vugt (vanvugt)]

It looks like you both indeed are hitting the same kernel crash in 'amdgpu'.

[Lawrence Houston (lhoust)]

Similar problem with my Toshiba Satellite C650 (embedded Intel HD Graphics 3000) running Xubuntu 18.10. Once the Screen has Blanked, it will not unblank with normal Keystrokes and Mouse Events. My "Work around": Plugging an External Monitor into the Satellite C650's VGA Port, which will unblank the Toshiba's Screen!!!

NOTE: Even with Xfce Power Manager disabled the problem exists and therefore I do not know were other power management is being controlled?

[Daniel van Vugt (vanvugt)]

Lawrence,

Please log your own bug by running:

  ubuntu-bug linux

This bug is about an AMD graphics crash.

[d3b null (d3b-null)]

Sorry for the noise but, I am having the very same problem with an nvidia card. I am posting this here because it seems that this problem affecting AMD, intel an nvidia cards since the 18.10 update, so maybe this should be inspected as a general graphics bug, not just a bug in AMD. If that is not the case, my apologies for adding a bit of noise.

In my case, I am seeing this error:

Xan 30 12:43:54 boi kernel: nvidia-modeset: ERROR: GPU:0: Failed detecting connected display devices

I will try disabling modeset in nvidia