Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rsx: Shader interpreter causes a GPU hang when going ingame in Resistance 3 #16587

Open
kd-11 opened this issue Jan 19, 2025 · 4 comments
Open
Assignees
Labels

Comments

@kd-11
Copy link
Contributor

kd-11 commented Jan 19, 2025

Likely broken flow control. The GPU hangs for a few seconds then gets kicked by TDR.

@kd-11 kd-11 added the RSX label Jan 19, 2025
@kd-11 kd-11 self-assigned this Jan 19, 2025
@digant73
Copy link
Contributor

In my HW it happens with Vulkan renderer and Shader Interpreter only shader. R3 immediately crashes with device lost when loading any chapter (black screen and freeze with device-lost logged in the GUI).
That report is more to troubleshoot the device-lost issue in case you can reproduce the issue with that given example I found on R3 while testing Shader Interpreter only shader.

@digant73
Copy link
Contributor

the hang is also present on an AMD iGPU (my laptop). In that case the AMD control panel popups an error message asking to report the crash to AMD. There is no issue at all reported on the RPCS3's GUI. Don't know if you were able to reproduce the issue so you hopefully can fix the issue (maybe the root cause is the same of the general device-lost reported on different games)

@kd-11
Copy link
Contributor Author

kd-11 commented Jan 21, 2025

I can reproduce. However this is not the same cause of the device lost error observed elsewhere. This is just a hang (shader end could not be found within X seconds so the driver kills it). An interpreter is a program that runs another program inside it so that's not totally unexpected. The same is not possible with a recompiled program though. If it had no exit the recompiler itself would have crashed. It's more likely some poorly implemented interpreter instruction wrecked the virtualized shader state.

@digant73
Copy link
Contributor

thanks for the clarification

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants