Been fighting this bug for a while now, but since I updated rocm to 7.2 DaVinci resolve died.
Took me a while to track down that it was rocm until I ran across an endeavour os post about it. But if you’ve noticed that resolve stopped loading and not showing errors, Try downgrading rocm and trying again.
Endevour OS Post: https://forum.endeavouros.com/t/can-t-use-davinci-resolve-studio-crash-to-desktop/77870/11
AUR post which the Endevour OS post was referring to: https://aur.archlinux.org/packages/davinci-resolve-studio#comment-1058336
If you need to downgrade your amdgpu-install package, AMD’s repo link is here https://repo.radeon.com/amdgpu-install/


I am curious if it’s a Davinci issue or a AMD one. Would love to hear the results.
I don’t suspect it’s davinci resolve. This is likely due to rocm-opencl.
It’s a long weekend, so I likely won’t hear back from my colleagues until Tuesday at the earliest
have filed this to the ROCm team, hope to get someone looking into this tomorrow.
Thank you, hopefully it’s something small
We’ll find out. It’s filed to the public issue tracker, which is a nice change of pace. Hope you can stay appraised of the progress from the following link:
https://github.com/ROCm/ROCm/issues/5970
Good news, seems there’s an existing internal ticket covering this defect. It’s an application-side issue pertaining to libProResRAW.so.
I believe we’re shipping a workaround at the ROCm framework side in 7.2.1
That is fantastic to hear!
Someone on the github issue thread has been asking for clinfo output on affected systems, theorising that client issues are caused by issues with vendor detection.
This is a bit of an ask, but if it’s quick to jump forward and back between ROCm releases on your setup, would you be able to pass your clinfo output from 7.2.0 into the ticket linked above? No worries if not
More than happy to, though it might be later today thing
no hurry at all, thanks a bunch!
Posted, I also had an error on the output
Memory access fault by GPU node-1 (Agent handle: 0x5a020e3bce10) on address 0x7f86a34eb000. Reason: Page not present or supervisor privilege. Aborted (core dumped)