From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 99143] r9 390: Hardware cursor invisible after hibernate/resume Date: Tue, 20 Dec 2016 14:29:20 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0378448802==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [IPv6:2610:10:20:722:a800:ff:fe98:4b55]) by gabe.freedesktop.org (Postfix) with ESMTP id E6BD16E9AC for ; Tue, 20 Dec 2016 14:29:19 +0000 (UTC) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============0378448802== Content-Type: multipart/alternative; boundary="14822441591.C060772F8.4504"; charset="UTF-8" --14822441591.C060772F8.4504 Date: Tue, 20 Dec 2016 14:29:19 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D99143 --- Comment #3 from Michel D=C3=A4nzer --- (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 submit= ted this report. If that commit really doesn't fix the problem, can you bisect which commit introduced it? --=20 You are receiving this mail because: You are the assignee for the bug.= --14822441591.C060772F8.4504 Date: Tue, 20 Dec 2016 14:29:19 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated

Comment= # 3 on bug 99143<= /a> from Michel D=C3=A4nzer 
(In reply to Harald Judt from comment #2)
> Unfortunately, the commit does not fix the probl=
em.

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 submit=
ted
this report.

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

You are receiving this mail because:
  • You are the assignee for the bug.
= --14822441591.C060772F8.4504-- --===============0378448802== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============0378448802==--