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: Thu, 25 Sep 2014 22:24:33 -0400 [thread overview]
Message-ID: <20140926022433.GA4602@thunk.org> (raw)
In-Reply-To: <CAPM=9txYd6LBojX+y5TYdW=8O=v49mcodj4iBZAmytXTRL68LA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2251 bytes --]
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?
>
> If so, then see if disabling that in the monitor menus helps.
>
> This is probably due to the fact we now attempt to talk to new DP devices
> with the protocol they provide. So previously the monitor exposed DP 1.2
> and we just didn't care, now if it exposes it we attempt to talk to it.
Hi Dave,
I've since upgraded to a newer X server, which may have been
responsible for the symptoms somewhat. It now doesn't seem to matter
whether the Dell 30" monitor is set to DP 1.2 or not. It now will
find the Dell 30" monitor reliably when the system is freshly booted,
attached to the Dock. If I then suspend the laptop, remove it from
the dock, unsuspend it from the laptop, then resuspend the laptop, and
return it to the dock, it can no longer see the monitor until I
reboot.
I am currently running 3.17-rc4 based kernel, and I have the following
X server components:
ii xserver-xorg 1:7.7+7 amd64 X.Org X server
ii xserver-xorg-core 2:1.16.0.901-1 amd64 Xorg X server - core server
ii xserver-xorg-video-intel 2:2.21.15-2+b2 amd64 X.Org X server -- Intel i8xx, i9xx display driver
Here is the dmesg file with drm.debug=6. Could you take a quick look
and see if anything obvious jumps out at you?
Thanks,
- Ted
[-- Attachment #2: dmesg-repro.gz --]
[-- Type: application/gzip, Size: 32179 bytes --]
next prev parent reply other threads:[~2014-09-26 2:24 UTC|newest]
Thread overview: 10+ 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
2014-09-02 11:23 ` Dave Airlie
2014-09-02 13:13 ` Theodore Ts'o
2014-09-26 2:24 ` Theodore Ts'o [this message]
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 4:08 ` 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=20140926022433.GA4602@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 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).