https://bugzilla.kernel.org/show_bug.cgi?id=207383 laser.eyess.trackers@xxxxxxxxx changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |laser.eyess.trackers@gmail. | |com --- Comment #91 from laser.eyess.trackers@xxxxxxxxx --- I wanted to comment on this bug because I believe I have been experiencing it based on a bug report I filed with amdgpu[1]. As of 5.7.8 on Arch Linux I no longer experiencing this bug regularly. Usually I could trigger it every 1-3 days. The biggest change I made was turning off adaptive_sync (VRR, Freesync, etc.) in my window manager. Now it's been almost a week and I haven't seen it. Right now I am on 5.7.9 and will keep running as long as possible until it crashes again, if it crashes again. I see some discussion here about race conditions between memory allocations and atomic commits, and while I don't understand most of it, would I be correct in assuming that variable frame timing would exacerbate this bug? If so, I believe that is exactly what I am experiencing. I'd love to help test patches for this as they come in, but for now I want to add that VRR is an important part of the equation for this bug for me. The bug report linked in [1] has more of my set up but all I'll say here is that I also have a multimonitor setup, each one supports VRR and they are at varying resolutions/refresh rates; two at 1440p 144Hz, one at 4k 60Hz. 1. https://gitlab.freedesktop.org/drm/amd/-/issues/1216 -- You are receiving this mail because: You are watching the assignee of the bug. _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
