https://bugs.freedesktop.org/show_bug.cgi?id=109239
Bug ID: 109239 Summary: Polaris10: Periodic random black screens for 1-2 seconds Product: DRI Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel@lists.freedesktop.org Reporter: rocketraman@gmail.com
Created attachment 142997 --> https://bugs.freedesktop.org/attachment.cgi?id=142997&action=edit Xorg.0.log with modesetting
I have 3 Dell WQHD Screens (2560x1440) screens, connected to a Radeon RX580 (XFX, RX-580 GTS Black Edition, 1425 MHz 8GB), running on Fedora 29.
My kernel is:
Linux edison 4.19.13-300.fc29.x86_64 #1 SMP Sat Dec 29 22:54:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
On 2/3 monitors I get periodic random black screens for 1-2 seconds. The display comes back and all appears normal after this happens.
I have tried both with and without modesetting enabled. Nothing at all appears in either the kernel log when this happens, or in Xorg.0.log. I have attached complete Xorg.0.log's and the relevant parts of dmesg (from boot to the very last drm-related message).
I was sure this was a hardware issue, and after a debugging process with XFX support in which they had me swapping monitors and cables, they RMAed my card and sent me a new one. However, the new card has very similar behavior (the old card seemed to black screen only one monitor, the new seems to do two of them, but in exactly the same way, and I have also updated my kernel and OS since then, so its possible the hardware is completely unrelated to the minor change in behavior).
Given the change in hardware, it seems likely to me this is a driver bug rather than a hardware one.
https://bugs.freedesktop.org/show_bug.cgi?id=109239
--- Comment #1 from Raman Gupta rocketraman@gmail.com --- Created attachment 142998 --> https://bugs.freedesktop.org/attachment.cgi?id=142998&action=edit Xorg.0.log without modesetting
https://bugs.freedesktop.org/show_bug.cgi?id=109239
--- Comment #2 from Raman Gupta rocketraman@gmail.com --- Created attachment 142999 --> https://bugs.freedesktop.org/attachment.cgi?id=142999&action=edit dmesg with modesetting
https://bugs.freedesktop.org/show_bug.cgi?id=109239
--- Comment #3 from Raman Gupta rocketraman@gmail.com --- Created attachment 143000 --> https://bugs.freedesktop.org/attachment.cgi?id=143000&action=edit dmesg without modesetting
https://bugs.freedesktop.org/show_bug.cgi?id=109239
Michel Dänzer michel@daenzer.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #142997|text/x-log |text/plain mime type| |
https://bugs.freedesktop.org/show_bug.cgi?id=109239
Michel Dänzer michel@daenzer.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #142998|text/x-log |text/plain mime type| |
https://bugs.freedesktop.org/show_bug.cgi?id=109239
Michel Dänzer michel@daenzer.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #142999|text/x-log |text/plain mime type| |
https://bugs.freedesktop.org/show_bug.cgi?id=109239
Michel Dänzer michel@daenzer.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #143000|text/x-log |text/plain mime type| |
https://bugs.freedesktop.org/show_bug.cgi?id=109239
--- Comment #4 from Michel Dänzer michel@daenzer.net --- When you wrote "modesetting", you meant "DC". So the problem is the same with or without DC?
Does it also happen with the Xorg modesetting driver instead of xf86-video-amdgpu, or with a Wayland compositor such as GNOME on Wayland?
https://bugs.freedesktop.org/show_bug.cgi?id=109239
--- Comment #5 from Raman Gupta rocketraman@gmail.com --- (In reply to Michel Dänzer from comment #4)
When you wrote "modesetting", you meant "DC". So the problem is the same with or without DC?
Yes, DC does not make a difference.
Does it also happen with the Xorg modesetting driver instead of xf86-video-amdgpu, or with a Wayland compositor such as GNOME on Wayland?
I tried it with plasma Wayland and had the same exact problem.
https://bugs.freedesktop.org/show_bug.cgi?id=109239
--- Comment #6 from Samuel Pitoiset samuel.pitoiset@gmail.com --- FWIW, I have the same issue on both Polaris/Vega. Disabling DC on Polaris appears to fix the problem on my side. Also, those periodic random black screens seem to only happen with my 4K screen, I don't have this problem at 1080p.
Let me know if you need more info.
https://bugs.freedesktop.org/show_bug.cgi?id=109239
--- Comment #7 from Harry Wentland harry.wentland@amd.com --- If you didn't say you tried swapping monitors and cables I'd say it was a cable issue.
Are those high refresh rate displays (120Hz+)? If so you might want to give what's suggested in this comment a try: https://bugs.freedesktop.org/show_bug.cgi?id=102646#c41 It would help us diagnose the issue.
https://bugs.freedesktop.org/show_bug.cgi?id=109239
--- Comment #8 from Raman Gupta rocketraman@gmail.com --- Created attachment 143137 --> https://bugs.freedesktop.org/attachment.cgi?id=143137&action=edit Xorg.0.log with modeset ddx instead of amdgpu ddx
(In reply to Michel Dänzer from comment #4)
Does it also happen with the Xorg modesetting driver instead of xf86-video-amdgpu, or with a Wayland compositor such as GNOME on Wayland?
Ok, I've tried both the modeset ddx (Xorg.0.log attached), as well as a Wayland compositor (plasma-wayland), and both exhibit exactly the same behavior. I used kernel setting `amdgpu.dc=0` in both cases. Unfortunately, I can't try it with `amdgpu.dc=1` due to issue https://bugs.freedesktop.org/show_bug.cgi?id=109238.
https://bugs.freedesktop.org/show_bug.cgi?id=109239
--- Comment #9 from Raman Gupta rocketraman@gmail.com --- (In reply to Harry Wentland from comment #7)
If you didn't say you tried swapping monitors and cables I'd say it was a cable issue.
Are those high refresh rate displays (120Hz+)? If so you might want to give what's suggested in this comment a try: https://bugs.freedesktop.org/show_bug.cgi?id=102646#c41 It would help us diagnose the issue.
While I believe this was directed at Samuel Pitoiset (I don't have high refresh rate displays), I tried it anyway. Same problem occurs.
https://bugs.freedesktop.org/show_bug.cgi?id=109239
--- Comment #10 from Samuel Pitoiset samuel.pitoiset@gmail.com --- I don't think it's a cable issue because it works fine with NVIDIA.
echo manual > /sys/class/drm/card0/device/power_dpm_force_performance_level echo "0" > /sys/class/drm/card0/device/pp_dpm_mclk
Doing this doesn't fix the problem.
Anything else?
https://bugs.freedesktop.org/show_bug.cgi?id=109239
--- Comment #11 from Samuel Pitoiset samuel.pitoiset@gmail.com --- FWIW, it's not a cable issue, I tried to replace it, same problem.
Though, after trying with a new 4K screen the problem is "fixed".
I assume it's a screen issue, I also tried to reset settings to default for the old screen but the problem still occurs.
Do you need more info about that screen?
Keep in mind that the problem doesn't happen with amdgpu.dc=0 on Polaris10.
https://bugs.freedesktop.org/show_bug.cgi?id=109239
--- Comment #12 from Samuel Pitoiset samuel.pitoiset@gmail.com --- Actually, the problem happens with that new 4K screen too, lees frequently but still.
https://bugs.freedesktop.org/show_bug.cgi?id=109239
--- Comment #13 from Raman Gupta rocketraman@gmail.com --- Still having this problem with newer software:
Linux edison 5.0.16-200.fc29.x86_64 #1 SMP Tue May 14 18:27:35 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
Mesa 18.3.6-3.fc29
It seems to happen more often when using Google Hangouts, with video turned on. However, it does not happen more often when watching YouTube videos.
https://bugs.freedesktop.org/show_bug.cgi?id=109239
--- Comment #14 from Raman Gupta rocketraman@gmail.com --- Purchased a new Radeon RX590 (made by Asus instead of XFX) and no longer have this issue.
https://bugs.freedesktop.org/show_bug.cgi?id=109239
Martin Peres martin.peres@free.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |MOVED
--- Comment #15 from Martin Peres martin.peres@free.fr --- -- 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/660.
dri-devel@lists.freedesktop.org
-
bugzilla-daemon＠freedesktop.org