A thread checks the ring every 500 ms as msm's hangcheck_handler does:
no fence progress with work pending and no CP progress (a6xx_progress,
at most three retries) is a hang. Recovery follows recover_worker: the
hung job's VM takes the fault and, unless it is the kernel's, becomes
unusable; the fence moves past it; the board's restart hook resets the
GPU and runs hw_init and CP init on the same ring; every later job is
replayed with its own fence. Clients read the global fault count plus
their own VM's, so only the guilty client sees its device lost. The
ring gains restart, unfenced submission, a6xx_idle, progress state and
the GBIF bus halt; CP init can run unfenced.