Control: found -1 6.12.74-2

Hi Bernd,

On Wed, Mar 18, 2026 at 02:30:28PM +0100, Bernd Schumacher wrote:
> Hi Salvatore,
> 
> Am Mittwoch, dem 18.03.2026 um 13:41 +0100 schrieb Salvatore
> Bonaccorso:
> > 
> > Given you have the range 6.12.63 (good) .. 6.12.73 (bad), can you
> > 
> > 1. confirm if 6.12.74-2 still as well is broken
> > 
> Yes I confirm, that the same problem exists with:
> ii  linux-image-6.12.74+deb13+1-amd64        6.12.74-2 

Thanks for the confirmation.

> > and if so
> > 
> > 2. would you be able to bisect the upstream changes beween 6.12.63
> > and
> > 6.12.73 to identify the commit which introduces this regression for
> > you? (Do you need instructions for that?).
> Yes, I need instructions how I can find the relevant change. 

So first thanks if you find time to do that work, that is great. Here
are the instructions, it will involve doing some rounds of compiling
and testing kernels as follows:

    git clone --single-branch -b linux-6.12.y 
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
    cd linux-stable
    git checkout v6.12.63
    cp /boot/config-$(uname -r) .config
    yes '' | make localmodconfig
    make savedefconfig
    mv defconfig arch/x86/configs/my_defconfig

    # test 6.12.63 to ensure this is "good"
    make my_defconfig
    make -j $(nproc) bindeb-pkg
    ... install the resulting .deb package and confirm problem does not exist

    # test 6.12.73 to ensure this is "bad"
    git checkout v6.12.73
    make my_defconfig
    make -j $(nproc) bindeb-pkg
    ... install the resulting .deb package and confirm problem exists.

With that confirmed, the bisection can start:
 
    git bisect start
    git bisect good v6.12.63
    git bisect bad v6.12.73
 
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, verify if problem exists
 
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.

Hope this helps so far.

Regards,
Salvatore

Reply via email to