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: Tue, 08 Jan 2019 05:09:31 +0000 Message-ID: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0181201470==" 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 81A8B6E00D for ; Tue, 8 Jan 2019 05:09:31 +0000 (UTC) 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 --===============0181201470== Content-Type: multipart/alternative; boundary="15469241710.AFCBAd08.12469" Content-Transfer-Encoding: 7bit --15469241710.AFCBAd08.12469 Date: Tue, 8 Jan 2019 05:09:31 +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 Bug ID: 109246 Summary: HDMI connected monitors fail to sleep and instead turn back on when amdgpu.dc=3D1 Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel@lists.freedesktop.org Reporter: t00m4nyerr0rs@gmail.com Original launchpad thread: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790861 Overview: When my computer tries to suspend my monitors after a period of idleness, they'll suspend for a few seconds before waking back up. Steps to Reproduce: 1) Have a monitor attached over HDMI. 2) Set screen energy saving (in Plasma 5) to 1 minute. 3) After 1 minute has passed, the monitor will try to enter sleep mode. It = will fail and turn back on. 4) The monitor will continue to attempt to enter sleep mode every minute un= til interrupted by the user. Actual Results: The monitors turn back on a few seconds after entering sleep mode. Expected Results: The monitors stay in sleep mode. Additional Information: While I have two monitors, this issue is only triggered when one is connect= ed using HDMI. Connecting only one monitor using HDMI will trigger the problem. Connecting either one using DVI does not trigger the problem.=20 I am unable to test if DisplayPort triggers the problem, as I have no compatible monitors. Setting the kernel parameter amdgpu.dc=3D0 does not cause the problem to tr= igger. I haven't confirmed if the other affected users in the launchpad thread are using HDMI, so I'm only reporting my experience. --=20 You are receiving this mail because: You are the assignee for the bug.= --15469241710.AFCBAd08.12469 Date: Tue, 8 Jan 2019 05:09:31 +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
Bug ID 109246
Summary HDMI connected monitors fail to sleep and instead turn back o= n when amdgpu.dc=3D1
Product DRI
Version unspecified
Hardware x86-64 (AMD64)
OS Linux (All)
Status NEW
Severity normal
Priority medium
Component DRM/AMDgpu
Assignee dri-devel@lists.freedesktop.org
Reporter t00m4nyerr0rs@gmail.com 

Original launchpad thread:
ht=
tps://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790861

  Overview:
When my computer tries to suspend my monitors after a period of idleness,
they'll suspend for a few seconds before waking back up.

  Steps to Reproduce:
1) Have a monitor attached over HDMI.
2) Set screen energy saving (in Plasma 5) to 1 minute.
3) After 1 minute has passed, the monitor will try to enter sleep mode. It =
will
fail and turn back on.
4) The monitor will continue to attempt to enter sleep mode every minute un=
til
interrupted by the user.

  Actual Results:
The monitors turn back on a few seconds after entering sleep mode.

  Expected Results:
The monitors stay in sleep mode.

  Additional Information:
While I have two monitors, this issue is only triggered when one is connect=
ed
using HDMI. Connecting only one monitor using HDMI will trigger the problem.
Connecting either one using DVI does not trigger the problem.=20
I am unable to test if DisplayPort triggers the problem, as I have no
compatible monitors.
Setting the kernel parameter amdgpu.dc=3D0 does not cause the problem to tr=
igger.

I haven't confirmed if the other affected users in the launchpad thread are
using HDMI, so I'm only reporting my experience.

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