From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 101499] Black screen when detaching HDMI cable (AMD A10-9620P)
Date: Mon, 19 Jun 2017 16:27:19 +0000 [thread overview]
Message-ID: <bug-101499-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1315 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=101499
Bug ID: 101499
Summary: Black screen when detaching HDMI cable (AMD A10-9620P)
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: carlo@caione.org
Created attachment 132061
--> https://bugs.freedesktop.org/attachment.cgi?id=132061&action=edit
journal_from_boot_to_HDMI_cable_detaching
We are working with new laptops that have the AMD Bristol Ridge
chipset with this SoC:
AMD A10-9620P RADEON R5, 10 COMPUTE CORES 4C+6G
When the HDMI cable is attached and then detached, the internal panel goes
black and the only way to have it back is switching to another TTY and then
back to xorg or doing 'xset dpms force off; xset dpms force on'.
This is reproducible also on the ~agd5f/drm-next-4.13-wip branch.
In the attachment the whole journal when booting the kernel compiled from
~agd5f/drm-next-4.13-wip, landing in xorg and then attaching and detaching the
HDMI cable.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2791 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-06-19 16:27 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-19 16:27 bugzilla-daemon [this message]
2017-06-19 16:29 ` [Bug 101499] Black screen when detaching HDMI cable (AMD A10-9620P) 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
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@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.