From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arnd Bergmann Subject: Re: BUG: pin_count exceeded in i915_gem_object_pin Date: Mon, 18 Oct 2010 09:44:23 +0200 Message-ID: <201010180944.23134.arnd@arndb.de> References: <201010172006.37749.arnd@arndb.de> <849307$a1g9u0@azsmga001.ch.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.171]) by gabe.freedesktop.org (Postfix) with ESMTP id 514899E9E9 for ; Mon, 18 Oct 2010 00:43:52 -0700 (PDT) In-Reply-To: <849307$a1g9u0@azsmga001.ch.intel.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org Errors-To: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org To: Chris Wilson Cc: Dave Airlie , dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org On Monday 18 October 2010, Chris Wilson wrote: > On Sun, 17 Oct 2010 20:06:37 +0200, Arnd Bergmann wrote: > > This happened when I killed Xorg as root after plugging in a different screen. > > kdm usually restarts immediately, so I don't know if this was the dying Xorg > > or the new one. > > The new BUG_ON() has spotted that we are leaking pinned fb. I haven't > gotten to the bottom of this entirely yet, in theory this should be fixed > with the unpin fb added when disabling the connector in -next. I am not > totally convinced that explains everything in this case though: > > https://bugs.freedesktop.org/show_bug.cgi?id=29857 Well, this was using -next from friday, which should already include that fix, right? It sounds to me that there is another unpin missing in the close path for the file descriptor. Arnd