| 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 1=
42997 [details]
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 x8=
6_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 appe=
ars
in either the kernel log when this happens, or in Xorg.0.log. I have attac=
hed
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 ca=
rd
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 th=
em,
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 cha=
nge
in behavior).
Given the change in hardware, it seems likely to me this is a driver bug ra=
ther
than a hardware one.
Created attachmen=
t 142998 [details]
Xorg.0.log without modesetting
Created attachment 142999=
[details]
dmesg with modesetting
Created attachment 143=
000 [details]
dmesg without modesetting
| What | Removed | Added |
|---|---|---|
| Attachment #142997 mime type | text/x-log | text/plain |
| What | Removed | Added |
|---|---|---|
| Attachment #142998 mime type | text/x-log | text/plain |
| What | Removed | Added |
|---|---|---|
| Attachment #142999 mime type | text/x-log | text/plain |
| What | Removed | Added |
|---|---|---|
| Attachment #143000 mime type | text/x-log | text/plain |
When you wrote "modesetting", you meant "DC&quo=
t;. 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?
(In reply to Michel D=C3=A4nzer from comment #4) > When you wrote "modesetting", you mean= t "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 dr= iver instead of > xf86-video-amdgpu, or with a Wayland compositor such as GNOME on Wayla= nd? I tried it with plasma Wayland and had the same exact problem.
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.
If you didn't say you tried swapping monitors and cables I'd s= ay 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=3D102646#c41 It would help us diagnose the issue.
Created attachment 143137 [= details] Xorg.0.log with modeset ddx instead of amdgpu ddx (In reply to Michel D=C3=A4nzer from comment #4) > Does it also happen with the Xorg modesetting dr= iver instead of > xf86-video-amdgpu, or with a Wayland compositor such as GNOME on Wayla= nd? Ok, I've tried both the modeset ddx (Xorg.0.log attached), as well as a Way= land compositor (plasma-wayland), and both exhibit exactly the same behavior. I = used kernel setting `amdgpu.dc=3D0` in both cases. Unfortunately, I can't try it= with `amdgpu.dc=3D1` due to issue https://bugs.freedesktop.org/show_bug.= cgi?id=3D109238.
(In reply to Harry Wentland from comment #7) > If you didn't say you tried swapping monitors an= d cables I'd say it was a > cable issue. >=20 > 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=3D102646#c41 It would help us > diagnose the issue. While I believe this was directed at Samuel Pitoiset (I don't have high ref= resh rate displays), I tried it anyway. Same problem occurs.
I don't think it's a cable issue because it works fine with NV= IDIA. echo manual > /sys/class/drm/card0/device/power_dpm_force_performance_le= vel echo "0" > /sys/class/drm/card0/device/pp_dpm_mclk Doing this doesn't fix the problem. Anything else?
FWIW, it's not a cable issue, I tried to replace it, same prob= lem. 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=20 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=3D0 on Polaris1= 0.
Actually, the problem happens with that new 4K screen too, lee= s frequently but still.
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.
Purchased a new Radeon RX590 (made by Asus instead of XFX) and= no longer have this issue.
| What | Removed | Added |
|---|---|---|
| Status | NEW | RESOLVED |
| Resolution | --- | MOVED |
-- 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.