https://bugzilla.kernel.org/show_bug.cgi?id=207383 --- Comment #9 from Duncan (1i5t5.duncan@xxxxxxx) --- I'm not there yet but it's starting to look like a possibly dud bisect: everything showing good so far. Maybe I didn't wait long enough for the bug to trigger at some step and I'm running up the wrong side of the tree, or maybe it's not drm after all (I thought I'd try something new and limit the paths to drivers/gpu/drm/ and include/drm/, but that may have been a critical mistake). Right now there's only 3-4 even remotely reasonable candidates (out of 14 left to test... the rest being mediatek or similar): 4064b9827 Peter Xu mm: allow VM_FAULT_RETRY for multiple times 6bfef2f91 Jason Gunthorpe mm/hmm: remove HMM_FAULT_SNAPSHOT 17ffdc482 Christoph Hellwig mm: simplify device private page handling in hmm_range_fault And maybe (but I'm neither EFI nor 32-bit) 72e0ef0e5 Mikel Rychliski PCI: Use ioremap(), not phys_to_virt() for platform ROM Meanwhile, user-side I've gotten vulkan/mesa/etc updates recently. I'm considering checking out linus-master/HEAD again, doing a pull, and seeing if by chance either the last week's kernel updates or the user-side updates have eliminated the problem. If not I can come back and finish the bisect (or try just reverting those four on current linus-master/HEAD), before starting a new clean bisect if necessary. Just saved the bisect log and current pointer. -- 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
