On Mon, Nov 9, 2026 at 2:34 PM Gaurav Suman via B4 Relay <[email protected]> wrote: > > From: Gaurav Suman <[email protected]> > > On an Adreno 640 (SM8150, LG G8x) GNOME Shell triggers SMMU > translation faults with source=CCU, about ten per login, when > freedreno uses GMEM (binning) rendering. FD_MESA_DEBUG=nogmem or > =inorder hides them. > > A stall-on-fault capture decoded with crashdec shows the faulting > address at an exact 64 KiB boundary (FAR 0x110690000) while the pass > drew to MRT0 at 0x110695000 and depth at 0x11069f000, all in that > 64 KiB block. The block start belonged to the unmapped tail of > another buffer that was not part of the running submit. A ring > buffer of pagetable operations confirmed this for every fault: the > CCU reads the 64 KiB-aligned start of the block holding a bound > render target, and msm packs kernel-managed VAs at 4 KiB, so that > address often belongs to a different, unmapped buffer. Batch > reordering makes this common, which is why inorder hides it. > > Align kernel-managed VAs to 64 KiB, falling back to page alignment > when the range is too tight (a6xx_gmu_init() fails with -ENOSPC > otherwise). > > Tested on the LG G8x with Mesa unchanged and GMEM enabled: in an A/B > run in one boot, 4 KiB alignment gave 10 and 10 faults per login, 64 > KiB alignment 0, 0, 0 and 0. No faults in three further logins, a > GMEM stress test or the full device test suite; glmark2 is unchanged > within noise. Userspace-managed VMs (VM_BIND) are not changed; Mesa > may want the same alignment there.
This seems like it is papering over a userspace bug.. Could you file a bug on mesa gitlab[1] and attach a GPU devcoredump[2] after an SMMU fault? BR, -R [1] https://gitlab.freedesktop.org/mesa/mesa/-/work_items [2] https://docs.mesa3d.org/drivers/freedreno.html#gpu-devcoredump > This was investigated, written and tested with the help of an AI > coding assistant (Claude Opus 5.5, Anthropic); I reviewed the change > and the test results. > > Signed-off-by: Gaurav Suman <[email protected]> > --- > Tested on LG G8x ThinQ (SM8150). > --- > drivers/gpu/drm/msm/msm_gem_vma.c | 13 ++++++++++++- > 1 file changed, 12 insertions(+), 1 deletion(-) > > diff --git a/drivers/gpu/drm/msm/msm_gem_vma.c > b/drivers/gpu/drm/msm/msm_gem_vma.c > index > f687a629629d348b54ebb379d3a2fa956b8e472e..2af43291289945d54326287affeffa7e72645880 > 100644 > --- a/drivers/gpu/drm/msm/msm_gem_vma.c > +++ b/drivers/gpu/drm/msm/msm_gem_vma.c > @@ -388,9 +388,20 @@ msm_gem_vma_new(struct drm_gpuvm *gpuvm, struct > drm_gem_object *obj, > if (vm->managed) { > BUG_ON(offset != 0); > BUG_ON(!obj); /* NULL mappings not valid for kernel managed > VM */ > + /* > + * On a6xx (seen on A640) the CCU can read the 64 KiB-aligned > + * start of the block that holds a bound render target. Align > + * kernel-managed VAs to 64 KiB so that block start lies > inside > + * the buffer itself; callers with a tight fixed window, such > as > + * the GMU, fall back to page alignment. > + */ > ret = drm_mm_insert_node_in_range(&vm->mm, &vma->node, > - obj->size, PAGE_SIZE, 0, > + obj->size, SZ_64K, 0, > range_start, range_end, 0); > + if (ret == -ENOSPC) > + ret = drm_mm_insert_node_in_range(&vm->mm, &vma->node, > + obj->size, > PAGE_SIZE, 0, > + range_start, > range_end, 0); > > if (ret) > goto err_free_vma; > > --- > base-commit: ddfe51b0a0f5dc9e415cc2c8ad8db17532dd426b > change-id: 20261109-msm-va-align-072b585038aa > > Best regards, > -- > Gaurav Suman <[email protected]> > >
