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

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

Bug#1139950: Acknowledgement (amdgpu carrizo: no display signal after modeset)

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#1139950: Acknowledgement (amdgpu carrizo: no display signal after modeset) Salvatore Bonaccorso <carnil@debian.org> - 2026-06-17 16:00 +0200
    Processed: Re: Bug#1139950: Acknowledgement (amdgpu carrizo: no  display signal after modeset) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2026-06-17 16:00 +0200

#93016 — Bug#1139950: Acknowledgement (amdgpu carrizo: no display signal after modeset)

Control: tags -1 + moreinfo

Hi,

On Sun, Jun 14, 2026 at 09:08:36PM +0300, Jaak Ristioja wrote:
> Using kernels from snapshot.debian.org, I narrowed this down even further:
> 
> Not affected:
>  * linux-image-6.12.48+deb13-amd64_6.12.48-1_amd64.deb
>  * linux-image-6.12.57+deb13-amd64_6.12.57-1_amd64.deb
>  * linux-image-6.12.63+deb13-amd64_6.12.63-1_amd64.deb
> 
> Affected:
>  * linux-image-6.12.69+deb13-amd64_6.12.69-1_amd64.deb

This is already great so we have a closer range. Can you please bisect
the changes between 6.12.63 and 6.12.69 upstream to identify the
offending commit introducing the problem?  Here is a small procedure:

    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.69 to ensure this is "bad"
    git checkout v6.12.69
    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.69

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] | [next] | [standalone]

#93021 — Processed: Re: Bug#1139950: Acknowledgement (amdgpu carrizo: no display signal after modeset)

Processing control commands:

> tags -1 + moreinfo
Bug #1139950 [linux-modules-7.0.10+deb13-amd64] amdgpu carrizo: no display signal after modeset
Added tag(s) moreinfo.

-- 
1139950: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1139950
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]

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

csiph-web