From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 46711] Monitor not turning on after DisplayPort re-plug in Xorg
Date: Wed, 07 Jan 2015 01:40:40 +0000 [thread overview]
Message-ID: <bug-46711-502-PijenR8DAF@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-46711-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 990 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=46711
Branen Salmon <bugs@nenarb.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bugs@nenarb.net
--- Comment #20 from Branen Salmon <bugs@nenarb.net> ---
Created attachment 111880
--> https://bugs.freedesktop.org/attachment.cgi?id=111880&action=edit
Logs from a reproduction of the bug using recent software
I'm seeing the same issue with Xorg 1.16.2.901, Linux 3.16.0, and a Radeon HD
7750. I've attached DRM logs that contrast the behavior when the monitor is
power-cycled in X (there's no signal when the monitor is powered back on) to
the behavior when the monitor is power-cycled in kernel framebuffer VT (the
signal returns when the monitor is powered back on), but am not sure what to
make of them.
Thanks!
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2511 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-01-07 1:40 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 10:22 [Bug 46711] New: Monitor not turning on after DisplayPort re-plug in Xorg bugzilla-daemon
2012-02-28 11:58 ` [Bug 46711] " bugzilla-daemon
2012-02-28 12:10 ` bugzilla-daemon
2012-02-28 15:59 ` bugzilla-daemon
2012-04-13 21:48 ` bugzilla-daemon
2012-04-13 22:28 ` bugzilla-daemon
2012-04-16 15:00 ` bugzilla-daemon
2012-04-16 15:25 ` bugzilla-daemon
2012-04-16 15:54 ` bugzilla-daemon
2012-04-16 16:07 ` bugzilla-daemon
2012-04-17 15:23 ` bugzilla-daemon
2012-04-17 15:45 ` bugzilla-daemon
2012-04-17 16:09 ` bugzilla-daemon
2012-04-17 16:37 ` bugzilla-daemon
2012-04-18 7:59 ` bugzilla-daemon
2012-04-18 8:16 ` bugzilla-daemon
2012-04-18 14:07 ` bugzilla-daemon
2012-04-20 10:07 ` bugzilla-daemon
2014-04-09 18:05 ` bugzilla-daemon
2014-04-09 22:05 ` bugzilla-daemon
2015-01-07 1:40 ` bugzilla-daemon [this message]
2015-01-11 2:29 ` bugzilla-daemon
2015-07-20 21:41 ` bugzilla-daemon
2016-03-24 10:41 ` bugzilla-daemon
2019-02-09 9:35 ` bugzilla-daemon
2019-04-19 8:14 ` bugzilla-daemon
2019-11-19 8:25 ` 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-46711-502-PijenR8DAF@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).