public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Josh Boyer <jwboyer@fedoraproject.org>
Cc: Dave Airlie <airlied@linux.ie>, Xi Ruoyao <xry111@outlook.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	"Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>,
	DRI mailing list <dri-devel@lists.freedesktop.org>,
	Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [git pull] drm fixes
Date: Tue, 24 Mar 2015 08:32:19 +0100	[thread overview]
Message-ID: <20150324073219.GV1349@phenom.ffwll.local> (raw)
In-Reply-To: <CA+5PVA7MwRfEnhvwAzPqhLCx3c+88E8xnZ0NPL=7Lun5UmW8Yw@mail.gmail.com>

On Mon, Mar 23, 2015 at 02:34:27PM -0400, Josh Boyer wrote:
> On Mon, Mar 23, 2015 at 11:33 AM, Josh Boyer <jwboyer@fedoraproject.org> wrote:
> 
> <snip>
> 
> >> Xi Ruoyao (1):
> >>       drm/i915: Ensure plane->state->fb stays in sync with plane->fb
> 
> Turns out to be that commit.
> 
> git bisect start 'drivers/gpu/drm/i915/'
> # good: [b314acaccd7e0d55314d96be4a33b5f50d0b3344] Merge branch
> 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input
> git bisect good b314acaccd7e0d55314d96be4a33b5f50d0b3344
> # bad: [bc465aa9d045feb0e13b4a8f32cc33c1943f62d6] Linux 4.0-rc5
> git bisect bad bc465aa9d045feb0e13b4a8f32cc33c1943f62d6
> # bad: [319c1d420a0b62d9dbb88104afebaabc968cdbfa] drm/i915: Ensure
> plane->state->fb stays in sync with plane->fb
> git bisect bad 319c1d420a0b62d9dbb88104afebaabc968cdbfa
> # first bad commit: [319c1d420a0b62d9dbb88104afebaabc968cdbfa]
> drm/i915: Ensure plane->state->fb stays in sync with plane->fb
> 
> Doing a straight revert on top of 4.0-rc5 makes things work again,
> albeit with the WARN_ON(obj->frontbuffer_bits) splat still being
> there.

Can you please test the tip of drm-fixes:

commit 8218c3f4df3bb1c637c17552405039a6dd3c1ee1
Author: Daniel Vetter <daniel.vetter@ffwll.ch>
Date:   Fri Feb 27 12:58:13 2015 +0100

    drm: Fixup racy refcounting in plane_force_disable

http://cgit.freedesktop.org/~airlied/linux/commit/?h=drm-fixes&id=8218c3f4df3bb1c637c17552405039a6dd3c1ee1

Because fumble that patch didn't make it to drm-fixes a while ago and
instead landed in drm-next.

Thanks, Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch

  reply	other threads:[~2015-03-24  7:30 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-20 21:49 [git pull] drm fixes Dave Airlie
2015-03-21 17:50 ` Linus Torvalds
2015-03-23 15:33 ` Josh Boyer
2015-03-23 18:34   ` Josh Boyer
2015-03-24  7:32     ` Daniel Vetter [this message]
2015-03-24 13:15       ` [Intel-gfx] " Josh Boyer
2015-03-24 13:40         ` Daniel Vetter
2015-03-24 13:57           ` Josh Boyer
2015-03-24 14:22             ` Josh Boyer
2015-03-24 14:34               ` Daniel Vetter
2015-03-24 14:46                 ` Josh Boyer
2015-03-24 16:10                   ` Josh Boyer
2015-03-24 16:48                     ` Daniel Vetter
2015-03-24 16:49                       ` Daniel Vetter
2015-03-24 16:54                         ` Josh Boyer
2015-03-25  3:49                           ` Xi Ruoyao
2015-03-25  8:54                     ` Daniel Vetter
2015-03-25 13:11                       ` Josh Boyer
2015-03-25 14:00                         ` Daniel Vetter
2015-03-25 14:56                           ` Xi Ruoyao
2015-03-25 15:12                             ` Xi Ruoyao
2015-03-25 15:19                             ` Jani Nikula
2015-03-25 15:26                           ` Takashi Iwai
2015-03-25 15:37                           ` Josh Boyer
2015-03-25 15:50                             ` Daniel Vetter
2015-03-25 15:53                               ` Josh Boyer
2015-03-25 16:42                                 ` Josh Boyer
2015-03-25 17:17                                   ` Daniel Vetter
2015-03-25 17:37                                     ` Josh Boyer
2015-03-25 19:40                                       ` Josh Boyer
2015-03-25 23:32                                         ` Xi Ruoyao
2015-03-25 23:45                                           ` Xi Ruoyao
2015-03-26  8:41                                           ` Xi Ruoyao
2015-03-26 12:06                                       ` Jani Nikula
2015-03-26 12:02                       ` Jani Nikula
2015-03-24  1:41   ` Dave Jones
2015-03-25  8:56     ` Daniel Vetter
2015-03-25 14:34       ` Dave Jones
  -- strict thread matches above, loose matches on Subject: below --
2015-02-27  4:42 Dave Airlie
2015-03-01  5:40 ` Linus Torvalds
2015-03-01  6:08   ` Linus Torvalds
2015-03-01  7:27     ` Linus Torvalds
2015-03-01 20:35       ` Linus Torvalds
2015-03-01 21:00         ` Linus Torvalds
2015-03-02  1:59           ` Linus Torvalds
2015-03-02  9:04             ` Daniel Vetter
2015-03-02 16:53               ` Linus Torvalds
2015-03-02 17:23                 ` [Intel-gfx] " Daniel Vetter
2015-03-02  9:44     ` Paul Bolle
2015-03-02 10:33       ` [Intel-gfx] " Daniel Vetter

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=20150324073219.GV1349@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jwboyer@fedoraproject.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=xry111@outlook.com \
    /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