From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 95206] Display port bandwidth regression
Date: Fri, 29 Apr 2016 11:40:16 +0000 [thread overview]
Message-ID: <bug-95206-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1727 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=95206
Bug ID: 95206
Summary: Display port bandwidth regression
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel@lists.freedesktop.org
Reporter: barneyman@gmx.de
Hi,
I have a mobile laptop (Dell Precision M4600) with an external monitor (Dell
U2414H) connected via display port.
Starting with mainline kernel 4.5.x I'm unable to connect the monitor with mode
(1920x1080p), instead the highest available option is 1920x1080i (interlaced)
which produces heavy flickering on the monitor and makes it unable to use at
all. Forcing the monitor into 1920x1080p (using xrandr --newmode, --addmode and
--mode) causes a total signal loss, however forcing the monitor into
1920x1080p@30hz makes the monitor available again. If I connect the monitor
using DVI/HDMI 1080p@60hz works without any problems.
So I think the problem might be that the maximum bandwidth of the display port
is reduced compared to the previous version.
Using kernel 4.4.8 the monitor is connected with 1080p using DP as expected
again. So it's definitely a regression introduced in kernel 4.5.
As a side note: the Ubuntu 16.04 kernel (4.4.0-21.37) also has this display
port problem, but as far as I know the ubuntu devs have backported large
portions of the 4.5 radeon patches.
If you need any further information (dmesg, xrandr output), don't hesitate to
ask...
Kind regards,
Christian
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2948 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2016-04-29 11:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-29 11:40 bugzilla-daemon [this message]
2016-04-29 14:19 ` [Bug 95206] Display port bandwidth regression bugzilla-daemon
2016-04-29 14:59 ` bugzilla-daemon
2016-04-29 15:00 ` bugzilla-daemon
2016-04-29 15:01 ` bugzilla-daemon
2016-04-29 15:03 ` bugzilla-daemon
2016-04-29 16:46 ` bugzilla-daemon
2016-04-29 19:51 ` bugzilla-daemon
2016-05-10 9:27 ` bugzilla-daemon
2016-05-10 20:36 ` bugzilla-daemon
2016-05-11 8:27 ` bugzilla-daemon
2016-05-11 20:22 ` bugzilla-daemon
2016-05-12 11:01 ` bugzilla-daemon
2016-12-08 23:18 ` bugzilla-daemon
2016-12-09 17:16 ` bugzilla-daemon
2016-12-10 16:48 ` bugzilla-daemon
2016-12-10 17:01 ` bugzilla-daemon
2017-01-03 0:53 ` bugzilla-daemon
2017-01-03 15:57 ` bugzilla-daemon
2017-01-03 15:57 ` bugzilla-daemon
2017-01-09 3:40 ` 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-95206-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 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.