On 2025-03-12 at 06:34:43, Salvatore Bonaccorso wrote: > So you know it worked with 6.10 but latest in 6.12 not, can you first > identify by fetching the old linux-images (use the snapshots.d.o > service) to pinpoint the Debian revision ranges where the regression > is introduced?
Yeah, I can do that. It might be this weekend before I finish, but I can pin it down to some versions. I'll get started on a few tonight. > What is that range? Could you next bisect. Assuming we get even a > result within one stable series, this would be great, because then > next I would like to ask if you can bisect the respective upstream > changes to the breaking commits (still works if the issue is > introduced on major version change, then bisect might take longer). I am less sure that I can build and install a functional kernel by hand. I have no problem bisecting a change (I contribute to Git, after all), but I don't usually do custom kernel builds. I'll see if I can coerce the linux package to build a custom version from upstream. -- brian m. carlson (they/them or he/him) Toronto, Ontario, CA
signature.asc
Description: PGP signature
