Pi 5: V3D hang with 'MMU error from client PSE ... pte invalid' in Chromium (cage kiosk) on 6.18.50

Aperta
  • Qualcosa non va?
#7,721 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
35/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
c, linux
Ambito
computer-graphics, operating-systems

Direzione di ricerca

Start by reading the V3D hang and MMU error logs in the report, then compare the earlier fixes in #7400 and #7503 with the prior reports #7397 and #7381. The issue does not identify a source file or provide an on-demand reproduction, so investigation will likely require tracing V3D kernel driver state and may need the suggested GPU tests or state dump. Done means identifying and fixing the cause of the intermittent hang, then confirming the GPU no longer resets under the reported workload.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Describe the bug

On a Pi 5 running Chromium in a cage kiosk session, the V3D GPU hangs while zooming out on a map page. The GPU is reset 6 times in about 6 s, with one MMU error from client PSE ... pte invalid. Chromium's GPU process crashes three times, falls back to --use-gl=disabled, and the screen stays black until the kiosk session is restarted.

The page is Freeboard-SK, an OpenLayers chart plotter. A radar overlay that renders with WebGL2 was off at the time, so the GPU load was Chromium's normal compositing and rasterization of a map while zooming out.

The kernel already includes #7400 and #7503, which fixed the earlier pte invalid hangs in #7397 and #7381.

Steps to reproduce the behaviour
  1. Pi 5, Raspberry Pi OS Lite (trixie) arm64, with cage -s -d -- chromium --kiosk --ozone-platform=wayland <url> on HDMI-A-2 (1280x800).
  2. Open a map page (Freeboard-SK / OpenLayers) and zoom out repeatedly with the touchscreen.
  3. After several hours of uptime it hung once, on a zoom-out. I can't reproduce it on demand yet.
Device (s)

Raspberry Pi 5

System
  • Raspberry Pi 5 Model B Rev 1.0, 8 GB (revision d04170)
  • Kernel 6.18.50+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.18.50-1+rpt1 (2026-09-11)
  • Firmware 1accd665, bootloader EEPROM 2026-09-25 (up to date), raspi-firmware 1:1.20260915-1
  • Mesa 26.2.2-1~bpo13+0~rpt1, chromium 1:155.0.8059.79-1~deb13u1+rpt1, rpi-chromium-mods 20260211
  • config.txt: stock (dtoverlay=vc4-kms-v3d, max_framebuffers=2, disable_fw_kms_setup=1, arm_boost=1)
  • vcgencmd get_throttled = 0xe0000 (no under-voltage); SoC at about 65 °C at the time of the hang
Logs
[Tue Oct 27 14:08:45 2026] v3d 1002000000.v3d: [drm:v3d_reset [v3d]] *ERROR* Resetting GPU for hang.
[Tue Oct 27 14:08:45 2026] v3d 1002000000.v3d: [drm:v3d_reset [v3d]] *ERROR* V3D_ERR_STAT: 0x00000000
[Tue Oct 27 14:08:45 2026] v3d 1002000000.v3d: MMU error from client PSE (57) at 0x1b100320, pte invalid
[Tue Oct 27 14:08:46 2026] v3d 1002000000.v3d: [drm:v3d_reset [v3d]] *ERROR* Resetting GPU for hang.
[Tue Oct 27 14:08:46 2026] v3d 1002000000.v3d: [drm:v3d_reset [v3d]] *ERROR* V3D_ERR_STAT: 0x00001000
[Tue Oct 27 14:08:46 2026] v3d 1002000000.v3d: [drm:v3d_reset [v3d]] *ERROR* Resetting GPU for hang.
[Tue Oct 27 14:08:46 2026] v3d 1002000000.v3d: [drm:v3d_reset [v3d]] *ERROR* V3D_ERR_STAT: 0x00001000
[Tue Oct 27 14:08:47 2026] v3d 1002000000.v3d: [drm:v3d_reset [v3d]] *ERROR* Resetting GPU for hang.
[Tue Oct 27 14:08:47 2026] v3d 1002000000.v3d: [drm:v3d_reset [v3d]] *ERROR* V3D_ERR_STAT: 0x00001000
[Tue Oct 27 14:08:50 2026] v3d 1002000000.v3d: [drm:v3d_reset [v3d]] *ERROR* Resetting GPU for hang.
[Tue Oct 27 14:08:50 2026] v3d 1002000000.v3d: [drm:v3d_reset [v3d]] *ERROR* V3D_ERR_STAT: 0x00001000
[Tue Oct 27 14:08:51 2026] v3d 1002000000.v3d: [drm:v3d_reset [v3d]] *ERROR* Resetting GPU for hang.
[Tue Oct 27 14:08:51 2026] v3d 1002000000.v3d: [drm:v3d_reset [v3d]] *ERROR* V3D_ERR_STAT: 0x00001000

Chromium GPU process afterwards: --gpu-recent-crash-count=3 ... --render-node-override=/dev/dri/card1 --use-angle=gles ... --use-gl=disabled

Additional context
  • Earlier in the same boot, starting Chromium with --use-angle=gles-egl under cage produced 16 similar resets within a minute (09:14–09:15). That flag was then removed, and the GPU ran normally for about five hours before the hang above, with stock flags.
  • The two previous boots had no GPU hangs. After a reboot there have been none so far.
  • The same software stack on another Pi doesn't show this, so a board-specific cause (as discussed in #7657) is possible. I'm happy to run a GPU test (e.g. piglit / deqp) or collect a V3D state dump if that helps.
Lingua principale
C
Stelle
13.3k
Fork
5.5k
Merge medio
1g 7h
PR unite (30g)
16

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di raspberrypi/linux

Tutte le issue di raspberrypi/linux

Issue simili

Altre issue su C

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.