From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 39027] [evergreen] Monitor fails to come back after unplug and replug (recent regression)
Date: Thu, 7 Jul 2011 02:50:22 -0700 (PDT) [thread overview]
Message-ID: <20110707095022.C0A4513004D@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-39027-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=39027
Thomas Lindroth <thomas.lindroth@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Product|xorg |DRI
Component|Driver/Radeon |DRM/Radeon
AssignedTo|xorg-driver-ati@lists.x.org |dri-devel@lists.freedesktop
| |.org
QAContact|xorg-team@lists.x.org |
--- Comment #1 from Thomas Lindroth <thomas.lindroth@gmail.com> 2011-07-07 02:50:21 PDT ---
It is a kernel regression. A bisect on the drivers/gpu folder resulted in the
following likely candidate.
commit 1e85e1d07b9255bd52c557f1a77fb72ccfacaf1c
Author: Alex Deucher <alexdeucher@gmail.com>
Date: Fri May 20 04:34:29 2011 -0400
drm/radeon/kms: simplify hotplug handler logic
In the hotplug handler, just use the drm dpms functions.
If the monitor is plugged in, turn it on, if it's not,
turn it off. This also reduces power usage by turning
off the encoder and crtc when the monitor is unplugged.
Signed-off-by: Alex Deucher <alexdeucher@gmail.com>
Signed-off-by: Dave Airlie <airlied@redhat.com>
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next parent reply other threads:[~2011-07-07 9:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-39027-502@http.bugs.freedesktop.org/>
2011-07-07 9:50 ` bugzilla-daemon [this message]
2011-07-11 14:48 ` [Bug 39027] [evergreen] Monitor fails to come back after unplug and replug (recent regression) bugzilla-daemon
2011-07-11 17:38 ` bugzilla-daemon
2011-07-31 18:45 ` bugzilla-daemon
2011-07-31 22:07 ` 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=20110707095022.C0A4513004D@annarchy.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.