Hello Dieter, On Sun, Feb 02, 2025 at 11:22:49AM +0100, Dieter Faulbaum wrote: > Sorry I'm not really sure, what I can do to find the breaking commit. Bisecting would work as follows: - Cloning the upstream source: git clone https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git cd linux git checkout v6.11 - Reusing the Debian configuration and disable all modules not in use: cp /boot/config-$(uname -r) .config make localmodconfig cp .config arch/x86/configs/my_defconfig - Building a kernel package: make -j10 my_defconfig bindeb-pkg The last step creates a kernel package. Install it and test if the issue occurs. For 6.11 I would expect this to work (but in general it's good to make sure one's assumptions are good, so please don't skip that test). Then do git checkout v6.12 make -j10 my_defconfig bindeb-pkg which creates another kernel package. Test this in the same way. If this shows the problems you're set for a bisection: - Start the bisection: git bisect start v6.12 v6.11 - Build and test the version that git suggested: make -j10 my_defconfig bindeb-pkg ... install + boot - Depending on the outcome of your test do either git bisect good (if the tested kernel package doesn't show the problem) or git bisect bad and repeat starting at "Build and test the version that git suggested" until git identfied the first bad commit. I skipped some steps (like maybe you need to install build dependencies and how you install the resulting package). Also you probably need to deinstall the test packages again to not fill your /boot partition (if you have one). If you still have questions, don't hesitate to ask. Best regards Uwe
Attachment:
signature.asc
Description: PGP signature