Created attachment 139789 [details] dmesg While watching a youtube video the screen froze but the youtube audio continued for a while. The box was reachable via ssh. No restart of xorg did fix the situation.
Created attachment 139790 [details] messages no xorg log messages for this one
Created attachment 139863 [details] dmesg Another hang. Was reading slashdot,
messages file has similar messages.
Created attachment 139864 [details] xorg log
Also happens on 4.17-rc7.
These issues happen multiple times per day. Not when I am away, but when I am using the PC. Thus making the system unusable due to unreliability.
Also when no video activity is going on, thus bug can happen.
video as in youtube, vlc, xine, etc.
This bug also happens in amd-staging-drm-next kernel of 02-jun-2018.
Created attachment 139982 [details] dmesg
The symptoms you describe sound very much the same as the ones I experience - I reported them in https://bugs.freedesktop.org/show_bug.cgi?id=102322
Per https://bugs.freedesktop.org/show_bug.cgi?id=105251#c9 , make sure you have current microcode and LLVM
Thanks. For my Ryzen 5 2400g that means all vega* files from https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amdgpu ? LLVM is at 6.0.0, it it the fedora 28 llvm. I should switch to git llvm? (again)
(In reply to udo from comment #13) > For my Ryzen 5 2400g that means all vega* files from > https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/ > tree/amdgpu ? Mostly the raven* ones, but it doesn't hurt to grab the vega* ones as well, or indeed all of them. > LLVM is at 6.0.0, it it the fedora 28 llvm. > I should switch to git llvm? (again) The referenced comment says 6.0.0 is fine. YMMV.
Only the file from this commit https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/amdgpu/vega10_vce.bin?id=1fa9ce33895f3634398a360715331cc222d243d6 was different from the Fedora rpm linux-firmware-20180525-85.git7518922b.fc28.noarch. I'll test with 4.16.14.
Hi everyone, I have the same issue with 2400g, and I believe I have found a way to reproduce it. Please try the following apitrace of a game called Deadly Premonition [1]. Just decompress it (it's almost 1.5 GB) and run it with 32-bit version of apitrace: apitrace replay deadly_premonition.trace Please let me know if it works. [1] https://mega.nz/#!O3JSCbZI!TEYmOxpvjCosO3AhW1kvdcxdMCEkpqNTxrl9tWdDVYE
Latest firmwares do influence the situation in a positive way.
I think that, with two times 3 days of amdgpu-problem free uptime, we can say that updates firmwares do fix this issue.
Ok then let's mark this as resolved for now.
Created attachment 140158 [details] dmesg w/mesa 18.0.2-1.fc28 I am still suffering from this issue, even with latest firmware from comment 15. Kernel: 4.16.14-300.fc28.x86_64 Mesa: tested both 18.0.2-1.fc28 (current Fedora release) and 18.2.0-0.11.git41dabdc.fc28 (from che/mesa copr repo). Bug occurred on both. Firmware: 20180525-85.git7518922b.fc28 (current Fedora release), but with vega10_vce.bin from comment 15 replacing the one installed by the package. My graphics card is a PowerColor RX Vega 64. I am attaching two dmesgs: one with each mentioned tested Mesa version.
Created attachment 140159 [details] dmesg w/mesa 18.2.0-0.11.git41dabdc.fc28
(In reply to sam.psylo from comment #20) > I am still suffering from this issue, even with latest firmware from comment > 15. Please file your own report. This report is resolved. > Firmware: 20180525-85.git7518922b.fc28 (current Fedora release), but with > vega10_vce.bin from comment 15 replacing the one installed by the package. Did you double-check that's the only file which differs from the ones you have?
(In reply to Michel Dänzer from comment #22) > (In reply to sam.psylo from comment #20) > > I am still suffering from this issue, even with latest firmware from comment > > 15. > > Please file your own report. This report is resolved. Will do. Sorry about that. > > Firmware: 20180525-85.git7518922b.fc28 (current Fedora release), but with > > vega10_vce.bin from comment 15 replacing the one installed by the package. > > Did you double-check that's the only file which differs from the ones you > have? Not directly, but I did take a look at the linux-firmware git history and that was the only firmware changed after May 25 (the date that the fedora package was based on). I'll make a new report for the bug, and continue there.
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.