Repository navigation
Conversation
…atomics The RDNA2 ISA (8.1.7) ignores the two low address bits of dword or wider non-formatted accesses in alignment mode DWORD. MXGP 26 (PPSA30839) sets bits with buffer_atomic_or at odd byte offsets, which recorded an unaligned BDA fault and dropped the atomic. A 32-bit buffer atomic now acts on the dword that holds its address; 64-bit atomics off an 8-byte boundary still fault. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Oct 15, 2026
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Saros PPSA07631 v01.000.000 aborts on current main
d92a8dadatsceAudioPropagationSourceGetAudioPath: index 0 out of range (0 audio paths). This draft publishes a focused startup integration of audio path state #56, AGC FS table #6160, and 32-bit atomic alignment #6094, preserving the component authors.The integration remains unstable. A cold startup passed the former exception and rendered the Soltari intro logo at 240 seconds, reaching the planned 300-second stop. A warm run then failed around 100 seconds with GPU virtual-memory faults and Vulkan device loss. The kernel reset recovered the GPU. Title-menu progression and gameplay are unverified.
The component gaps still apply: active acoustic path rendering is unsupported; the FS table currently points to return-only placeholder routines; the console's atomic alignment mode remains unknown. These observations do not validate those assumptions.
Tested
Linux / Ryzen 7950X / Radeon RX 6650 XT, RADV Mesa 26.2.4. Public head
fe380fe0c6905c8407ac73e72cf79eaa09567eb0retains the official SPIRV-Tools pin. The native test head05113b1e3f4b7813ad4a6e43e6a0e2d30f624a53differs only by the common private validator-table teardown repair gitlink.A GPUVM fault has been detected, a read at0xffff80363dda3000, andvkQueueSubmit recorder: Vulkan result -4. The game log identifies an instruction-fetch fault. The kernel log for the same Saros PID (1216766) records TCP texture-cache read faults before the instruction-fetch reports; the first recorded read is at 0x9d3d880000. This ordering does not identify the first failing guest instruction or prove a lifetime defect. No causal attribution to one component has been established.The older Saros stack's ordered-append, runtime image-table, table-call and AJM ratio-ramp dependencies have merged into main. This branch omits its old private shader probes and superseded mouse workaround. No proprietary title assets, screenshots, shader requests or raw logs are committed.
Checklist