Re: [drm:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer

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)
> _at__at_ -2528,7 +2528,7 _at__at_
>  		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.