Bug#1099032: Flickering on BananaPI CM4 with Arm Mali-G52
Hey,
On Sat, 2025-04-12 at 08:10 +0200, Johannes Schauer Marin Rodrigues wrote:
<snip>
> On Wed, 5 Mar 2025 10:07:15 +0100 Sjoerd Simons <sjoerd@collabora.com> wrote:
> > On Tue, Mar 04, 2025 at 11:42:17AM +0100, Diederik de Haas wrote:
> > > 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).
>
> I built a kernel without 32x8 AFBC disabled and am now back with a machine
> where I observe the regular flicker effect.
>
> I attached the contents of /sys/kernel/debug/dri/ff900000.vpu/framebuffer to
> this mail.
>
> I've also attached the output of `drm_info /dev/dri/card0`.
Right so you're ending up using AFBC:
Modifier: ARM_AFBC(BLOCK_SIZE = 32x8, SPLIT, SPARSE) (0x800000000000062
Which pretty much means that this is an issue with the meson display driver not
handling AFBC entirely correct. Which likely never surfaced before as mesa
wasn't actively using that. So same issue as we're chasing on some MTK devices
atm.
> > 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.
>
> I'm running sway (as shown in the framebuffer attachment).
>
> Thanks!
>
> cheers, josch
Reply to: