Hi Christian,
On Tue, Aug 11, 2026 at 07:49:00AM +0200, Christian Schwamborn wrote:
> Hello Salvatore,
>
> I was able to do a quick record this morning via the servers kvm but still
> with the bookworm kernel. For the 6.12 Kernel I need to free another system.
Please take my apologies, I caused here some confusion because of
finger memory. While it defintively would be good to know if 6.12.y
exposes the problem as well, we are interested here more on the 6.1.y
specific regression. I will do some more research based on the capture
you were able to do.
Were you able to take for testing off one such system? If so it would
be awesome if you could do the following, so we know 6.1.177-1 is good
and 6.1.180-1 is bad. And e need to have bisect, the procedure is as
follows:
git clone --single-branch -b linux-6.1.y
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
cd linux-stable
git checkout v6.1.177
cp /boot/config-$(uname -r) .config
yes '' | make localmodconfig
make savedefconfig
mv defconfig arch/x86/configs/my_defconfig
# test 6.1.177 to ensure this is "good"
make my_defconfig
make -j $(nproc) bindeb-pkg
... install the resulting .deb package and confirm it successfully boots
# test 6.1.180 to ensure this is "bad"
git checkout v6.1.180
make my_defconfig
make -j $(nproc) bindeb-pkg
... install the resulting .deb package and confirm it fails to boot
With that confirmed, the bisection can start:
git bisect start
git bisect good v6.1.177
git bisect bad v6.1.180
In each bisection step git checks out a state between the oldest
known-bad and the newest known-good commit. In each step test using:
make my_defconfig
make -j $(nproc) bindeb-pkg
... install, try to boot
and if the problem is hit run:
git bisect bad
and if the problem doesn't trigger run:
git bisect good
. Please pay attention to always select the just built kernel for
booting, it won't always be the default kernel picked up by grub.
Iterate until git announces to have identified the first bad commit.
Then provide the output of
git bisect log
In the course of the bisection you might have to uninstall previous
kernels again to not exhaust the disk space in /boot. Also in the end
uninstall all self-built kernels again.
The expected number of compilations will be:
Bisecting: 516 revisions left to test after this (roughly 9 steps)
With the procedure you will build a targeted kernel, so the rounds
should be relatively fast.
Regards,
Salvatore
