From owner-freebsd-current@freebsd.org  Sun Aug 30 21:25:43 2015
Return-Path: <owner-freebsd-current@freebsd.org>
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 75DD79C69A7
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Sun, 30 Aug 2015 21:25: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 33182F79
 for <freebsd-current@freebsd.org>; Sun, 30 Aug 2015 21:25:43 +0000 (UTC)
 (envelope-from slw@zxy.spb.ru)
Received: from slw by zxy.spb.ru with local (Exim 4.84 (FreeBSD))
 (envelope-from <slw@zxy.spb.ru>)
 id 1ZWA6e-000Gro-Lt; Mon, 31 Aug 2015 00:25:40 +0300
Date: Mon, 31 Aug 2015 00:25:40 +0300
From: Slawa Olhovchenkov <slw@zxy.spb.ru>
To: Ruslan Makhmatkhanov <cvs-src@yandex.ru>
Cc: FreeBSD Current <freebsd-current@freebsd.org>
Subject: Re: [drm:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned
 buffer
Message-ID: <20150830212540.GA21849@zxy.spb.ru>
References: <55E212F9.6010908@yandex.ru> <20150830130604.GN3158@zxy.spb.ru>
 <20150830175039.GO3158@zxy.spb.ru> <55E35257.9030201@yandex.ru>
 <20150830191739.GZ21849@zxy.spb.ru> <55E36EAE.60606@yandex.ru>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <55E36EAE.60606@yandex.ru>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-SA-Exim-Connect-IP: <locally generated>
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
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Aug 2015 21:25:43 -0000

On Sun, Aug 30, 2015 at 11:59:26PM +0300, Ruslan Makhmatkhanov wrote:

> Slawa Olhovchenkov wrote on 08/30/2015 22:17:
> > On Sun, Aug 30, 2015 at 09:58:31PM +0300, Ruslan Makhmatkhanov wrote:
> 
> >> 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?
> 
> You are right. After reverting r279599 two of this messages ("timed out 
> waiting for panel to power off" and "unbind pinned buffer") disappeared, 
> while "Power management discrepancy" is still there. Should I try to 
> revert r275209 too?

I think r275209 is not relevant here.