10-21-2020, 03:02 AM
Hint to everyone here: This issue isn't going to automatically fix itself.
I haven't been able to reproduce this myself, so someone here who has the problem will have to help find the problem by bisecting.
You'll have to use git bisect on Mesa, with a "good" commit of ac6b8e42ce2 and a "bad" commit of 20a4235c4c9 (man git-bisect for docs).
Configure Mesa from the build directory like this:
Compile and install with `ninja; sudo ninja install`
Install ccache beforehand to speed up the bisect process significantly.
Once an issue is narrowed down to a specific commit, it's usually pretty easy to find what the problem is and fix it.
I haven't been able to reproduce this myself, so someone here who has the problem will have to help find the problem by bisecting.
You'll have to use git bisect on Mesa, with a "good" commit of ac6b8e42ce2 and a "bad" commit of 20a4235c4c9 (man git-bisect for docs).
Configure Mesa from the build directory like this:
Code:
meson -Dgallium-drivers=panfrost,kmsro -Dvulkan-drivers= -Db_ndebug=false --buildtype=plain
Compile and install with `ninja; sudo ninja install`
Install ccache beforehand to speed up the bisect process significantly.
Once an issue is narrowed down to a specific commit, it's usually pretty easy to find what the problem is and fix it.