Re: [PATCH 0/2] drm/v3d: Fix system freezes by serializing the GPU reset

On Tue, 28 Jul 2026 23:09:21 -0300, Maíra Canal wrote:
> V3D exposes several independent hardware queues, but it only has a single,
> global reset. Therefore, when a job times out in one queue, the timeout
> handler has to stop, reset and restart the schedulers of every other queue
> as well. As each scheduler queues its timeout work on the system workqueue,
> those handlers run concurrently and can interfere with each other.
> 
> This can be reproduced on a Raspberry Pi 4 or 5 by running glmark2-wayland,
> which keeps the CL queues busy, while a second application triggers a GPU
> reset in the CSD queue every 0.5 seconds. The failure is non-deterministic,
> but it usually shows up after a dozen resets: the DRM scheduler warns about
> a credit imbalance in one of the CL queues,
> 
> [...]

Applied, thanks!

[1/2] drm/v3d: Serialize the scheduler timeout handlers
      commit: 4da94744707b27a3ae1197bdd7127da4505dc5b1

I'll apply "drm/v3d: Remove the now-redundant reset lock" to drm-misc-next when
the former commit is merged to it.

Best regards,
- Maíra