On Wed, 18 Nov 2026 18:47:27 -0300, Maíra Canal wrote:
> Mesa issue #16652 [1] reports GPU resets every few minutes on the
> Raspberry Pi 3. They happen when text labels are drawn over their shadows:
> two different threaded fragment shaders, plus untextured single-threaded
> ones, in the same tiles.
> 
> During a hang, the performance counters show four QPUs fetching
> instructions with 0 cache hits, ~6.5M misses per 100 ms, and 0 valid
> instructions executed. This matches HW erratum GFXH-16: the QPUs of a
> slice share one instruction cache and can livelock, evicting each other's
> fills. Since shader code always starts at offset 0 of a page-aligned BO,
> every shader competes for the same cache sets.
> 
> [...]

Applied, thanks!

[1/4] drm/vc4: Fix off-by-one in the shader record BO handle check
      commit: 1fbbd14add401c70c178f0fa13016a3a53ef0de5
[2/4] drm/vc4: Check for a validated shader before reading its thread mode
      commit: 15da41dff1f66a389d238db60a1c19fa83582d07
[3/4] drm/vc4: Start shader code at varying offsets in its BO
      commit: c0e1ed41ad86cf5230d64dc5f2c6d2e3aeb59937
[4/4] drm/vc4: Clear the slice caches before resetting a stalled GPU
      commit: af1cf92e8617a7f7aa24b415596cbf64b76a12e7

Best regards,
- Maíra

Reply via email to