panfrost: midgard: PAN_MESA_DEBUG fails

System information

System:
  Host: pmos Kernel: 6.1.24-postmarketos-exynos5 arch: armv7l bits: 32
    compiler: N/A Desktop: GNOME tk: GTK v: 3.90.99 wm: phoc dm: N/A
    Distro: postmarketOS edge
CPU:
  Info: dual core model: ARMv7 v7l variant: cortex-a15 bits: 32 type: MCP
    arch: v7l rev: 4
  Speed: N/A min/max: N/A cores: No per core speed data found. bogomips: N/A
  Features: Use -f option to see features
Graphics:
  Device-1: exynos5250-mali driver: panfrost v: kernel bus-ID: N/A
    chip-ID: samsung:11800000
  Device-2: exynos4212-hdmi driver: N/A bus-ID: N/A chip-ID: samsung:soc
  Display: wayland server: X.org v: 1.21.1.8 with: Xwayland v: 23.1.1
    compositor: phoc driver: N/A display-ID: 0
  Monitor-1: eDP-1 res: 2560x1600 size: N/A
  API: OpenGL v: 2.1 Mesa 23.2.0-devel (git-92a7cba4f2)
    renderer: Mali-T604 (Panfrost) direct-render: Yes

Describe the issue

Starting phoc with PAN_MESA_DEBUG=trace,sync creates

pandecode.dump.0001
pandecode.dump.0003

and stops with this error message:

Access to unknown memory a002000 in ../src/panfrost/lib/genxml/decode_jm.c:289

Backtrace:

pandecode_vertex_compute_geometry_job
  pandecode_dcd
    at pandecode_fetch_gpu_mem(p->state, pan_size(RENDERER_STATE));

Kernel log shows no error. Running kmscube with PAN_MESA_DEBUG doesn't fail and creates dump file for each frame.

I know t604 is not supported yet, but I suspect that other midgard (e.g. T620) are affected as well. This blocks further debugging of drawing issues with T604.