On Mon, Aug 4, 2025 at 12:57 PM Andy Mindful <andy.mind...@gmail.com> wrote: > Double-checked bisect, looks like I've have found broken commit: > > > > git bisect bad > > > The merge base ba5afb9a84df2e6b26a1b6389b98849cd16ea757 is bad. > > > This means the bug has been fixed between > > > ba5afb9a84df2e6b26a1b6389b98849cd16ea757 and > > > [1b1934dbbdcf9aa2d507932ff488cec47999cf3f > > > 61da593f4458f25c59f65cfd9ba1bda570db5db7 > > > 6fc5460ed8dd0edf29e7c5cfb1ef9b1aa04208a1 > > > ba5afb9a84df2e6b26a1b6389b98849cd16ea757].
This skip is messing up the results: # skip: [0dd3ee31125508cd67f7e7172247f05b7fd1753a] Linux 6.7 git bisect skip 0dd3ee31125508cd67f7e7172247f05b7fd1753a and there are still 3858 commits in ba5afb9a84df2e6b26a1b6389b98849cd16ea757..{1b1934dbbdcf9aa2d507932ff488cec47999cf3f,61da593f4458f25c59f65cfd9ba1bda570db5db7,ba5afb9a84df2e6b26a1b6389b98849cd16ea757} Any chance you can get 6.7 to work and restrict the range further? Thanks, Paolo