You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
vkQuake 1.37.0 demo1 1080p hangs the GPU on Apple M1 with r_oit 0 (Unmapped read faults); r_oit 1 is clean #16
vkQuake 1.37.0 demo1 at 1920x1080 (windowed) hangs the GPU on an Apple M1 (G13G) with r_oit 0, the vkQuake default. Each hang is a GPU timeout with an Unmapped read fault. The same run with r_oit 1 completes without any timeout.
Setup
Apple M1 (13-inch), kernel 7.1.12-2-20261013.18-sep-ARCH.
Command: vkquake -basedir <dir> -width 1920 -height 1080 -window -nosound -nostartdemos +vid_vsync 0 +host_maxfps 200 <extra cvars> +timedemo demo1. Each run was killed at the first GPU timeout or after 120 s.
Results (GPU timeout lines added in dmesg per run)
Status 2026-11-05 (w7K): no retest yet. A retest needs an M1 run that goes through the GPU ticket queue, and it has not started. Staying open until there is data: either a retest on the current head, or a close with the result.
Result: demo1 at 1920x1080 with r_oit 0 hung the GPU again. The demo played into the first pickups, then the log stops at "Reallocating dynamic vertex buffers (512 KB)". No result line printed, and the r_oit readback did not print before the hang.
Kernel journal for the same window: 8 GPU timeout events (Timeout count 0 to 7), each with reason: Unmapped, vm_slot: 0x37, and an Attempting recovery line. Event slots 77 and 79 are shown; a later event used slot 78. Excerpt, hostname removed:
Follow-up to my comment linked above with a second run on the same 13-inch M1.
Second run (rev 8 of the test packet, 2026-11-05). Same demo1 timedemo, same vkQuake 1.37.0 binary and pak0 hashes as the packet, mesa 1:26.2.4-1 and vulkan-asahi-omarchy 1:26.2.4.git69bde15340-2, after a clean reboot (new boot id). The runner started the game at 04:40:52 CST with timeout --kill-after=4 15, which sends SIGTERM at 15 seconds. The kernel logged eight GPU timeouts, all stamped 04:41:07 CST, which is 15 seconds after the start.
The run log shows that the timedemo started ("Playing demo from demo1.dem"). The last game line is "Reallocating dynamic vertex buffers (512 KB)", the same line where the first run stopped. No result line was printed. The runner printed no summary: its summary file holds only the start line, and the watch ended with status unknown and no return code.
The kernel log cannot show whether the GPU stopped during the demo or during the runner's termination at 15 seconds. The timeouts are at the bound, so I am not calling this a hang. I am reporting the fault sequence.
Kernel log, abridged. Timestamps, host name, the ASCII art, the Unk lines, and most FaultInfo fields are removed. The lines below are from the first and last events:
The eight events: event 1 is slot 41 at address 0x0 on unit DCMP with three pending events. Events 2 to 8 are slot 43 on unit UL1C, at addresses 0x11fffbc180, 0x11fffbc700, 0x11fffbc200, 0x11fffbd280 (twice), 0x11fffbd200, and 0x11fffbd400. Every event is reason: Unmapped, read: true, vm_slot: 0x17. Recovery was attempted after each. The issue body's "Defaults, timeout 47" sample has the same address and unit as event 8, with vm_slot: 0xf.
First run (rev 5, 2026-11-05, 04:05 CST, earlier boot). Eight timeout events, reason Unmapped, on slots 77, 79 and 78, with vm_slot 0x37, and the same recovery pattern. The journal excerpt is in my comment linked above. The first run queued its readback after the timedemo, so the absence of its readback proves nothing. The first run also stopped at "Reallocating dynamic vertex buffers (512 KB)".
Runner limits
Readback: the second run queued +r_oit 0 +r_oit before the timedemo. The readback did not print to the stdout log. The console file was not copied because the run stopped first, so I cannot say whether it printed to the console.
Summary: neither run produced a result or summary line.
No FPS or pass for either run.
Not tested in this session
No r_oit 1 run in this session. The issue body reports that r_oit 1 completed with no timeouts on this hardware in an earlier session. These two runs do not repeat that comparison.
No other demo, no pak1, and no other Vulkan application on this driver.
Activity
joshuaswarren commentedon Nov 5, 2026
Status 2026-11-05 (w7K): no retest yet. A retest needs an M1 run that goes through the GPU ticket queue, and it has not started. Staying open until there is data: either a retest on the current head, or a close with the result.
joshuaswarren commentedon Nov 5, 2026
Status, 2026-11-05 (single run, 04:05 CST, 13-inch M1 host).
Result: demo1 at 1920x1080 with
r_oit 0hung the GPU again. The demo played into the first pickups, then the log stops at "Reallocating dynamic vertex buffers (512 KB)". No result line printed, and ther_oitreadback did not print before the hang.Versions: kernel
7.1.12-2-20261013.18-sep-ARCH; mesa1:26.2.4-1; vulkan-asahi-omarchy1:26.2.4.git69bde15340-2; vkquake1.37.0-2(binary SHA256a2924ed8...); driver library SHA25640282811....Kernel journal for the same window: 8 GPU timeout events (
Timeout count0 to 7), each withreason: Unmapped,vm_slot: 0x37, and anAttempting recoveryline. Event slots 77 and 79 are shown; a later event used slot 78. Excerpt, hostname removed:Limits:
r_oit 1comparison was run in this session.joshuaswarren commentedon Nov 5, 2026
Follow-up to my comment linked above with a second run on the same 13-inch M1.
Second run (rev 8 of the test packet, 2026-11-05). Same demo1 timedemo, same vkQuake 1.37.0 binary and pak0 hashes as the packet, mesa 1:26.2.4-1 and vulkan-asahi-omarchy 1:26.2.4.git69bde15340-2, after a clean reboot (new boot id). The runner started the game at 04:40:52 CST with
timeout --kill-after=4 15, which sends SIGTERM at 15 seconds. The kernel logged eight GPU timeouts, all stamped 04:41:07 CST, which is 15 seconds after the start.The run log shows that the timedemo started ("Playing demo from demo1.dem"). The last game line is "Reallocating dynamic vertex buffers (512 KB)", the same line where the first run stopped. No result line was printed. The runner printed no summary: its summary file holds only the start line, and the watch ended with status unknown and no return code.
The kernel log cannot show whether the GPU stopped during the demo or during the runner's termination at 15 seconds. The timeouts are at the bound, so I am not calling this a hang. I am reporting the fault sequence.
Kernel log, abridged. Timestamps, host name, the ASCII art, the
Unklines, and most FaultInfo fields are removed. The lines below are from the first and last events:The eight events: event 1 is slot 41 at address 0x0 on unit DCMP with three pending events. Events 2 to 8 are slot 43 on unit UL1C, at addresses 0x11fffbc180, 0x11fffbc700, 0x11fffbc200, 0x11fffbd280 (twice), 0x11fffbd200, and 0x11fffbd400. Every event is
reason: Unmapped,read: true,vm_slot: 0x17. Recovery was attempted after each. The issue body's "Defaults, timeout 47" sample has the same address and unit as event 8, withvm_slot: 0xf.First run (rev 5, 2026-11-05, 04:05 CST, earlier boot). Eight timeout events, reason Unmapped, on slots 77, 79 and 78, with vm_slot 0x37, and the same recovery pattern. The journal excerpt is in my comment linked above. The first run queued its readback after the timedemo, so the absence of its readback proves nothing. The first run also stopped at "Reallocating dynamic vertex buffers (512 KB)".
Runner limits
+r_oit 0 +r_oitbefore the timedemo. The readback did not print to the stdout log. The console file was not copied because the run stopped first, so I cannot say whether it printed to the console.Not tested in this session
r_oit 1run in this session. The issue body reports thatr_oit 1completed with no timeouts on this hardware in an earlier session. These two runs do not repeat that comparison.The vkQuake retest is stopped on this path, and we are not running it again.