On Sat, 27 Sep 2025 16:09:08 +0200 Salvatore Bonaccorso <[email protected]> wrote: > - Can you temporarily test as well the upper kernels from unstable > (6.16.8-1 right now, but soonish 6.16.9-1 as well) to see if the > problem is triggerable there as well?
I tested the upper kernels and was still able to reproduce the issue on both 6.16.8-1 and 6.16.9-1. > Note: If we find the problem is prosent in 6.16.y then we need to find > the breaking change between 6.1.y and 6.12.y. It might be asier here > if we first make the range of potential upstream versions more narrow, > so you might first do a "manual bisect" on Debian revisions (For that > use the snapshot.debian.org service to retrieve linux-images uploaded > to Debian. E.g. go down from 6.12 in "major version" steps until we > have close enough range of broken/fixed upstream major versions. Then > perform a normal bisect between the upstream versions. Using snapshot.debian.org I have determined that the breaking change was introduced between 6.11.10 (tested 6.11.10-1) and 6.12 (tested 6.12.3-1 and 6.12~rc6-1~exp1). Thank you for your assistance. Let me know what would be the next step. -- Kevin
