Created attachment 1474125 [details] stack trace found in kernel log that coincides with an episode Description of problem: Since updating to 4.17 I started to notice that my workstation would hang from time to time (input wouldn't be registered). I also noticed stack traces from amdgpu being printed during shutdown (but too quickly to read). I figured it was amdgpu misbehaving at that point and suspected some behavior change between 4.16 and 4.17, which eventually lead me to the amdgpu.dc=0 setting which seems to stop the issue from occurring. Version-Release number of selected component (if applicable): 4.17.2 or so was the first I updated to that I noticed this behavior and it persists into at least 4.17.9 How reproducible: Very. Stack traces also display during shut down, around when I think it switches display modes right before powering off. Steps to Reproduce: 1. boot without admgpu.dc=0 (amdgpu.dc=1 is the default as I understand it in 4.17) 2. open up a few browser windows/terminals use computer as normal, notice display unresponsiveness. Actual results: Periodic unresponsive graphical environment Expected results: Consistently responsive graphical environment Additional info: Possibly related to https://bugzilla.redhat.com/show_bug.cgi?id=1594488
the gpu in question: 04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Bonaire [FirePro W5100] 04:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Tobago HDMI Audio [Radeon R7 360 / R9 360 OEM]
still present in 4.17.12
still present in 4.17.14
still present in 4.17.17
still present in 4.17.19
still present in 4.18.5
I'm testing on a "Bonaire" AMD GPU on Fedora 29 Workstation and Silverblue - "Bonaire" is a "Sea Islands" card. I'm running into slow display with Fedora 29 Workstation and no display at all on Silverblue 29. I suspect this is the issue - will verify shortly. I can capture logfiles if it will help.
can confirm it's still an issue for me with 4.19.3-300 on Fedora 29. Switching to a virtual terminal also results in a completely blank screen now with dc=1
Been testing with 5.0.5 and I've not had the issue reoccur yet.
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 '28'. 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 28 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.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.