From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 102684] Monitor sometimes cuts to black after idling overnight Date: Tue, 12 Sep 2017 16:58:46 +0000 Message-ID: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0441714557==" 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 55B636E6BF for ; Tue, 12 Sep 2017 16:58:46 +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 --===============0441714557== Content-Type: multipart/alternative; boundary="15052355260.a8130710.19791"; charset="UTF-8" --15052355260.a8130710.19791 Date: Tue, 12 Sep 2017 16:58:46 +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=3D102684 Bug ID: 102684 Summary: Monitor sometimes cuts to black after idling overnight 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: bugs.freedesktop@haasn.xyz This is a rather difficult issue to reproduce. After leaving my PC idle overnight (monitor turned off) and waking up the next day, I noticed an odd issue started happening: The monitor started randomly cutting to black for a second. It was not entirely unpredictable: it seemed to happen especially w= hen I triggered a seek in `mpv` -perhaps because this either recreated the framebuffer or recreated some video textures, I'm not entirely sure. Restar= ting X seems to have fixed it. The GPU was in power mode 'auto' overnight. It sort of reminds me of similar issues I had with the nvidia drivers some years ago, where leaving them in 'adaptive' performance mode overnight caus= ed them to fail switching frequencies the next day. Leaving them in 'performan= ce' mode overnight solved that issue; but it has also been since fixed. But that was an issue actually related to the performance scaling, whereas this seems more like an issue with the display connection in general. I'm not sure where else to take this - I can try reproducing it the next ti= me I go to sleep, I guess, just to see if it will happen again. Apart from that,= I'm pretty much blind debuggin here. Xorg version is 1.19.3, mesa version is 17.2, kernel version is 4.12.4, dev= ice is a Sapphire RX 560. --=20 You are receiving this mail because: You are the assignee for the bug.= --15052355260.a8130710.19791 Date: Tue, 12 Sep 2017 16:58:46 +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 102684
Summary Monitor sometimes cuts to black after idling overnight
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 bugs.freedesktop@haasn.xyz

This is a rather difficult issue to reproduce. After leaving m=
y PC idle
overnight (monitor turned off) and waking up the next day, I noticed an odd
issue started happening: The monitor started randomly cutting to black for a
second. It was not entirely unpredictable: it seemed to happen especially w=
hen
I triggered a seek in `mpv` -perhaps because this either recreated the
framebuffer or recreated some video textures, I'm not entirely sure. Restar=
ting
X seems to have fixed it. The GPU was in power mode 'auto' overnight.

It sort of reminds me of similar issues I had with the nvidia drivers some
years ago, where leaving them in 'adaptive' performance mode overnight caus=
ed
them to fail switching frequencies the next day. Leaving them in 'performan=
ce'
mode overnight solved that issue; but it has also been since fixed. But that
was an issue actually related to the performance scaling, whereas this seems
more like an issue with the display connection in general.

I'm not sure where else to take this - I can try reproducing it the next ti=
me I
go to sleep, I guess, just to see if it will happen again. Apart from that,=
 I'm
pretty much blind debuggin here.

Xorg version is 1.19.3, mesa version is 17.2, kernel version is 4.12.4, dev=
ice
is a Sapphire RX 560.


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