From: Jani Nikula <jani.nikula@linux.intel.com>
To: Daniel Martin <consume.noise@gmail.com>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [i915 dp mst] drm-intel-nightly-2015y-05m-07d dies when monitor at docking station
Date: Fri, 08 May 2015 18:13:56 +0300 [thread overview]
Message-ID: <87sib785l7.fsf@intel.com> (raw)
In-Reply-To: <CADscph2GzOS4Bdcp0i6ggwO9_i-xZ--SKJ8YmSSVLRR2hSA48Q@mail.gmail.com>
On Fri, 08 May 2015, Daniel Martin <consume.noise@gmail.com> wrote:
> On 8 May 2015 at 11:26, Daniel Martin <consume.noise@gmail.com> wrote:
>> Hi,
>>
>> I've just tested drm-intel-nightly, last commit:
>>
>> 20e7fca drm-intel-nightly: 2015y-05m-07d-16h-16m-10s UTC
>> integration manifest
>>
>> and it makes the machine crash as soon as I plug a monitor to the
>> docking station or boot with one already attached. dmesg has been
>> captured while plugging in a VGA connector, but it happens with DP
>> too.
>
> The first bad commit is:
> 8c7b5cc drm/i915: Use atomic helpers for computing changed flags
Please update nightly and try again, a commit referencing that one as
regressing was just pushed:
commit 90d469067d0808ddbd9be2c97a4a8e14037b5e46
Author: Matt Roper <matthew.d.roper@intel.com>
Date: Thu May 7 14:31:28 2015 -0700
drm/i915: Set crtc_state->active to false when CRTC is disabled (v2)
BR,
Jani.
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2015-05-08 15:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-08 9:26 [i915 dp mst] drm-intel-nightly-2015y-05m-07d dies when monitor at docking station Daniel Martin
2015-05-08 12:46 ` Daniel Martin
2015-05-08 15:13 ` Jani Nikula [this message]
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=87sib785l7.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=consume.noise@gmail.com \
--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