From owner-freebsd-current@freebsd.org Sun Aug 30 13:06:14 2015 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 36CE69C6B7D for ; Sun, 30 Aug 2015 13:06:14 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E746CCBF for ; Sun, 30 Aug 2015 13:06:13 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.84 (FreeBSD)) (envelope-from ) id 1ZW2JA-000NQJ-Ju; Sun, 30 Aug 2015 16:06:04 +0300 Date: Sun, 30 Aug 2015 16:06:04 +0300 From: Slawa Olhovchenkov To: Ruslan Makhmatkhanov Cc: FreeBSD Current Subject: Re: [drm:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer Message-ID: <20150830130604.GN3158@zxy.spb.ru> References: <55E212F9.6010908@yandex.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <55E212F9.6010908@yandex.ru> User-Agent: Mutt/1.5.23 (2014-03-12) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Aug 2015 13:06:14 -0000 On Sat, Aug 29, 2015 at 11:15:53PM +0300, Ruslan Makhmatkhanov wrote: > Hello, > > I'm getting tons of this in /var/log/messages: > error: [drm:pid9:i915_gem_object_unbind] *ERROR* Attempting to unbind > pinned buffer > > As far I understand [1], this case is harmless and there is no point to > print it with DRM_ERROR - DRM_DEBUG is sufficient. Can we please change > it in our tree like it done in patch attached? Thanks. > > PS. In Linux 3.8 [2] this check was changed by removing the warning > altogether and just returning -EBUSY, so may be we can do just this to > reduce the diff ;). > > [1] https://bugs.freedesktop.org/show_bug.cgi?id=50075 > [2] > http://lxr.free-electrons.com/source/drivers/gpu/drm/i915/i915_gem.c?v=3.8 > > -- > Regards, > Ruslan > > T.O.S. Of Reality > Index: sys/dev/drm2/i915/i915_gem.c > =================================================================== > --- sys/dev/drm2/i915/i915_gem.c (revision 287214) > +++ sys/dev/drm2/i915/i915_gem.c (working copy) > @@ -2528,7 +2528,7 @@ > return 0; > > if (obj->pin_count) { > - DRM_ERROR("Attempting to unbind pinned buffer\n"); > + DRM_DEBUG("Attempting to unbind pinned buffer\n"); > return -EINVAL; > } > I think this is not root of cause, this is only cause of other error: === dmesg ==== info: [drm] Initialized i915 1.6.0 20080730 for drmn0 on minor 0 error: [drm:pid12:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung info: [drm] capturing error event; look for more information in sysctl hw.dri.0.info.i915_error_state error: [drm:pid0:i915_reset] *ERROR* Failed to reset chip. ============== This cause: === Xorg.log ==== [ 51.010] (EE) intel(0): Detected a hung GPU, disabling acceleration. [ 51.010] (EE) intel(0): When reporting this, please include i915_error_state from debugfs and the full dmesg. ================= and after this you see Attempting to unbind pinned buffer. I am see this in STABLE after Aug upgrade. I am don't see this at 2014-Oct STABLE.