[6.1][regression] after commit dd80d9c8eecac8c516da5b240d01a35660ba6cb6 some games (Cyberpunk 2077, Forza Horizon 4/5) hang at start
Christian König
christian.koenig at amd.com
Mon Nov 14 13:22:37 UTC 2022
Hi Mikhail,
Am 02.11.22 um 14:43 schrieb Christian König:
> Am 02.11.22 um 14:36 schrieb Mikhail Gavrilov:
>> On Tue, Nov 1, 2022 at 10:52 PM Christian König
>> <ckoenig.leichtzumerken at gmail.com> wrote:
>> [SNIP]
>> But the most interesting thing is that all previous kernels 6.0, 5.19
>> are affected by the problem. It is not enough to revert the
>> dd80d9c8eecac8c516da5b240d01a35660ba6cb6 commit.
>
> Yeah, that totally confirms what I expected. The context lock just
> hides the problem because userspace tended to use the same context.
>
> What the application now seems to do is to use multiple contexts for
> its submission and in this case re-adding the lock doesn't even help.
>
> Thanks for that information, gets me a lot closer to a solution.
I've found and fixed a few problems around the userptr handling which
might explain what you see here.
A series of four patches starting with "drm/amdgpu: always register an
MMU notifier for userptr" is under review now.
Going to give that a bit cleanup later today and will CC you when I send
that out. Would be nice if you could give that some testing.
Thanks,
Christian.
>
> Regards,
> Christian.
More information about the amd-gfx
mailing list