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 09:13:52 -0400 [thread overview]
Message-ID: <20140902131352.GA6232@thunk.org> (raw)
In-Reply-To: <CAPM=9txM1HnJHdT=B03Nd4oawAy23a4Uen66kz8g5nG655WQ=Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1038 bytes --]
On Tue, Sep 02, 2014 at 09:23:16PM +1000, Dave Airlie wrote:
>
> Interesting, I have the same combo of hw available on my desk at work,
> but it might be a couple of days before I can get to the office to
> debug it,
>
> can you boot with drm.debug=6 and get me the dmesg?
I'll do that when I get home. In the meantime, here's an additional
data point. At work, I have the same model docking station connected
to a 2011 Dell 2410f Rev A04 (max resolution 1920x1200, and I suspect
not DP 1.2 capable; at least, it doesn't mention DP in monitor menu)
--- and connecting through the docking station, it does work
(connecting through either DVI or DisplayPort).
Here's the drm.debug=6 connecting to the docking station via DVI. I
can get a drm.debug=6 connecting via the DP and the docking station if
that would be helpful. Similarly, if you want, I can also try to get
a debug run connecting to the HP ZRW30 monitor (either direct or via
the docking station), since that's the monitor on the walkstation. :-)
Cheers,
- Ted
[-- Attachment #2: drm-debug.xz --]
[-- Type: application/octet-stream, Size: 27396 bytes --]
next prev parent reply other threads:[~2014-09-02 13:14 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 [this message]
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 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=20140902131352.GA6232@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).