(In reply to comment #18) > If I've got it right, that should be fixed on -next with the per-process > throttling.
Tried drm-intel-next from today, bug still remains.
(In reply to comment #18)
> If I've got it right, that should be fixed on -next with the per-process
> throttling.
Tried drm-intel-next from today, bug still remains.