System Information

• GPU: Intel UHD Graphics 620 (Kaby Lake GT2, PCI ID: 0x5917)
• OS / Kernel: CachyOS (Kernel 7.1.4-cachyos)
• Mesa Driver Version: Mesa ANV 26.1.5 / 26.3-git
• VKD3D-Proton Version: vkd3d-proton 3.0.1 / 3.1.0+
• Proton / Wine Version: Proton-CachyOS Latest

Describe the Bug

On Intel Gen9/9.5 graphics hardware, multiple complex Direct3D 12 titles translated via VKD3D-Proton trigger a deterministic, fatal GPU ring hang and preemption timeout during command buffer execution loops.

Affected titles:

• Resident Evil 2 Remake
• Resident Evil Village
• Red Dead Redemption
• Ratchet & Clank: Rift Apart
• Ghostrunner
• Pretty much EVERY GAME THAT USES DX12

Terminal Log Snippet:

err:vkd3d-proton:vkd3d_wait_for_gpu_timeline_semaphore: Failed to wait for Vulkan timeline semaphore, vr -4
i915: GPU HANG: ecode 9:1:85ddfffa
i915: Resetting rcs0 for preemption time out

The Cross-Layer Isolation Triage

Extensive deep-dive analysis between the driver state tracker, runtime environment variables, and memory layers confirms the following parameters:

1. The 'reemit' Cache Padding Mask: Setting the Mesa environment variable INTEL_DEBUG=reemit completely mitigates the hang for Resident Evil 2, passing full playthrough verification. Concurrently, INTEL_DEBUG=reemit,sync,stall eliminates the hang on Red Dead Redemption 1 (at a heavy 20-30% frame allocation performance penalty).
2. Hardware Architecture Divergence: The hang is strictly isolated to legacy Intel architectures (Gen9/9.5). Running the exact same software ecosystem, configuration layers, and Proton runtimes on Gen12 configurations (Tiger Lake, Alder Lake) displays total stability.
3. Mesa Maintainer Triage Context: Upstream cross-referencing with Intel Mesa driver maintainers (Lionel Landwerlin, ref: Mesa issue #14348 / #15474) establishes that certain VKD3D-Proton resource allocation translations are triggering out-of-bounds descriptor array accesses.

Architectural Friction: Why this hits Gen9

On newer Intel execution layers (Gen12+), the ANV driver configures a virtualized hardware scratch page memory abstraction space. When a translated shader emits an out-of-bounds descriptor index read, the modern hardware silently catches and mirrors the request into the zeroed scratch space—manifesting as minor visual artifacts while avoiding crashes.

Conversely, older Gen9/9.5 hardware features zero hardware memory redirection virtualization layers for invalid indices. When VKD3D-Proton emits these translated shader streams onto Kaby Lake silicons, the hardware Memory Management Unit page-faults on the unmapped address space, stalling rcs0. Forcing a global reemit through Mesa pads and realigns instruction memory shapes enough to mask the illegal access vector, but breaks driver execution performance loops.

Proposed Request / Solution

Because this failure vector depends directly on illegal out-of-bounds index generation paths during DX12-to-Vulkan pipeline state construction, could an aggressive descriptor array boundary tracking check, index clamp pass, or explicit fallback safety block be implemented inside VKD3D-Proton when parsing pipelines on legacy Intel hardware configurations?

Workarounds Tried (That Failed to Prevent the Fault)

• VKD3D_CONFIG=virtual_heaps,no_upload_hvv,single_queue -> No behavioral modification.
• preempt_timeout_ms=3000 -> Artificially shifts the crash window timeline but fails to prevent the hard hardware trap.
• anv_enable_scratch_page=true -> Inoperable/No-Op on Gen9 hardware architectures.