Hi Andrzej,
On Tue, Dec 05, 2023 at 02:09:37PM +0100, Andrzej Hajda wrote:
> After i915_active_unlock_wait i915_active can be still non-idle due
> to barrier async handling in signal_irq_work. As a result one can observe
> following errors:
> bcs0: heartbeat pulse did not flush idle tasks
> *ERROR
After i915_active_unlock_wait i915_active can be still non-idle due
to barrier async handling in signal_irq_work. As a result one can observe
following errors:
bcs0: heartbeat pulse did not flush idle tasks
*ERROR* pulse active pulse_active [i915]:pulse_retire [i915]
*ERROR* pulsecount: 0
*ERRO