Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752714AbbB1VKZ (ORCPT ); Sat, 28 Feb 2015 16:10:25 -0500 Received: from mail.fireflyinternet.com ([87.106.93.118]:55955 "EHLO fireflyinternet.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752280AbbB1VKY (ORCPT ); Sat, 28 Feb 2015 16:10:24 -0500 X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=78.156.65.138; Date: Sat, 28 Feb 2015 21:10:13 +0000 From: Chris Wilson To: Andrey Skvortsov , 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: <20150228211013.GB13459@nuc-i3427.alporthouse.com> Mail-Followup-To: Chris Wilson , Andrey Skvortsov , 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> <20150223212031.GI15204@nuc-i3427.alporthouse.com> <20150223234245.GA24485@phenom.ffwll.local> <20150228122037.GA12590@nest> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150228122037.GA12590@nest> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1107 Lines: 23 On Sat, Feb 28, 2015 at 03:20:37PM +0300, Andrey Skvortsov wrote: > Unfortunately this is not the last bug, that breaks i915/drm working > on my laptop. Sometimes system successfully loads with couple warnings mentioned in > previous mail: > > [ 26.922953] WARNING: CPU: 1 PID: 767 at drivers/gpu/drm/i915/i915_gem.c:4525 i915_gem_free_object+0x13f/0x288 [i915]() > [ 26.922954] WARN_ON(obj->frontbuffer_bits) That's inocuous, but for the serious hang, you may want to try video=SVIDEO-1:d on the kernel commandline to workaround the hang. (Check /sys/class/drm/card/ for the actual name of the connector for TV). I think Ville mentioned he was looking/looked at the atomic-vs-load_detect changes that is at the heart of the issue here. (Admittedly he did say it was worthy of a drink or two.) -Chris -- Chris Wilson, Intel Open Source Technology Centre -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/