Pi 5: V3D hang with 'MMU error from client PSE ... pte invalid' in Chromium (cage kiosk) on 6.18.50
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- c, linux
- Domain
- computer-graphics, operating-systems
Research direction
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.
Written by the indexing model from the issue text.
Description
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
- Pi 5, Raspberry Pi OS Lite (trixie) arm64, with
cage -s -d -- chromium --kiosk --ozone-platform=wayland <url>on HDMI-A-2 (1280x800). - Open a map page (Freeboard-SK / OpenLayers) and zoom out repeatedly with the touchscreen.
- 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, chromium1: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-eglunder 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.
- Dominant language
- C
- Stars
- 13.3k
- Forks
- 5.5k
- Avg merge
- 4d 10h
- Merged PRs (30d)
- 31
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from raspberrypi/linux
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
raspberrypi/linux#7415 · 2 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
rp1-cfe doesn't forward V4L2_EVENT_SOURCE_CHANGE event from csi-2 sensor driver to userspace appOpen
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
raspberrypi/linux#7399 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
raspberrypi/linux#7357 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
raspberrypi/linux#7054 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
raspberrypi/linux#7770 ·
Maintainers usually reply within 1 day
All issues in raspberrypi/linux
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
LedgerHQ/app-bitcoin-legacy#306 ·
-
[issue]: Ventoy2Disk.sh can leave the end of VTOYEFI unwritten (xzcat | dd without iflag=fullblock)Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
prusa3d/Prusa-Firmware-Buddy#5629 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 3 days
-
Issue PRL on WindowsOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day