From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 109246] HDMI connected monitors fail to sleep and instead turn back on when amdgpu.dc=1 Date: Wed, 09 Jan 2019 14:39:49 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1676838733==" 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 3335C6EC7C for ; Wed, 9 Jan 2019 14:39:49 +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 --===============1676838733== Content-Type: multipart/alternative; boundary="15470447890.B918C.14162" Content-Transfer-Encoding: 7bit --15470447890.B918C.14162 Date: Wed, 9 Jan 2019 14:39:49 +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=3D109246 --- Comment #13 from Nicholas Kazlauskas --- (In reply to Michel D=C3=A4nzer from comment #12) > (In reply to tme from comment #9) > > Setting amdgpu.dc=3D1 on 4.15.18 and 4.16.18 does not reproduce the pro= blem. > > It does, however, reproduce on 4.17.19. >=20 > Can you bisect between 4.16.18 and 4.17.19? >=20 > (I see some HPD filtering related changes between them, Nicholas / Harry > maybe you can take a look if anything jumps out?) I haven't had a chance to look into the HPD changes yet, but we haven't seen this bug occur with our DPMS tests so I'm guessing that it's monitor specif= ic. A system environment with Ubuntu/Plasma/xf86-video-amdgpu seems pretty stan= dard at least. A bisection point on amd-staging-drm-next would certainly help narrow this down. --=20 You are receiving this mail because: You are the assignee for the bug.= --15470447890.B918C.14162 Date: Wed, 9 Jan 2019 14:39:49 +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

Comme= nt # 13 on bug 10924= 6 from Nicholas Kazlauskas<= /a> 
(In reply to Michel D=C3=A4nzer from comment #12)
> (In reply to tme from comment #9)
> > Setting amdgpu.dc=3D1 on 4.15.18 and 4.16.18 does not reproduce t=
he problem.
> > It does, however, reproduce on 4.17.19.
>=20
> Can you bisect between 4.16.18 and 4.17.19?
>=20
> (I see some HPD filtering related changes between them, Nicholas / Har=
ry
> maybe you can take a look if anything jumps out?)

I haven't had a chance to look into the HPD changes yet, but we haven't seen
this bug occur with our DPMS tests so I'm guessing that it's monitor specif=
ic.
A system environment with Ubuntu/Plasma/xf86-video-amdgpu seems pretty stan=
dard
at least.

A bisection point on amd-staging-drm-next would certainly help narrow this
down.

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