From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 102684] Monitor sometimes cuts to black after idling overnight
Date: Tue, 12 Sep 2017 16:58:46 +0000 [thread overview]
Message-ID: <bug-102684-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1868 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=102684
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 when
I triggered a seek in `mpv` -perhaps because this either recreated the
framebuffer or recreated some video textures, I'm not entirely sure. Restarting
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 caused
them to fail switching frequencies the next day. Leaving them in 'performance'
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 time 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, device
is a Sapphire RX 560.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3170 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2017-09-12 16:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-12 16:58 bugzilla-daemon [this message]
2017-09-15 7:02 ` [Bug 102684] Monitor sometimes cuts to black after idling overnight bugzilla-daemon
2018-06-30 17:08 ` bugzilla-daemon
2019-11-19 8:24 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-102684-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.