Bug 110339

Summary:	Cursor hides and reappear in the middle of screen, when moving mouse horizontally
Product:	DRI	Reporter:	Pinky <j-pi>
Component:	DRM/AMDgpu	Assignee:	Default DRI bug account <dri-devel>
Status:	RESOLVED MOVED	QA Contact:
Severity:	normal
Priority:	medium	CC:	harry.wentland, nicholas.kazlauskas
Version:	DRI git
Hardware:	x86-64 (AMD64)
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:

Description Pinky 2019-04-05 17:39:33 UTC

Cursor gradually disappears and then reappears at once when moving mouse horizontally. This happends on vertical line exactly in the center of the screen. It creates impression there are 2 tiles on the screen, (left and right). When mouse moves to the right edge of the left tile it gradually "hides" under the one on the right side, when when the cursor is whole on the right tile it "pop ups" again at once.

This happends even on external monitor, where resolution is different, it still dissapears exactly in the center of the screen.

This does not happends when both monitors are used as outputs (orientation does not matter, they can be left, right, above, bellow of each other or even overlap). I did not find any horizontal line where the cursor "hides".

Also in some positions along the central line sometimes some artifacts appears, when the mouse is partialy hidden. They change when the mouse moves in any direction. But those are not always reproducible and in fact are rare.

I actually does not have an idea where the bug actually is (can be anywhere along the pipeline including kernel).

This is on Lenovo A485 notebook with Arch linux.

mesa 19.0.1
xf86-video-amdgpu-git-19.0.1.0

[lspci]
06:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] (rev d1)

Comment 1 Pinky 2019-04-05 17:41:52 UTC

kernel: Linux 5.1.0-rc2-1-next-git-g7cdd4dc58d28 #5 SMP Fri Apr 5 18:06:31 CEST 2019 x86_64 GNU/Linux

Comment 2 Nicholas Kazlauskas 2019-04-08 13:10:29 UTC

Thanks for the report, this is a kernel bug.

This was actually a regression caused from:

"drm/amd/display: PIP overlay corruption"

which was fixed by:

"drm/amd/display: Fix negative cursor pos programming"

...and has another fix for overlay specific cases 

"drm/amd/display: Prevent cursor hotspot overflow for RV overlay planes"

It actually looks like these 3 patches are in Linux next-git... but in the wrong order or not applied correctly, since there are still remnants of the first commit leftover that were removed by the second.

My guess is this was a bad patch autoselect, but I'll follow up with the maintainers to try and get this fixed.

FWIW, you shouldn't see this in amd-staging-drm-next.

Comment 3 Pinky 2019-04-08 16:53:03 UTC

* bugzilla-daemon@freedesktop.org <bugzilla-daemon@freedesktop.org> [2019-04-08 13:10:29 +0000]:

>https://bugs.freedesktop.org/show_bug.cgi?id=110339
>
>--- Comment #2 from Nicholas Kazlauskas <nicholas.kazlauskas@amd.com> ---
>Thanks for the report, this is a kernel bug.
>
>This was actually a regression caused from:
>
>"drm/amd/display: PIP overlay corruption"
>
>which was fixed by:
>
>"drm/amd/display: Fix negative cursor pos programming"
>
>...and has another fix for overlay specific cases
>
>"drm/amd/display: Prevent cursor hotspot overflow for RV overlay planes"
>
>It actually looks like these 3 patches are in Linux next-git... but in the
>wrong order or not applied correctly, since there are still remnants of the
>first commit leftover that were removed by the second.
>
>My guess is this was a bad patch autoselect, but I'll follow up with the
>maintainers to try and get this fixed.
>
>FWIW, you shouldn't see this in amd-staging-drm-next.

Yes, the bug does not manifest in this branch.

>
>-- 
>You are receiving this mail because:
>You reported the bug.

Comment 4 Martin Peres 2019-11-19 09:18:24 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/738.

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.