On Thu, 06 Nov 2025, Jakub Prussak <[email protected]> wrote: > Hello, > > For some time, users of DisplayLink USB-3 docking stations face > corruptions Ubuntu 24.04 on machines with Intel i915+Xe driver (LENOVO > IdeaPad Pro 5 16IMH9 in our case) > Machines using only i915 driver are fine.
AFAICT all IdeaPad Pro 5 16IMH9 models have Meteorlake GPU, and you should be using i915 driver with that. The attached dmesg only appears to have the i915 driver anyway. So how's the xe driver related here? > DisplayLink driver is using evdi kernel > module(https://github.com/DisplayLink/evdi/blob/main/module) that > works as drm output slave. It is using drm_prime exported buffers from > i915 driver. Mmh, can you reproduce any of this running upstream kernels without out-of-tree modules? It's highly unlikely anyone from our side would start debugging scenarios with out-of-tree modules. > We had checked a way evdi access dma-buf exported buffer, e.g. if it > is reading it within dma_buf_begin_cpu_access/dma_buf_end_cpu_access. > > Also, we ruled out access to the buffer before all dma_fence's on > drm_plane are signaled. > Another approach was to wait on dma_resv resv object from > drm_gem_object's dma_buf_attachment, again with no luck. > The issue is reproducible with evdi's evdi_gem_object and generic > drm_gem_shmem_object implementations of drm_gem_object. Corruptions > are visible with all compositors - XServer, Gnome/mutter, weston. > Other kernel module facing this issue is udl. > Nothing was helpful and we suspect some cache coherency issues. > > The problem can be reproduced on the latest kernel on computers with > new Intel devices, and a lot of our users face this problem > (https://github.com/DisplayLink/evdi/issues/524). The way to reproduce > it requires installing EVDI module > (https://github.com/DisplayLink/evdi), loading it and creating a > virtual screen (this can be achieved with this sample app: > https://github.com/jakub-prussak-synaptics/evdipp). Once a virtual > screen is created, the artifacts should be visible while moving the > window around on that screen (see the attached picture or user reports > mentioned earlier). Similar issue appears with devices using UDL > driver on Intel platform. Attached are device information files and a > dmesg output when reproducing this issue. I had a glance at the github issue. First, "new Intel devices" is quite vague. Which devices exactly? 'lspci -vnn -d :*:0300'. Also we can see both i915 and xe drivers in some lsmod listings, but there's no info which drivers are being used with which devices. That's not actionable. Second, seems to me there are a lot of people having issues with non-Intel GPUs as well. What makes you say this is related to i915 or xe drivers? BR, Jani. -- Jani Nikula, Intel
