Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #93526 > unrolled thread

Bug#1142863: linux-image-6.12.96+deb13-amd64: S3 (deep) suspend powers the machine off instead of suspending

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#1142863: linux-image-6.12.96+deb13-amd64: S3 (deep) suspend powers the machine off instead of suspending Salvatore Bonaccorso <carnil@debian.org> - 2026-07-30 10:50 +0200

#93526 — Bug#1142863: linux-image-6.12.96+deb13-amd64: S3 (deep) suspend powers the machine off instead of suspending

Hi,

On Wed, Jul 29, 2026 at 05:21:23PM +0000, gpomaayll@mozmail.com wrote:
> no - sorry, wouldn't know where to start or have capacity. I am just a user
> reporting a loss of functionality and logs on this hardware.

Okay. If you want to give it a try still here are the instrucitons on
how to bisect the changes between 6.12.95 and 6.12.96 to identify the
problematic commit:

    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.95
    cp /boot/config-$(uname -r) .config
    yes '' | make localmodconfig
    make savedefconfig
    mv defconfig arch/x86/configs/my_defconfig

    # test 6.12.95 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.96 to ensure this is "bad"
    git checkout v6.12.96
    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.95
    git bisect bad v6.12.96

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.

Regards,
Salvatore

[toc] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web