Bug 103317

Summary: Tearing in WQHD, but not in FHD
Product: DRI Reporter: Torsten Kessler <torkes94>
Component: DRM/AMDgpuAssignee: Default DRI bug account <dri-devel>
Status: RESOLVED MOVED QA Contact:
Severity: normal    
Priority: medium CC: harry.wentland, jordan.lazare
Version: unspecified   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
X server log
none
Dmesg output
none
Output of xrandr --verbose
none
Second Xorg log with EnablePageFlip turned off none

Description Torsten Kessler 2017-10-17 19:19:26 UTC
Created attachment 134888 [details]
X server log

Hi all,

I'm using Arch Linux with kernel 4.13.5-1-ARCH, Xorg 1.19.5 and the amdgpu driver, version 1.4. My GPU is a R9 390. I attached the X server log.
My window manager is i3.

Entries in xorg.conf.d:

20-amdgpu.conf

Section "Device"
	Identifier "AMD R9 390"
	Driver "amdgpu"
	Option "DRI" "3"
	Option "TearFree" "true"
EndSection

With this setup I experience screen tearing and flickering on a WQHD monitor.
Enabling a compositor like compton makes these effects worse.
I can reproduce this issue on the same machine with KDE instead of i3.
To give you an idea of my problem, I captured a scene from the RTS 0ad:

https://youtu.be/ZhjPpB7djyk

The same kind of flickering and tearing also happens in desktop mode. It seems to appear randomly.
However, the problem disappears when I'm using the radeonsi driver or changing the resolution to FHD. In both cases everything is fine.
Comment 1 Torsten Kessler 2017-10-17 19:20:11 UTC
Created attachment 134889 [details]
Dmesg output
Comment 2 Michel Dänzer 2017-10-18 13:54:45 UTC
Please attach the output of

 xrandr --verbose

while the problem occurs (i.e. while e.g. 0ad is running and showing flickering).

Does not enabling TearFree or

 Option "EnablePageFlip" "off"

avoid the problem?
Comment 3 Torsten Kessler 2017-10-18 17:03:36 UTC
Created attachment 134912 [details]
Output of xrandr --verbose

As suggested I turned EnablePageFlip off:

Section "Device"
	Identifier "AMD R9 390"
	Driver "amdgpu"
	Option "DRI" "3"
	Option "EnablePageFlip" "off"
#	Option "TearFree" "true"
EndSection

But this doesn't avoid the problem. As before, everything works fine when I switch to FHD or radeonsi.
Comment 4 Michel Dänzer 2017-10-19 08:56:38 UTC
(In reply to Torsten Kessler from comment #3)
> As suggested I turned EnablePageFlip off:
[...]
> But this doesn't avoid the problem.

Please attach the corresponding Xorg log file.


> As before, everything works fine when I switch to FHD or radeonsi.

You cannot "switch to radeonsi", I assume you mean when you use the radeon kernel driver instead of amdgpu. The Mesa radeonsi driver is used in both cases.

You might want to try a kernel built from the amd-staging-drm-next branch of https://cgit.freedesktop.org/~agd5f/linux/ with CONFIG_DRM_AMD_DC=y at build time and amdgpu.dc=1 at runtime, to see if that works better.
Comment 5 Torsten Kessler 2017-10-20 18:32:13 UTC
Created attachment 134943 [details]
Second Xorg log with EnablePageFlip turned off

You're right. I was mixing things up. I meant loading the radeon module and blacklisting the amdgpu module solves the issue.
I'm just downloading the kernel from the amd-staging-drm-next branch. I will see tomorow if it helps. Thank you for your help so far!
Comment 6 Torsten Kessler 2017-10-22 15:49:02 UTC
The new display engine (amdgpu.dc=1) definitely helps. It nearly eliminates the flickering during videos or browsing. It has no effect on 3D applications, for example 0ad.
There seems to be a bug in the amd-staging-drm-next branch. Rotating the screen with xrandr results in a blackscreen. But this will be a different bug report.
That's why I using the kernel from the amd-staging-4.13 branch with amdgpu.dc=1.
Comment 7 Michel Dänzer 2017-10-23 09:50:59 UTC
(In reply to Torsten Kessler from comment #6)
> The new display engine (amdgpu.dc=1) definitely helps. It nearly eliminates
> the flickering during videos or browsing. It has no effect on 3D
> applications, for example 0ad.

Adding DC developers to Cc. I'm afraid at this point it's unlikely that this issue will be fixed in the non-DC code.
Comment 8 Martin Peres 2019-11-19 08:24:54 UTC
-- 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/246.

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.