Hello there! I just installed my 5700 XT in my system, running Manjaro in testing branch with Mesa 19.2.1, 5.3.6-1-MANJARO and LLVM 9.0.0. Issue has appeared in native game The Witcher 1 and Space Engineers, in both these instances a few moments (in The Witcher 1 it once took a few minutes) the video freezes, while audio continues in the background. I cannot alt-tab or enter TTY, I am forced to force shutdown. I have not been able to reproduce the hang issue while playing YouTube or other normal tasks. I am not sure how to provide logs since this hangs my entire system and I am forced to shutdown, which journalctl filter do I use to provide useful information? Thank you, and sorry if I am not providing anything useful, it is my first time submitting a bug here.
(In reply to Daniel Suarez from comment #0) I was able to reproduce the issue with gfxbench, it hanged during the tessellation test at the beginning, I was still able to hear a YouTube video I had playing in the background.
Created attachment 145720 [details] Apitrace I think I was able to get an apitrace by doing DEBUGGER="apitrace trace" steam steam://rungameid/20920 > ApiTrace.txt For The Witcher 2 and Space Engineers respectably and then DEBUGGER="apitrace trace" gfxbench For Gfxbench, I include the results of these since I am able to recover them since they save after I am forced to shutdown my PC
Created attachment 145721 [details] Apitrace GFXBench
Created attachment 145722 [details] Apitrace The Witcher 2
Update: The same issue just occurred with just Firefox being opened Apologies for so many comments, if any additional information is needed please do not hesitate to ask
Created attachment 145728 [details] Xorg log I switched over to mesa-git (along with all the other packages recommended to accompany it mentioned in the Arch wiki) and the same exact issue occurs, this is the log found in "/var/log/Xorg.0.log.old", grabbed it right after booting in after having been forced to shutdown when my PC froze when running GFXBench
Thanks for your bug report. It would be really helpful to have the content of dmesg when your system hangs. You can get it from another computer using ssh or you could extract it from /var/log/dmesg* files after a reboot. You can also check some of the existing bugs and see if they are the same as yours: - https://bugs.freedesktop.org/show_bug.cgi?id=111986 - https://bugzilla.kernel.org/show_bug.cgi?id=205169
(In reply to Pierre-Eric Pelloux-Prayer from comment #7) > Thanks for your bug report. > > It would be really helpful to have the content of dmesg when your system > hangs. > You can get it from another computer using ssh or you could extract it from > /var/log/dmesg* files after a reboot. > > You can also check some of the existing bugs and see if they are the same as > yours: > - https://bugs.freedesktop.org/show_bug.cgi?id=111986 > - https://bugzilla.kernel.org/show_bug.cgi?id=205169 Thank you so much for taking the time to reply to my bug report, I really wanted to provide that but unfortunately it doesn't exist, I even did "ls -ls /var/log/" to make sure it wasn't dolphin hiding the file, but a dmesg file/folder doesn't exist. Closest thing I see is "Xorg.0.log.old" which I will attach just incase As for bug report 205169, I do not believe so since my system hangs regardless if a game or application is fullscreen or not.
Created attachment 145735 [details] Xorg log 2
Created attachment 145736 [details] Got by running sudo journalctl -b > dmesg.log Thanks to the explanation by someone I believe I understand now what you meant. I went ahead and reproduced the hang by running gfxbench and when the system hanged at around 3:23 I force shutdown seconds later, once I booted in I ran "sudo journalctl -b > dmesg.log" and I am sending you the output now
(In reply to Daniel Suarez from comment #10) > Created attachment 145736 [details] > Got by running sudo journalctl -b > dmesg.log > > Thanks to the explanation by someone I believe I understand now what you > meant. I went ahead and reproduced the hang by running gfxbench and when the > system hanged at around 3:23 I force shutdown seconds later, once I booted > in I ran "sudo journalctl -b > dmesg.log" and I am sending you the output now You need to use "sudo journalctl -b -1 > dmesg.log" to get the logs from the previous boot (= the one that hanged).
(In reply to Pierre-Eric Pelloux-Prayer from comment #11) > (In reply to Daniel Suarez from comment #10) > > Created attachment 145736 [details] > > Got by running sudo journalctl -b > dmesg.log > > > > Thanks to the explanation by someone I believe I understand now what you > > meant. I went ahead and reproduced the hang by running gfxbench and when the > > system hanged at around 3:23 I force shutdown seconds later, once I booted > > in I ran "sudo journalctl -b > dmesg.log" and I am sending you the output now > > You need to use "sudo journalctl -b -1 > dmesg.log" to get the logs from the > previous boot (= the one that hanged). I am deeply sorry, I attach the correct one now
Created attachment 145744 [details] Correct journalctl
The last lines of your log indicates a gfx hang. You can try to set the environment variable AMD_DEBUG to the "nongg" value to see if it helps. The apitrace you attached are the log output from apitrace, not the real trace. The trace should be next to the binary of the game (try to search for .trace file in $HOME/.steam/steam/steamapps/common).
I'm having the same issue on a 5700 (non-xt). It seems to be this bug: https://bugs.freedesktop.org/show_bug.cgi?id=111481#c9
(In reply to Sabbie from comment #15) > I'm having the same issue on a 5700 (non-xt). > > It seems to be this bug: > > https://bugs.freedesktop.org/show_bug.cgi?id=111481#c9 Yeah, apologies I have not provided the logs asked I've had a few hard days due to college entrance shit, but it's the exact same issue as the one listed in the bug report you linked, this is completely unacceptable from Amd honestly
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/935.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.