From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 94471] Displayport monitor randomly disconnects
Date: Wed, 08 Apr 2015 09:39:04 +0000 [thread overview]
Message-ID: <bug-94471-2300-y88ANzNRLb@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-94471-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=94471
Leho Kraav <leho@kraav.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |leho@kraav.com
--- Comment #3 from Leho Kraav <leho@kraav.com> ---
Kernel 3.19.3
I can confirm that similar things with that kernel error message is happening
here as well.
apr 08 12:25:10 papaya kernel: [drm:drm_dp_get_mst_branch_device.isra.17
[drm_kms_helper]] *ERROR* failed to lookup MSTB with lct 2, rad 00
I have an LG 27" 2560 http://www.lg.com/us/monitors/lg-27EA83-D-led-monitor
connected to DELL PR02X dock via DisplayPort.
* After docking the laptop, if the monitor was powered on and sitting in
standby, all xrandr activation attempts fail with "*ERROR* failed to lookup
MSTB with lct 2, rad 00"
* After docking the laptop, I always have to power cycle the monitor in order
for xrandr --output DP1-1-8 --auto to succeed. See above.
MST implementation has been very flaky from the time it was implemented, but I
do understand it's more like prototype stage thing still and not enough
resource is available to make it more bulletproof. I've been able to crash the
whole display system with just xrandr-based display connection management
consistently, as in the screen goes completely blank with no way to bring it
back. Sucks a lot for being able to trust Linux with the basics, as a business
mobile desktop platform. Some more adventures for those interested
https://bugs.freedesktop.org/show_bug.cgi?id=85913
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-04-08 9:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-07 17:53 [Bug 94471] New: Displayport monitor randomly disconnects bugzilla-daemon
2015-03-09 2:31 ` [Bug 94471] " bugzilla-daemon
2015-03-09 10:51 ` bugzilla-daemon
2015-03-09 10:53 ` bugzilla-daemon
2015-04-08 9:39 ` bugzilla-daemon [this message]
2015-04-08 9:40 ` bugzilla-daemon
2015-10-07 10:09 ` 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-94471-2300-y88ANzNRLb@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.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.