Hi, On Wed, Jan 07, 2026 at 04:41:21AM +0000, Wolf wrote: > Hi Salvatore, > > I did a new test against v6.17-rc1, which is the first bugged version after > v6.16. > > root@gdeltop# git bisect log > git bisect start > # status: waiting for both good and bad commits > # good: [038d61fd642278bab63ee8ef722c50d10ab01e8f] Linux 6.16 > git bisect good 038d61fd642278bab63ee8ef722c50d10ab01e8f > # status: waiting for bad commit, 1 good commit known > # bad: [8f5ae30d69d7543eee0d70083daf4de8fe15d585] Linux 6.17-rc1 > git bisect bad 8f5ae30d69d7543eee0d70083daf4de8fe15d585
Yes, but now according to the outlined procedure you need to continue with the commits as described until you get the first bad commit. Regards, Salvatore
