From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 46711] New: Monitor not turning on after DisplayPort re-plug in Xorg
Date: Tue, 28 Feb 2012 10:22:57 +0000 [thread overview]
Message-ID: <bug-46711-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=46711
Bug #: 46711
Summary: Monitor not turning on after DisplayPort re-plug in
Xorg
Classification: Unclassified
Product: DRI
Version: unspecified
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: tvrtko.ursulin@onelan.co.uk
Created attachment 57747
--> https://bugs.freedesktop.org/attachment.cgi?id=57747
Kernel DRM debug log showing successful replug without, and failing with Xorg
running.
On a AMD G-T56N (Radeon HD 6310) box connected to the monitor via DisplayPort
monitor does not come on after re-plugging the display cable but claims to be
in power save.
At the same time, according to xrandr it is connected and displaying.
Stopping Xorg and monitor comes back up displaying the console.
Re-pluging the display cable with no Xorg running is fine.
Attached kernel DRM debug log. Log itself which ends after cable re-plug when
Xorg is running. Which is when the display goes into power save. Before that in
the same log you can find Xorg starting up and before that a successful cable
re-
plug when X was not running.
All this is with kernel.org 3.3.0-rc4 kernel. Xorg packages are:
xorg-x11-server-Xorg-1.11.3-1.fc16.x86_64
xorg-x11-drv-ati-6.14.3-8.20120209gite20284409.fc16.x86_64
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2012-02-28 10:22 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 10:22 bugzilla-daemon [this message]
2012-02-28 11:58 ` [Bug 46711] Monitor not turning on after DisplayPort re-plug in Xorg 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
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@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).