Bug 1752188 - GPU driver failure on Raven Ridge Ryzen 3 2200G
Summary: GPU driver failure on Raven Ridge Ryzen 3 2200G
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 31
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-14 05:27 UTC by Subsentient
Modified: 2020-11-24 16:57 UTC (History)
18 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-24 16:57:33 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Backtrace from amdgpu module (8.86 KB, text/plain)
2019-09-14 05:27 UTC, Subsentient
no flags Details

Description Subsentient 2019-09-14 05:27:48 UTC
Created attachment 1615083 [details]
Backtrace from amdgpu module

I get the attached backtrace on kernels 5.2.0 and above with my Ryzen 3 2200G's integrated GPU. Motherboard is MSI B450M Gaming Plus.

Lightdm starts properly, but upon login, the screen flickers and goes permanently black. The keyboard/numlock lights become unresponsive for a few moments, suggesting the kernel's busy.

Comment 1 Justin M. Forbes 2020-03-03 16:26:03 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There are a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 30 kernel bugs.

Fedora 30 has now been rebased to 5.5.7-100.fc30.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 31, and are still experiencing this issue, please change the version to Fedora 31.

If you experience different issues, please open a new bug report for those.

Comment 2 Subsentient 2020-03-24 05:31:07 UTC
This bug is not resolved in Fedora 31 and is present in the latest kernels.

Comment 3 Ben Cotton 2020-11-03 16:53:05 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 4 Ben Cotton 2020-11-24 16:57:33 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.