Bug 1780949 - Amdgpu driver crasher in Fedora 31
Summary: Amdgpu driver crasher in Fedora 31
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-amdgpu
Version: 31
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Christopher Atherton
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-12-08 16:49 UTC by rrezh
Modified: 2020-11-24 15:23 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-24 15:23:02 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
journalctl logs (17.79 KB, text/plain)
2019-12-08 16:51 UTC, rrezh
no flags Details

Description rrezh 2019-12-08 16:49:58 UTC
Description of problem:
After doing a clean install of Fedora 31 XFCE spin a few days ago, I'm seeing amdgpu driver crashes occurring once or twice a day always in mild desktop usage scenarios such as browsing (I haven't seen a single crash while playing a game). 

After the crash, the desktop environment becomes either totally unresponsive or extremely slow and screen artifacts appears. Sometimes those same artifacts screen can be seen on alternatives virtual consoles sometimes not.

Before Fedora 31, I was using Fedora 29 XFCE spin for almost a year and I hadn't experience a single graphics related crash.

I'm using RX580 as my primary graphics card
2d:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] (rev e7) (prog-if 00 [VGA controller])
	Subsystem: ASUSTeK Computer Inc. Device 0519
	Flags: bus master, fast devsel, latency 0, IRQ 64
	Memory at e0000000 (64-bit, prefetchable) [size=256M]
	Memory at f0000000 (64-bit, prefetchable) [size=2M]
	I/O ports at f000 [size=256]
	Memory at f7a00000 (32-bit, non-prefetchable) [size=256K]
	Expansion ROM at 000c0000 [disabled] [size=128K]
	Capabilities: <access denied>
	Kernel driver in use: amdgpu
	Kernel modules: amdgpu

2d:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590]
	Subsystem: ASUSTeK Computer Inc. Device aaf0
	Flags: bus master, fast devsel, latency 0, IRQ 67
	Memory at f7a60000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: <access denied>
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel

I also have NVIDIA 1070ti to be used for VMs for GPU passthrough but I haven't configured any virtual machine since reinstall so right now it's just sitting there idly
2e:00.0 VGA compatible controller: NVIDIA Corporation GP104 [GeForce GTX 1070 Ti] (rev a1) (prog-if 00 [VGA controller])
	Subsystem: ASUSTeK Computer Inc. Device 861e
	Flags: bus master, fast devsel, latency 0, IRQ 62
	Memory at f6000000 (32-bit, non-prefetchable) [size=16M]
	Memory at c0000000 (64-bit, prefetchable) [size=256M]
	Memory at d0000000 (64-bit, prefetchable) [size=32M]
	I/O ports at e000 [size=128]
	Expansion ROM at f7000000 [disabled] [size=512K]
	Capabilities: <access denied>
	Kernel driver in use: nouveau
	Kernel modules: nouveau

2e:00.1 Audio device: NVIDIA Corporation GP104 High Definition Audio Controller (rev a1)
	Subsystem: ASUSTeK Computer Inc. Device 861e
	Flags: bus master, fast devsel, latency 0, IRQ 68
	Memory at f7080000 (32-bit, non-prefetchable) [size=16K]
	Capabilities: <access denied>
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel


Version-Release number of selected component (if applicable):
kernel: 5.3.14-300.fc31.x86_64

xorg-x11-drv-amdgpu.x86_64: 19.1.0-1.fc31

mesa-dri-drivers.x86_64: 19.2.6-1.fc31
mesa-filesystem.x86_64: 19.2.6-1.fc31
mesa-libEGL.x86_64: 19.2.6-1.fc31
mesa-libGL.x86_64: 19.2.6-1.fc31
mesa-libGLU.x86_64: 9.0.1-1.fc31
mesa-libOSMesa.x86_64: 9.2.6-1.fc31
mesa-libOpenCL.x86_64: 19.2.6-1.fc31
mesa-libgbm.x86_64: 19.2.6-1.fc31
mesa-libglapi.x86_64: 19.2.6-1.fc31
mesa-libxatracker.x86_64: 19.2.6-1.fc31
mesa-vulkan-drivers.x86_64: 19.2.6-1.fc31

Each crash has a slightly different messages logged in journalctl, the logs from last two crashes are in attachment

Comment 1 rrezh 2019-12-08 16:51:13 UTC
Created attachment 1643052 [details]
journalctl logs

Comment 2 rrezh 2019-12-14 13:25:44 UTC
The bug persists after following updates

[username@hostname ~]$ uname -r
5.3.15-300.fc31.x86_64


[username@hostname ~]$ dnf list '*mesa*' --installed
Installed Packages
mesa-dri-drivers.x86_64                                                                          19.2.7-1.fc31                                                                        @updates
mesa-filesystem.x86_64                                                                           19.2.7-1.fc31                                                                        @updates
mesa-libEGL.x86_64                                                                               19.2.7-1.fc31                                                                        @updates
mesa-libGL.x86_64                                                                                19.2.7-1.fc31                                                                        @updates
mesa-libGLU.x86_64                                                                               9.0.1-1.fc31                                                                         @fedora 
mesa-libOSMesa.x86_64                                                                            19.2.7-1.fc31                                                                        @updates
mesa-libOpenCL.x86_64                                                                            19.2.7-1.fc31                                                                        @updates
mesa-libgbm.x86_64                                                                               19.2.7-1.fc31                                                                        @updates
mesa-libglapi.x86_64                                                                             19.2.7-1.fc31                                                                        @updates
mesa-libxatracker.x86_64                                                                         19.2.7-1.fc31                                                                        @updates
mesa-vulkan-drivers.x86_64                                                                       19.2.7-1.fc31                                                                        @updates

Comment 3 rrezh 2019-12-14 13:31:13 UTC
Also, 

[username@hostname ~]$ dnf list '*drm*' --installed
Installed Packages
libdrm.x86_64                                                                             2.4.100-1.fc31                                                                              @updates

Comment 4 Ben Cotton 2020-11-03 15:57:52 UTC
This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '31'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 31 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 5 Ben Cotton 2020-11-24 15:23:02 UTC
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.