I was finally able to spend a bit of time on this. Unfortunately, there’s
not much to report back.
Em terça-feira, 8 de junho de 2021, às 15:13:36 -03, Thiago Jung Bauermann
escreveu:
> Em terça-feira, 8 de junho de 2021, às 10:30:24 -03, Alex Deucher
escreveu:
> > Can you narrow down which specific firmware file causes the problem?
>
> Ok, I will try.
I don’t think I can narrow down which firmware file causes the problem,
because I don’t have a last known good version. All firmware files that I
tested (Ubuntu versions 1.190.5, 1.197 and latest linux-firmware.git)
immediately trigger the bug when I try the only reliable reproducer I know
(i.e., running flatpak’s com.github.quaternion package).
Since it can take several days for the bug to happen if I just use the
machine normally, it would take weeks to narrow down which of the picasso_*
files is more stable relative to the others. And even then, I wouldn’t be
sure about it.
> > I think it may be related to a change in mesa. Specifically mesa
> > commit
> > 820dec3f7c7. For more info see
> > https://gitlab.freedesktop.org/mesa/mesa/-/issues/4866
>
> I’ll run with Mario’s build of Mesa with that patch backported.
> Thanks, Mario!
I’m running with the Mesa build from Mario’s PPA now. If I don’t see any
issue within two weeks, I think it will be possible to say that the bug is
gone, or at least much harder to hit.
I can’t use my reproducer in this case, because I can’t change the Mesa
version inside the flatpak image.
I was finally able to spend a bit of time on this. Unfortunately, there’s
not much to report back.
Em terça-feira, 8 de junho de 2021, às 15:13:36 -03, Thiago Jung Bauermann
escreveu:
> Em terça-feira, 8 de junho de 2021, às 10:30:24 -03, Alex Deucher
escreveu:
> > Can you narrow down which specific firmware file causes the problem?
>
> Ok, I will try.
I don’t think I can narrow down which firmware file causes the problem, quaternion package).
because I don’t have a last known good version. All firmware files that I
tested (Ubuntu versions 1.190.5, 1.197 and latest linux-firmware.git)
immediately trigger the bug when I try the only reliable reproducer I know
(i.e., running flatpak’s com.github.
Since it can take several days for the bug to happen if I just use the
machine normally, it would take weeks to narrow down which of the picasso_*
files is more stable relative to the others. And even then, I wouldn’t be
sure about it.
> > I think it may be related to a change in mesa. Specifically mesa /gitlab. freedesktop. org/mesa/ mesa/-/ issues/ 4866
> > commit
> > 820dec3f7c7. For more info see
> > https:/
>
> I’ll run with Mario’s build of Mesa with that patch backported.
> Thanks, Mario!
I’m running with the Mesa build from Mario’s PPA now. If I don’t see any
issue within two weeks, I think it will be possible to say that the bug is
gone, or at least much harder to hit.
I can’t use my reproducer in this case, because I can’t change the Mesa
version inside the flatpak image.