From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 105188] Monitors don't always wake up after sleep Date: Wed, 21 Feb 2018 11:17:12 +0000 Message-ID: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2100649577==" 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 9EABF6E052 for ; Wed, 21 Feb 2018 11:17:13 +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 --===============2100649577== Content-Type: multipart/alternative; boundary="15192118330.b6c20.14438" Content-Transfer-Encoding: 7bit --15192118330.b6c20.14438 Date: Wed, 21 Feb 2018 11:17:13 +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=3D105188 Bug ID: 105188 Summary: Monitors don't always wake up after sleep 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: mbartoszkiewicz@gmail.com Created attachment 137497 --> https://bugs.freedesktop.org/attachment.cgi?id=3D137497&action=3Dedit Kernel log Hardware: GPU: Gigabyte Radeon RX 480 G1 Gaming 8GB Monitors: 3=C3=97 Eizo FlexScan S2243W, connected using DP Software: Distribution: Gentoo Kernel: 4.15.4 x11-drivers/xf86-video-amdgpu-1.4.0 x11-base/xorg-server-1.19.6 media-libs/mesa-18.0.0_rc4 x11-libs/libdrm-2.4.89 The monitors do not always correctly wake up from sleep. E.g. after locking the session, the monitors go to sleep. After pressing a key, only some wake up =E2=80=93 the rest are still sleepi= ng. It does not seem to be deterministic =E2=80=93 sometimes a monitor will wak= e up correctly, sometimes not. The kernel log attached is after running the following script: for i in {1..5}; do echo "XXX before suspend $i" | sudo tee /dev/kmsg; xset dpms force suspend; sleep 10; echo "XXX before on $i" | sudo tee /dev/kmsg; xset dpms force on; sleep 10; echo "XXX status $i:" $(cat /sys/devices/pci0000:00/0000:00:03.0/0000:03:00.0/drm/card0/card0-DP-*/stat= us) | sudo tee /dev/kmsg; done I am not sure if it is directly related to this issue, but the kernel log contains two refcount_t warnings in amdgpu code. --=20 You are receiving this mail because: You are the assignee for the bug.= --15192118330.b6c20.14438 Date: Wed, 21 Feb 2018 11:17:13 +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 105188
Summary Monitors don't always wake up after sleep
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 mbartoszkiewicz@gmail.com 

Created attachment 137497 [det=
ails]
Kernel log

Hardware:
 GPU: Gigabyte Radeon RX 480 G1 Gaming 8GB
 Monitors: 3=C3=97 Eizo FlexScan S2243W, connected using DP
Software:
 Distribution: Gentoo
 Kernel: 4.15.4
 x11-drivers/xf86-video-amdgpu-1.4.0
 x11-base/xorg-server-1.19.6
 media-libs/mesa-18.0.0_rc4
 x11-libs/libdrm-2.4.89

The monitors do not always correctly wake up from sleep.
E.g. after locking the session, the monitors go to sleep.
After pressing a key, only some wake up =E2=80=93 the rest are still sleepi=
ng.
It does not seem to be deterministic =E2=80=93 sometimes a monitor will wak=
e up
correctly, sometimes not.

The kernel log attached is after running the following script:
for i in {1..5}; do echo "XXX before suspend $i" | sudo tee /dev/=
kmsg; xset
dpms force suspend; sleep 10; echo "XXX before on $i" | sudo tee =
/dev/kmsg;
xset dpms force on; sleep 10; echo "XXX status $i:" $(cat
/sys/devices/pci0000:00/0000:00:03.0/0000:03:00.0/drm/card0/card0-DP-*/stat=
us)
| sudo tee /dev/kmsg; done

I am not sure if it is directly related to this issue, but the kernel log
contains two refcount_t warnings in amdgpu code.

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