From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 101499] Black screen when detaching HDMI cable (AMD A10-9620P)
Date: Tue, 20 Jun 2017 09:25:30 +0000 [thread overview]
Message-ID: <bug-101499-502-qkQ413wAXQ@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-101499-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1381 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=101499
--- Comment #11 from Michel Dänzer <michel@daenzer.net> ---
(In reply to Carlo Caione from comment #10)
> Probably I'm missing something, but when the HDMI is connected everything
> works fine, with the scanout buffer correctly displayed on the laptop panel
> + external monitor. The problem starts when we _disconnect_ the HDMI cable.
At least some of the errors you referenced in comment 8 already happen before
that. They're related to failed attempts at page flipping. xf86-video-amdgpu
manages to chug along regardless.
When you unplug the HDMI cable is presumably when
> Jun 19 17:10:31 endless gdm-Xorg-:0[672]: (EE) AMDGPU(0): failed to set mode: Invalid argument
appears, i.e. drmModeSetCrtc() fails, presumably (not 100% sure about this part
though) because the new, smaller scanout buffer cannot fit into VRAM while the
old, larger one is still being scanned out.
> Also if it was a problem with VRAM being too small, why toggling the DPMS
> makes the laptop panel working fine again?
Toggling DPMS off disables scanout, which allows the old scanout buffer to be
moved out of VRAM, so the new one can be moved in.
Some details might differ from the above, but that should be roughly what's
happening.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2359 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-20 9:25 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 [this message]
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
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-qkQ413wAXQ@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).