On 8/31/26 14:30, Timur Kristóf wrote: ... >>>> only flush when a GART window is actually used. >>> >>> Does that mean that there is still a risk of the wedge when the GART >>> windows are used? >> >> Yes, and that is actually not limited to the GART windows. It looks like >> every time we map something into any VM it can happen that the SDMA crashes >> when there are concurrent operations ongoing. > > Would it help to set > adev->vm_manager.concurrent_flush = false > until the problem is figured out?
That came to my mind as well, but I don't think that this would help in this situation. > Or can the crash also happen when the VM is not concurrently flushed? As far as we understand now that problem can happen whenever any VMID is flushed and the SDMA not idle. > By the way, is this the same issue as the Navi 1 sdma_invalidation_workaround > or is that completely different? It indeed looks very similar to me as well. Maybe the fix they came up with for Navi 1x was never 100% correct and now instead of accessing random addresses the SDMA just hangs. Anyway this is a serious HW problem and we need a proper fix ASAP. Regards, Christian. > >> It's just that the GART flushes triggered by the SDMA made that scenario >> much more likely than anything else. >>> Can you remind me when/why we need the GART windows exactly? >> >> Basically every time we want to copy something from system memory to VRAM >> with the kernel. > > Understood. Thanks for explaining! > > Best regards, > Tim
