Bug 109239 - Polaris10: Periodic random black screens for 1-2 seconds
Summary: Polaris10: Periodic random black screens for 1-2 seconds
Status: NEW
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/AMDgpu (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-01-07 14:35 UTC by Raman Gupta
Modified: 2019-01-17 20:16 UTC (History)
3 users (show)

See Also:
i915 platform:
i915 features:


Attachments
Xorg.0.log with modesetting (49.04 KB, text/plain)
2019-01-07 14:35 UTC, Raman Gupta
no flags Details
Xorg.0.log without modesetting (65.01 KB, text/plain)
2019-01-07 14:35 UTC, Raman Gupta
no flags Details
dmesg with modesetting (113.69 KB, text/plain)
2019-01-07 14:36 UTC, Raman Gupta
no flags Details
dmesg without modesetting (113.92 KB, text/plain)
2019-01-07 14:36 UTC, Raman Gupta
no flags Details
Xorg.0.log with modeset ddx instead of amdgpu ddx (107.41 KB, text/plain)
2019-01-15 20:24 UTC, Raman Gupta
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Raman Gupta 2019-01-07 14:35:39 UTC
Created attachment 142997 [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 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.
Comment 1 Raman Gupta 2019-01-07 14:35:56 UTC
Created attachment 142998 [details]
Xorg.0.log without modesetting
Comment 2 Raman Gupta 2019-01-07 14:36:18 UTC
Created attachment 142999 [details]
dmesg with modesetting
Comment 3 Raman Gupta 2019-01-07 14:36:29 UTC
Created attachment 143000 [details]
dmesg without modesetting
Comment 4 Michel Dänzer 2019-01-07 17:29:51 UTC
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?
Comment 5 Raman Gupta 2019-01-08 20:05:03 UTC
(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.
Comment 6 Samuel Pitoiset 2019-01-15 09:41:29 UTC
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.
Comment 7 Harry Wentland 2019-01-15 12:47:10 UTC
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.
Comment 8 Raman Gupta 2019-01-15 20:24:17 UTC
Created attachment 143137 [details]
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.
Comment 9 Raman Gupta 2019-01-17 20:16:46 UTC
(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.


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.