drm/i915: Remove the conflicting BUG_ON()

We now attempt to free "active" objects following a GPU hang as either
the GPU will be reset or the hang is permenant. In either case, the GPU
writes will not be flushed to main memory and it should be safe to
return that memory back to the system.

The BUG_ON(active) is thus overkill and can erroneously fire after a
EIO.

Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Signed-off-by: Eric Anholt <eric@anholt.net>

authored by Chris Wilson and committed by Eric Anholt 156dadc1 90eb77ba

-2
-2
drivers/gpu/drm/i915/i915_gem.c
··· 1979 * cause memory corruption through use-after-free. 1980 */ 1981 1982 - BUG_ON(obj_priv->active); 1983 - 1984 /* release the fence reg _after_ flushing */ 1985 if (obj_priv->fence_reg != I915_FENCE_REG_NONE) 1986 i915_gem_clear_fence_reg(obj);
··· 1979 * cause memory corruption through use-after-free. 1980 */ 1981 1982 /* release the fence reg _after_ flushing */ 1983 if (obj_priv->fence_reg != I915_FENCE_REG_NONE) 1984 i915_gem_clear_fence_reg(obj);