Re: [REGRESSION 7.2] drm/amdgpu: ~275 SDMA jobs per sparse VA bind since 4cdbba5a (RE Requiem 90->4 fps)
Natalie Vock <[email protected]> Mon, 22 Jun 2026 07:44:02 +0200
| Newsgroups | dev.linux.lists.regressions,org.freedesktop.lists.amd-gfx,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <[email protected]> |
On 6/21/26 22:55, Mikhail Gavrilov wrote:
> Hi Christian, Alex,
>
> git bisect points to
>
> 4cdbba5a16aa ("drm/amdgpu: restructure VM state machine v4")
>
> as the first bad commit (its parent tests fine) for a severe
> interactivity regression.
>
> It was merged during the current 7.2 merge window; it is not in any
> released kernel yet and will first appear in 7.2-rc1.
>
> Symptom: Resident Evil Requiem (re9.exe under VKD3D-Proton, RADV, RX
> 7900 XTX / Navi31, gfx11) drops from ~90 to 3-4 fps the instant the
> camera moves; still scenes are fine. The previous bisect point
> d352990bcaab is smooth.
I already fixed this in a patchset[1] that should be on its way - seems
like it didn't make it into rc1 at least?
Christian, Alex, can you make sure that the first patch from that set,
"drm/amdgpu: Only set bo->moved when the BO was actually moved", is
included in a -fixes PR for 7.2?
For the record, I intentionally did not include a Fixes: tag in this
patchset, because the commit was not merged anywhere but
amd-staging-drm-next at the point of writing, and the same commits in
amd-staging-drm-next and upstream have different SHAs. AFAIU, this also
prevents me from telling regzbot that a proper fix is underway for now.
Not sure if there's a workaround for this?
Best,
Natalie
[1]
https://lore.kernel.org/amd-gfx/[email protected]/