From owner-freebsd-current@freebsd.org Sun Aug 30 19:17:43 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 551919C4511 for ; Sun, 30 Aug 2015 19:17:43 +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 11885DB0 for ; Sun, 30 Aug 2015 19:17:43 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.84 (FreeBSD)) (envelope-from ) id 1ZW86l-000ASU-Gv; Sun, 30 Aug 2015 22:17:39 +0300 Date: Sun, 30 Aug 2015 22:17:39 +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: <20150830191739.GZ21849@zxy.spb.ru> References: <55E212F9.6010908@yandex.ru> <20150830130604.GN3158@zxy.spb.ru> <20150830175039.GO3158@zxy.spb.ru> <55E35257.9030201@yandex.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <55E35257.9030201@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 19:17:43 -0000 On Sun, Aug 30, 2015 at 09:58:31PM +0300, Ruslan Makhmatkhanov wrote: > >> 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. > > > > For -STABLE: > > > > r280368 -- All works OK (no error messages, video playback work) > > r280369 -- All works OK (no error messages, video playback work) > > r282141 -- error: [drm:pid5:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer (video don't tested) > > r282199 -- error: [drm:pid12:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung (video don't work) > > No doubt that this is not the root cause, but frankly I haven't that > "GPU hung" messages in my system. I have others like this one triggered > on shutdown: > error: [drm:pid1041:intel_lvds_enable] *ERROR* timed out waiting for > panel to power off > > And this one spamming almost with the same frequency as "pinned buffer": > error: [drm:pid1016:gen6_sanitize_pm] *ERROR* Power management > discrepancy: GEN6_RP_INTERRUPT_LIMITS expected 000d0000, was 180d0000 > > But I had not investigated that yet and not sure they are related. > It's on r287029 head. All of this related to import new DRI/DRM code and such code in Linux have same problems. r282141 in stable related to r279599 and r275209 in current. Can you try to revert r279599?