From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 101499] Black screen when detaching HDMI cable (AMD A10-9620P)
Date: Thu, 22 Jun 2017 09:00:59 +0000 [thread overview]
Message-ID: <bug-101499-502-cIL8NrXrjD@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-101499-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 804 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=101499
--- Comment #17 from Carlo Caione <carlo@caione.org> ---
Created attachment 132130
--> https://bugs.freedesktop.org/attachment.cgi?id=132130&action=edit
dm_plane_helper_prepare_fb with AMDGPU_GEM_DOMAIN_GTT
> Right, sorry, with DC you need to tweak dm_plane_helper_prepare_fb instead.
Yup, I tried this but not much luck. In attachment what I get when using
AMDGPU_GEM_DOMAIN_GTT. Using AMDGPU_GEM_DOMAIN_GTT | AMDGPU_GEM_DOMAIN_VRAM is
pretty much the same but the cursor is correctly displayed (even though I
cannot move it).
The log is filled with:
[drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer
/me scratch his head
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1824 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 prev parent reply other threads:[~2017-06-22 9:00 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-19 16:27 [Bug 101499] Black screen when detaching HDMI cable (AMD A10-9620P) bugzilla-daemon
2017-06-19 16:29 ` bugzilla-daemon
2017-06-20 4:02 ` bugzilla-daemon
2017-06-20 6:11 ` bugzilla-daemon
2017-06-20 6:15 ` bugzilla-daemon
2017-06-20 6:21 ` bugzilla-daemon
2017-06-20 6:24 ` bugzilla-daemon
2017-06-20 6:38 ` bugzilla-daemon
2017-06-20 6:45 ` bugzilla-daemon
2017-06-20 7:24 ` bugzilla-daemon
2017-06-20 9:10 ` bugzilla-daemon
2017-06-20 9:25 ` bugzilla-daemon
2017-06-20 9:46 ` bugzilla-daemon
2017-06-20 16:15 ` bugzilla-daemon
2017-06-21 8:14 ` bugzilla-daemon
2017-06-21 15:28 ` bugzilla-daemon
2017-06-22 8:23 ` bugzilla-daemon
2017-06-22 9:00 ` bugzilla-daemon [this message]
2017-06-27 8:21 ` bugzilla-daemon
2017-06-27 8:29 ` bugzilla-daemon
2017-06-27 10:29 ` bugzilla-daemon
2017-06-30 7:43 ` bugzilla-daemon
2017-06-30 9:44 ` bugzilla-daemon
2017-07-02 19:21 ` bugzilla-daemon
2017-07-03 3:23 ` bugzilla-daemon
2019-11-19 8:19 ` 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-101499-502-cIL8NrXrjD@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).