AMD RX 570 Black Screen at boot

Bug #1837945 reported by Surena Karimpour
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
xserver-xorg-video-amdgpu (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Ubuntu 19.04

Problem:
Booting from live media OR installed ubuntu fails with a blank, black screen and total system hang.

How to reproduce:
Using AMDGpu driver and AMD 4th Gen GCN GPU, try to boot Ubuntu 19.04 (or 18.04)

Resolution:
Manually updating kernel to 5.1 and adding the "amdgpu.dc=0" kernel boot parameter seems to fix the problem.

inxi -SGxxx Output:

System:
  Host: ---- Kernel: 5.1.0-050100-generic x86_64 bits: 64
  compiler: gcc v: 8.3.0 Desktop: Gnome 3.32.1 wm: gnome-shell
  dm: GDM3 3.32.0 Distro: Ubuntu 19.04 (Disco Dingo)
Graphics:
  Device-1: AMD Ellesmere [Radeon RX 470/480/570/570X/580/580X]
  driver: amdgpu v: kernel bus ID: 07:00.0 chip ID: 1002:67df
  Display: x11 server: X.Org 1.20.4 driver: ati,fbdev
  unloaded: modesetting,radeon,vesa compositor: gnome-shell
  resolution: 1920x1080~60Hz
  OpenGL: renderer: Radeon RX 570 Series (POLARIS10 DRM 3.30.0
  5.1.0-050100-generic LLVM 8.0.0)
  v: 4.5 Mesa 19.0.2 direct render: Yes
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
DistUpgraded: Fresh install
DistroCodename: disco
DistroRelease: Ubuntu 19.04
DistroVariant: ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1002:67df] (rev ef) (prog-if 00 [VGA controller])
   Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:0b31]
InstallationDate: Installed on 2019-07-26 (0 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: System manufacturer System Product Name
Package: xserver-xorg-video-amdgpu 19.0.1-1
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=d779e62a-1fa2-404f-97a3-5649f11998c2 ro quiet splash amdgpu.dc=0 vt.handoff=1
ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15
Tags: disco ubuntu
Uname: Linux 5.0.0-21-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 06/18/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5007
dmi.board.asset.tag: Default string
dmi.board.name: PRIME A320M-K
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5007:bd06/18/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

Revision history for this message
Tom Reynolds (tomreyn) wrote :

Please also test with the default 19.04 kernel (ideally the installer, too), can you get graphical output there using amdgpu.dc=0 ?

While running from the installed system, if possible using the default (after updates) kernel image, with amdgpu.dc=0 set, please run:
  apport collect-logs 1837945

Changed in xserver-xorg-video-amdgpu (Ubuntu):
status: New → Incomplete
Revision history for this message
Surena Karimpour (sudohalt) wrote :

I re-installed ubuntu 19.04 and the amdgpu.dc=0 fixed it in the installer, also I tested with the default kernel (latest update) and can confirm amdgpu.dc=0 works on default kernel as well, so it isnt related to the kernel version.

The apport command doesnt run, it returns a command not found error, but apport IS installed.

Revision history for this message
Tom Reynolds (tomreyn) wrote :

Apologies, the correct command is:
   apport-collect 1837945

Revision history for this message
Tom Reynolds (tomreyn) wrote :

Surena: After collecting logs, please continue and report this upstream where other amdgpu bugs have already been reported:
https://bugs.freedesktop.org/buglist.cgi?product=DRI&component=DRM%2FAMDgpu&list_id=676975&resolution=---
You can file a new bug at https://bugs.freedesktop.org/enter_bug.cgi against product "DRI", component "DRM/AMDgpu".

Ubuntu bug 1818580 is possibly related - the "[drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables amdgpu kernel modesetting." message was also observed here (according to details conveyed on #ubuntu IRC by user "sudo_halt" on 2019-07-25 - whom I assume is the same person as Surena Karimpour).

Revision history for this message
Surena Karimpour (sudohalt) wrote : CurrentDmesg.txt

apport information

tags: added: apport-collected disco ubuntu
description: updated
Revision history for this message
Surena Karimpour (sudohalt) wrote : Dependencies.txt

apport information

Revision history for this message
Surena Karimpour (sudohalt) wrote : DpkgLog.txt

apport information

Revision history for this message
Surena Karimpour (sudohalt) wrote : Lspci.txt

apport information

Revision history for this message
Surena Karimpour (sudohalt) wrote : Lsusb.txt

apport information

Revision history for this message
Surena Karimpour (sudohalt) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Surena Karimpour (sudohalt) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Surena Karimpour (sudohalt) wrote : ProcEnviron.txt

apport information

Revision history for this message
Surena Karimpour (sudohalt) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Surena Karimpour (sudohalt) wrote : ProcModules.txt

apport information

Revision history for this message
Surena Karimpour (sudohalt) wrote : UdevDb.txt

apport information

Revision history for this message
Surena Karimpour (sudohalt) wrote : XorgLog.txt

apport information

Revision history for this message
Surena Karimpour (sudohalt) wrote : XorgLogOld.txt

apport information

Revision history for this message
Surena Karimpour (sudohalt) wrote : Xrandr.txt

apport information

Revision history for this message
Surena Karimpour (sudohalt) wrote : xdpyinfo.txt

apport information

Revision history for this message
Surena Karimpour (sudohalt) wrote :

Sorry for late response:
Here is the command output:
Yes, i am sudo_halt!

This bug most definitely related to AMD's DC code, which i assume was updated in newer MESA versions. I will try to manually update MESA, and see if it will provide any resolution.

I ran the command you provided, and it uploaded the output to somewhere, not sure what happened.

Also, the other bugs are different: In this situation, AMDGpu's DC is the problem. Disabling it also means loss of any HDMI Audio functionality. I'll see to reporting this bug to freedesktop, if updating MESA doesn't help.

Revision history for this message
Surena Karimpour (sudohalt) wrote :

Updating MESA or Linux kernel does not solve the issue. I'll take this issue to AMD developers working on AMD DC support.

Tom Reynolds (tomreyn)
Changed in xserver-xorg-video-amdgpu (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Tom Reynolds (tomreyn) wrote :

Thanks for your feedback. Please post a link here to the upstream bug report once you filed it.

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.