From: Theodore Ts'o <tytso@mit.edu>
To: Dave Airlie <airlied@gmail.com>
Cc: Jani Nikula <jani.nikula@intel.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
LKML <linux-kernel@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [REGRESSION] i915: failure to see Dell 30" monitor connected to a Lenovo Haswell docking station
Date: Tue, 2 Sep 2014 07:03:37 -0400 [thread overview]
Message-ID: <20140902110337.GA5049@thunk.org> (raw)
In-Reply-To: <CAPM=9txYd6LBojX+y5TYdW=8O=v49mcodj4iBZAmytXTRL68LA@mail.gmail.com>
On Tue, Sep 02, 2014 at 02:15:39PM +1000, Dave Airlie wrote:
> On 2 September 2014 14:05, Theodore Ts'o <tytso@mit.edu> wrote:
> > I recently upgraded to v3.17-rc3, and on my Lenovo T540p, I can no
> > longer see the my Dell 30" monitor when it is connected via the
> > docking station using a Displayport connector. This worked using 3.16
> > kernel.
> >
> > If I connect to the monitor using the mini-display, by passing the
> > docking station, things work fine (but of course it's annoying not to
> > be able to use the docking station).
> >
> > Is this a known problem? This is not the first time that we've had
> > regressions with this docking station. It's vaguely reminsicent of
> >
> > https://bugs.freedesktop.org/show_bug.cgi?id=71267
> >
> > Except the system isn't hanging; it's just not seeing the monitor at all.
>
> Have you the Dell 30" set to Displayport 1.2 enabled mode?
No, it DP 1.2 was disabled. If I enable it, it breaks things when I
try connecting via the MiniDP port (bypassing the dock), and it is
still broken when I try to talk via the DisplayPort in the dock.
If I disable DP 1.2 again, it works via the MiniDP port, but if I try
to connect through the dock (which has a DP Hub which I believe is
MST/DP 1.2 capable), it is still broken.
It does seem that this might be related to 3.17-rc3 trying to talk DP
1.2 if it is available, since I can't control what the DP hub in the
docking station advertises --- is there a commit or some kind of hack
I can try to force talking to the DP hub using DP 1.1?
- Ted
WARNING: multiple messages have this Message-ID (diff)
From: "Theodore Ts'o" <tytso@mit.edu>
To: Dave Airlie <airlied@gmail.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
dri-devel <dri-devel@lists.freedesktop.org>,
LKML <linux-kernel@vger.kernel.org>,
Jani Nikula <jani.nikula@intel.com>
Subject: Re: [REGRESSION] i915: failure to see Dell 30" monitor connected to a Lenovo Haswell docking station
Date: Tue, 2 Sep 2014 07:03:37 -0400 [thread overview]
Message-ID: <20140902110337.GA5049@thunk.org> (raw)
In-Reply-To: <CAPM=9txYd6LBojX+y5TYdW=8O=v49mcodj4iBZAmytXTRL68LA@mail.gmail.com>
On Tue, Sep 02, 2014 at 02:15:39PM +1000, Dave Airlie wrote:
> On 2 September 2014 14:05, Theodore Ts'o <tytso@mit.edu> wrote:
> > I recently upgraded to v3.17-rc3, and on my Lenovo T540p, I can no
> > longer see the my Dell 30" monitor when it is connected via the
> > docking station using a Displayport connector. This worked using 3.16
> > kernel.
> >
> > If I connect to the monitor using the mini-display, by passing the
> > docking station, things work fine (but of course it's annoying not to
> > be able to use the docking station).
> >
> > Is this a known problem? This is not the first time that we've had
> > regressions with this docking station. It's vaguely reminsicent of
> >
> > https://bugs.freedesktop.org/show_bug.cgi?id=71267
> >
> > Except the system isn't hanging; it's just not seeing the monitor at all.
>
> Have you the Dell 30" set to Displayport 1.2 enabled mode?
No, it DP 1.2 was disabled. If I enable it, it breaks things when I
try connecting via the MiniDP port (bypassing the dock), and it is
still broken when I try to talk via the DisplayPort in the dock.
If I disable DP 1.2 again, it works via the MiniDP port, but if I try
to connect through the dock (which has a DP Hub which I believe is
MST/DP 1.2 capable), it is still broken.
It does seem that this might be related to 3.17-rc3 trying to talk DP
1.2 if it is available, since I can't control what the DP hub in the
docking station advertises --- is there a commit or some kind of hack
I can try to force talking to the DP hub using DP 1.1?
- Ted
next prev parent reply other threads:[~2014-09-02 11:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-02 4:05 [REGRESSION] i915: failure to see Dell 30" monitor connected to a Lenovo Haswell docking station Theodore Ts'o
2014-09-02 4:15 ` Dave Airlie
2014-09-02 11:03 ` Theodore Ts'o [this message]
2014-09-02 11:03 ` Theodore Ts'o
2014-09-02 11:23 ` Dave Airlie
2014-09-02 11:23 ` Dave Airlie
2014-09-02 13:13 ` Theodore Ts'o
2014-09-02 13:13 ` Theodore Ts'o
2014-09-26 2:24 ` Theodore Ts'o
2014-09-26 2:24 ` Theodore Ts'o
2014-12-08 0:34 ` WARNING: /usr/projects/linux/linux/drivers/gpu/drm/i915/intel_pm.c:6585 intel_display_power_put+0x4b/0x116 [i915]() Theodore Ts'o
2014-12-08 2:32 ` Dave Airlie
2014-12-08 2:32 ` Dave Airlie
2014-12-08 4:08 ` Theodore Ts'o
2014-12-08 4:08 ` Theodore Ts'o
2014-12-15 13:26 ` Theodore Ts'o
2014-12-15 13:26 ` Theodore Ts'o
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=20140902110337.GA5049@thunk.org \
--to=tytso@mit.edu \
--cc=airlied@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=linux-kernel@vger.kernel.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.