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: Mon, 16 Apr 2012 16:07:59 +0000 [thread overview]
Message-ID: <bug-46711-502-4fC8NvjixH@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-46711-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=46711
--- Comment #9 from Alex Deucher <agd5f@yahoo.com> 2012-04-16 09:07:59 PDT ---
(In reply to comment #8)
>
> Brief look doesn't show me any locks there, I'll dig in.
The locking (or lack there of) would be on the kernel side.
>
> If relevant, we have the same symptoms with and without a "desktop
> environment". Meaning same thing happens with pure X, and also with our
> software running which does explicit output probing when nothing is connected.
>
> Problem is (seems to me) xrandr reports monitor connected when in that state.
>
> Also if relevant we do get two RandR events (RRScreenChangeNotify and
> RRNotify_OutputChange) when re-plugging the monitor.
>
> Unless there is no intersection between RandR and DPMS... ?
We don't change the dpms state in the hotplug handler we just use the dpms code
paths to properly tear down and bring up the display when an enabled monitor is
connected or disconnected.
Unfortunately it's been a while since I looked at this so I don't remember how
events are handled once X gets them.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2012-04-16 16:07 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 [this message]
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
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-4fC8NvjixH@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).