Created attachment 1172736 [details] Journalctl of the affected boot. Description of problem: While playing Payday 2 and Team Fortress 2, I had several moments where the entire system seemed to lock up. This would be categorized by the video output freezing on a single frame, the audio stuttering over the last 1 second or so of audio in a loop, and no input of any kind being accepted. This would occur for 10 seconds or so, then the monitor would go black, declare no video input, then snap back on and the game would continue. This happened repeatedly, usually every few minutes. Eventually, one of the lockups did not have an automatic recovery and I was forced to shutoff the power to the system. GPU is a Sapphire TRI-X R9 290. Journal output for the last boot is attached, just 'ctrl-f radeon' and you'll find the entries. This has happened before on other games, so it is not limited to only those two. Any suggestions for debugging or workarounds would be appreciated. Version-Release number of selected component (if applicable): Kernel: 4.5.7 Mesa: 11.2.2 LLVM: 3.8.0 Additional info: The lockups did not begin immediately. I was able to play for an hour or so before I started to get hit by them, though after the second one they did seem to get progressively more frequent.
Can confirm problem persists on 4.7rc4 (rawhide-nodebug). Appears this might be application specific, though, because I didn't get hit by it in Civ5, Beyond Earth, or Fallout: New Vegas / Skyrim (Crossover). Definitely persists with Team Fortress 2, however.
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 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 '24'. 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 24 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 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.