Skip to content

wrapper: capture Content Warning semaphore device loss - #48

Open
butilly wants to merge 1 commit into
wrapper-25from
fix/content-warning-wrapper-diagnostic
Open

butilly wants to merge 1 commit into
wrapper-25from
fix/content-warning-wrapper-diagnostic

Conversation

@butilly

@butilly butilly commented Oct 30, 2026

Copy link
Copy Markdown
Collaborator

Game: Content Warning; executable: Content Warning.exe; thread: 1565788402815733800. Mali-G57 r34 through Wrapper and DXVK-Sarek 1.11 reports Failed to wait for semaphore: VK_ERROR_DEVICE_LOST (debug_log L2004); no driver fault report with Mesa debug flags. Existing WRAPPER_DIAG fault reporting runs only after failed QueueSubmit/QueueSubmit2; WaitSemaphores is a silent trampoline. Add executable-scoped GN-WRAPPER-LOSS-v1 logging for the first eight waits/submits and first device loss per device, including native result, queue, submit sequence, batch/command counts and wait values. Request existing EXT_device_fault report on host-wait loss too, and explicitly report unavailable fault support. Preserve submission order, timeout, native return values, Proton 9 ARM64EC and Sarek. Review: git diff --check passed; CI compilation required. Next report must show diagnostic marker and first failing API; distinguish wrapper-base behavior changes from instrumentation. Diagnostic 1 of 2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant