From: Dave Hansen <dave.hansen@intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Daniel Vetter <daniel.vetter@intel.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
DRI Development <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] drm: Don't race connector registration
Date: Thu, 26 Jan 2017 12:34:29 -0800 [thread overview]
Message-ID: <250cde2d-e97f-e5fd-b3d3-81d033cd14e5@intel.com> (raw)
In-Reply-To: <20170125153817.zk5ees7dv7azutbg@phenom.ffwll.local>
On 01/25/2017 07:38 AM, Daniel Vetter wrote:
> On Wed, Jan 25, 2017 at 07:20:45AM -0800, Dave Hansen wrote:
>> On 01/24/2017 10:21 PM, Daniel Vetter wrote:
>>> Hi Dave,
>>>
>>> Still waiting for your testing results on this one here ...
>>
>> It's definitely stable with that patch applied. No more crashes.
>>
>> But, it's also definitely having difficulty re-probing to find the
>> monitor that's attached to the dock in some cases. Whatever is going on
>> isn't fixed by poking it with xrandr.
>
> Is this new? When exactly does this happen? Does the mst sink connector no
> longer show up, or is the connected/disconnected status all wrong?
It's hard to say whether it's new or not. I *think* it worked better
before, but it also crashed pretty often, so it's hard to say.
And, yeah, I think it just gets the connected status wrong. The
connector is still there.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-01-26 20:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-12 16:15 [PATCH] drm: Don't race connector registration Daniel Vetter
2017-01-12 16:17 ` Daniel Vetter
2017-01-25 6:21 ` Daniel Vetter
2017-01-25 15:20 ` Dave Hansen
2017-01-25 15:38 ` Daniel Vetter
2017-01-26 20:34 ` Dave Hansen [this message]
2017-01-30 9:12 ` Daniel Vetter
2017-01-30 16:43 ` Dave Hansen
2017-01-31 7:44 ` Daniel Vetter
[not found] ` <e5d9f6e2-3fcc-59e1-6e12-b8062b5122f5@intel.com>
2017-02-01 0:27 ` Dave Hansen
2017-02-01 8:52 ` Daniel Vetter
2017-02-01 20:55 ` Dave Hansen
2017-01-12 16:54 ` Chris Wilson
2017-01-12 17:54 ` ✓ Fi.CI.BAT: success for " Patchwork
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=250cde2d-e97f-e5fd-b3d3-81d033cd14e5@intel.com \
--to=dave.hansen@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@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 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).