• Bug#1099032: Flickering on BananaPI CM4 with Arm Mali-G52

    From Johannes Schauer Marin Rodrigues@21:1/5 to martin@lichtvoll.de on Sat Mar 1 17:50:01 2025
    --===============7068663468702726513==
    Content-Type: text/plain; charset="utf-8"
    MIME-Version: 1.0
    Content-Transfer-Encoding: quoted-printable

    Control: tag -1 + patch

    Hi,

    MNT Reform forum user deianara identified upstream commit e0f48568c7f2a638213dee317fde03c23775556f as the origin of the regression on BananaPI CM4. I verified that reverting this commit on top of mesa 25 indeed fixes the problem. Patch attached.

    On Thu, 27 Feb 2025 18:01:04 +0100 Martin Steigerwald <martin@lichtvoll.de> wrote:
    Flickering and various graphics related glitches with
    mesa 25.0.0-1 on ThinkPad T14 AMD Gen 5 with AMD Ryzen 7 PRO 8840U
    w/ Radeon 780M Graphics:

    your flicker effects are probably unrelated to the ones that this bug is about because the fix for this bug is a change in mesa's panfrost driver which is unrelated to your radeon card.

    Thanks!

    cheers, josch
    --==============p68663468702726513=Content-Type: text/x-diff; charset="utf-8" MIME-Version: 1.0
    Content-Transfer-Encoding: quoted-printable
    Content-Disposition: attachment; filename="mesa.debdiff"; maxlinelen="78"

    diff -Nru mesa-25.0.0/debian/changelog mesa-25.0.0/debian/changelog
    --- mesa-25.0.0/debian/changelog 2025-02-23 10:22:33.000000000 +0100
    +++ mesa-25.0.0/debian/changelog 2025-03-01 11:27:41.000000000 +0100
    @@ -1,3 +1,11 @@
    +mesa (25.0.0-1.1) UNRELEASED; urgency=medium
    +
    + * Non-maintainer upload.
    + * Revert upstream commit e0f48568c7f2a638213dee317fde03c23775556f to fix
    + flickering on BananaPI CM4 with Arm Mali-G52 (Closes: #1099032)
    +
    + -- <mmmm@localhost> Sat, 01 Mar 2025 11:27:41 +0100
    +
    mesa (25.0.0-1) unstable; urgency=medium

    * New upstream release.
    diff -Nru mesa-25.0.0/debian/patches/0001-Revert-panfrost-Advertise-support-for-AFBC-32x8-spar.patch mesa-25.0.0/debian/patches/0001-Revert-panfrost-Advertise-support-for-AFBC-32x8-spar.patch
    --- mesa-25.0.0/debian/patches/0001-Revert-panfrost-Advertise-support-for-AFBC-32x8-spar.patch 1970-01-01 01:00:00.000000000 +0100
    +++ mesa-25.0.0/debian/patches/0001-Revert-panfrost-Advertise-support-for-AFBC-32x8-spar.patch 2025-03-01 11:27:26.000000000 +0100
    @@ -0,0 +1,44 @@
    +From 3b296fd4936c14f91d1ff4
  • From Diederik de Haas@21:1/5 to Johannes Schauer Marin Rodrigues on Tue Mar 4 12:00:01 2025
    --ae58cad244cf39da2503241b9a5fe4053c9be319c2c6dc609e7e13a6daa4 Content-Transfer-Encoding: quoted-printable
    Content-Type: text/plain; charset=UTF-8

    Hi,

    On Thu Feb 27, 2025 at 2:30 PM CET, Johannes Schauer Marin Rodrigues wrote:
    Source: mesa
    Version: 25.0.0-1
    Severity: serious

    this is a regression from mesa 24.3.4-3. I'm filing with RC severity because this affects not only me but also other users on the BananaPI [1] and by

    I have a Pine64 PineTab2 (rk3566) which also has an Arm Mali-G52 GPU and
    I was NOT able to reproduce the issue. I played the exact same MNT video
    in Firefox, but also playing a (local) video in mpv didn't show any
    issues. I'm using sway as wayland compositor.

    So I looked a bit further into the differences and noticed it's using an Amlogic A311D SoC. That the bisected commit mentions "Some MTK display controller drivers" indicates the problem could be in that direction.

    But even before reading about the bisected commit, I had a look at the
    dts[i] files for BananaPI (``arch/arm64/boot/dts/amlogic/meson-g12b*``).
    There was 1 property in particular that I was 'missing' and that was ``mali-supply``, so I'd recommend to test if adding that makes a
    difference. See also the example in the DT binding schema: ``Documentation/devicetree/bindings/gpu/arm,mali-bifrost.yaml``

    preventing mesa from transitioning to testing, downgrading mesa is much easier
    than when having to cherry-pick it from snapshot.d.o.

    I'll leave possibly changing the severity up to the maintainer, but I
    don't think "making it easier to downgrade" is a valid reason in itself.

    You can add a line to sources.list referencing a particular date in the snapshot.d.o archive and then constructing (and sharing in the MNT
    forums) a line/command like this:
    ``aptitude install <mesa-pkg1>=<24.x> <mesa-pkg2>=<24.x>``

    HTH,
    Diederik

    [1] https://community.mnt.re/t/display-flickering-on-pocket-reform-related-to-mesa-25-0-0/3133


    --ae58cad244cf39da2503241b9a5fe4053c9be319c2c6dc609e7e13a6daa4
    Content-Type: application/pgp-signature; name="signature.asc"

    -----BEGIN PGP SIGNATURE-----

    iHUEABYIAB0WIQT1sUPBYsyGmi4usy/XblvOeH7bbgUCZ8bZDgAKCRDXblvOeH7b bstSAQC9KqEQchV5ii54SSSLGSxU6ldXg8uEEm1kUjK6k2XacgD8DVoNkyyLvtXE fyjAbo+twHnY3yQlFcASvfSZrUfPBQ0=7/1M
    -----END PGP SIGNATURE-----

    --ae58cad244cf39da2503241b9a5fe4053c9be319c2c6dc609e7e13a6daa4--

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Sjoerd Simons@21:1/5 to Diederik de Haas on Wed Mar 5 10:40:02 2025
    On Tue, Mar 04, 2025 at 11:42:17AM +0100, Diederik de Haas wrote:
    Hi,

    On Thu Feb 27, 2025 at 2:30 PM CET, Johannes Schauer Marin Rodrigues wrote:
    Source: mesa
    Version: 25.0.0-1
    Severity: serious

    this is a regression from mesa 24.3.4-3. I'm filing with RC severity because
    this affects not only me but also other users on the BananaPI [1] and by

    I have a Pine64 PineTab2 (rk3566) which also has an Arm Mali-G52 GPU and
    I was NOT able to reproduce the issue. I played the exact same MNT video
    in Firefox, but also playing a (local) video in mpv didn't show any
    issues. I'm using sway as wayland compositor.

    So I looked a bit further into the differences and noticed it's using an Amlogic A311D SoC. That the bisected commit mentions "Some MTK display controller drivers" indicates the problem could be in that direction.

    Given the bisected commit, this is not actually a bug in panfrost/mesa. This is likely a bug in the display controller not handling the relevant AFBC formats correctly.

    We're seeing the same on Mediatek devices at the moment. If you could dump the output of /sys/kernel/debug/dri/*/framebuffer while running into these issues that would be very helpful (as that will show the modifiers in use).

    It would also be helpful if you could mention the display stack you're using (e.g. which compositor). At least in my testing gnome wasn't impacted as that didn't seem to be using modifiers. If you're using weston you could try with WESTON_DISABLE_GBM_MODIFIERS=1 set in the environment to avoid modifier usage.

    Regards,
    Sjoerd

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)