From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752772AbbCQHvs (ORCPT ); Tue, 17 Mar 2015 03:51:48 -0400 Received: from mail-wg0-f44.google.com ([74.125.82.44]:33982 "EHLO mail-wg0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752652AbbCQHvl (ORCPT ); Tue, 17 Mar 2015 03:51:41 -0400 Date: Tue, 17 Mar 2015 08:53:21 +0100 From: Daniel Vetter To: Steven Rostedt Cc: Daniel Vetter , Andrey Skvortsov , Chris Wilson , Daniel Vetter , Jani Nikula , David Airlie , intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, Sitsofe Wheeler Subject: Re: [Intel-gfx] [Regression] WARNING: drivers/gpu/drm/i915/i915_gem.c:4525 i915_gem_free_object Message-ID: <20150317075321.GM21993@phenom.ffwll.local> Mail-Followup-To: Steven Rostedt , Andrey Skvortsov , Chris Wilson , Daniel Vetter , Jani Nikula , David Airlie , intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, Sitsofe Wheeler References: <20150203191507.GA2374@crion86> <20150203202152.GD5784@nuc-i3427.alporthouse.com> <20150204182627.GA2272@crion86> <20150204184217.GG10991@nuc-i3427.alporthouse.com> <20150223201239.GC3871@crion86> <20150305142728.GC3042@home.goodmis.org> <20150316114503.21846d5e@gandalf.local.home> <20150316164333.GJ21993@phenom.ffwll.local> <20150316132158.35df25a1@gandalf.local.home> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150316132158.35df25a1@gandalf.local.home> X-Operating-System: Linux phenom 4.0.0-rc3+ User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Mar 16, 2015 at 01:21:58PM -0400, Steven Rostedt wrote: > On Mon, 16 Mar 2015 17:43:33 +0100 > Daniel Vetter wrote: > > > > Is linux-next also affected or is this just a case of i915 maintainers > > having failed to push the right patch to -fixes? > > I just confirmed, linux-next boots without the warning. > > > > > I'll try to figure out what fell apart here meanwhile. To help out, can > > you please boot with drm.debug=0xe and grab the full dmesg for booting? > > Looks like it falls over in the initial fbcon modeset, which is indeed > > strange ... > > Here they are: > > http://rostedt.homelinux.com/private/dmesg-next > > http://rostedt.homelinux.com/private/dmesg-4.0 The unnerving part is that I didn't find any patch not anything else that might fix this frontbuffer_bits leak. I also couldn't spot the bug. The real reason why -next works and 4.0 doesn't seems to be that 4.0 reconstructs a bogus initial framebuffer and then falls over when cleaning that up. -next just doesn't reconstruct that framebuffer and hence also can't fall over on cleanup. Can you please cherry pick 42a7b088127f (\"drm/i915: Make sure the primary plane is enabled before reading out the fb state\") from -next to 4.0-rc to test whether this is indeed the difference in ducttape? Thanks, Daniel -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch