On Mon, May 12, 2025 at 4:07 PM Steven J Abner <pheonix....@att.net> wrote: > > On Fri, May 9 2025 at 03:01:13 PM +0000, Steven J Abner > <pheonix....@att.net> wrote: > > On Fri, May 9 2025 at 02:05:16 PM +0000, Alex Deucher > > <alexdeuc...@gmail.com> wrote: > >> bisect between 6.2.16 and 6.2.17 to identify the commit which broke > > > > Are you asking for a 'diff' output of drm and amdgpu directories > > between 6.2.16 (last of the 6.2 series) and 6.3 (start of the 6.3 > > series)? > > I'm willing to revert/test code on my machine, problem is I don't know > sequence nor what I can safely revert. I haven't messed with video > drivers/code since DOS days of having to write ones own graphics > routines. I could force? kernel to build with '-g' on drm/amdgpu? and > walk it I guess. But don't know what I'm looking for. :(
See: https://docs.kernel.org/admin-guide/bug-bisect.html If you know a good and bad point on a particular kernel branch, you can use git to bisect the tree and identify the exact commit which broke caused your issue. Alex > Steve > >
