Bug 99143

Summary:	r9 390: Hardware cursor invisible after hibernate/resume
Product:	DRI	Reporter:	Harald Judt <h.judt>
Component:	DRM/AMDgpu	Assignee:	Default DRI bug account <dri-devel>
Status:	RESOLVED MOVED	QA Contact:
Severity:	normal
Priority:	medium
Version:	XOrg git
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:

Description Harald Judt 2016-12-19 14:12:36 UTC

I have merged https://cgit.freedesktop.org/~agd5f/linux/log/?h=drm-next-4.10-wip into 4.9, as this solves the failures to hibernate/resume on my machine with the r9 390. The only problem with hibernation left now is that the HW cursor vanishes after hibernating and resuming. Widgets still get focused, only the cursor is no longer visible. Switching to software cursor as a workaround solves this.

lspci:
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Hawaii PRO [Radeon R9 290/390] (rev 80)
01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Hawaii HDMI Audio [Radeon R9 290/290X / 390/390X]

Using xorg-server-1.18.4, libdrm-git, mesa-git and xf86-video-amdgpu-git.

Comment 1 Michel Dänzer 2016-12-20 02:10:11 UTC

Thanks for the report. Should be fixed by https://cgit.freedesktop.org/~agd5f/linux/commit/?h=drm-next-4.10-wip&id=a1f49cc179ce6b7b7758ae3ff5cdb138d0ee0f56 .

Comment 2 Harald Judt 2016-12-20 11:03:40 UTC

Unfortunately, the commit does not fix the problem.

I have also seen this issue when logging out, and the lightdm login appears, so it may not even be related to hibernation/resuming, but I haven't had enough time to look properly into this.

Comment 3 Michel Dänzer 2016-12-20 14:29:20 UTC

(In reply to Harald Judt from comment #2)
> Unfortunately, the commit does not fix the problem.

Just to make sure, you did update the drm-next-4.10-wip branch again before testing, right? The commit in question only appeared there after you submitted this report.

If that commit really doesn't fix the problem, can you bisect which commit introduced it?

Comment 4 Jacky Hu 2017-01-10 09:22:48 UTC

I reverted both a1f49cc179ce and 7c83d7abc999, the hardware cursor is back working.

Obviously 7c83d7abc999 is wrong, and a1f49cc179ce is doubling it.

Comment 5 Michel Dänzer 2017-01-10 10:02:30 UTC

Please attach the dmesg output and Xorg log file corresponding to the problem.

Comment 6 Harald Judt 2017-01-11 09:42:51 UTC

Hi, sorry for not reporting earlier, but the holidays and lack of time...

I will test this and also the reverting patch send to the mailing list tonight and verify that it helps.

Comment 7 Harald Judt 2017-01-13 09:46:22 UTC

After applying the patch to revert the commits, hw cursor works fine. Feel free to close as resolved. Thanks!

Comment 8 Martin Peres 2019-11-19 08:11:53 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/117.

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.