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

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

Bug#1128396: linux-image-6.12.69+deb13-amd64: Black screen on boot with Intel Meteor Lake xe driver (PCI ID 7d55)

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#1128396: linux-image-6.12.69+deb13-amd64: Black screen on boot with Intel Meteor Lake xe driver (PCI ID 7d55) Salvatore Bonaccorso <carnil@debian.org> - 2026-02-19 10:10 +0100
    Bug#1128396: linux-image-6.12.69+deb13-amd64: Black screen on boot with Intel Meteor Lake xe driver (PCI ID 7d55) Salvatore Bonaccorso <carnil@debian.org> - 2026-02-25 21:30 +0100

#91294 — Bug#1128396: linux-image-6.12.69+deb13-amd64: Black screen on boot with Intel Meteor Lake xe driver (PCI ID 7d55)

Control: tags -1 + moreinfo

On Thu, Feb 19, 2026 at 10:36:57AM +0200, stanislav wrote:
> Package: linux-image-6.12.69+deb13-amd64
> Version: 6.12.69-1
> Severity: important
> 
> After upgrading from kernel 6.12.63+deb13-amd64 to 6.12.69+deb13-amd64,
> the system boots to a black screen with no Wayland/KDE Plasma session starting.
> 
> Hardware: Intel Meteor Lake-P [Intel Arc Graphics] (PCI ID 7d55, rev 08)
> Driver: xe (with force_probe=7d55)
> Desktop: KDE Plasma Wayland (kwin_wayland)
> 
> Kernel 6.12.63+deb13-amd64 works correctly with the same configuration.
> Kernel 6.12.69+deb13-amd64 results in a completely black screen after boot.
> 
> Kernel parameters:
>   xe.enable_psr=0 xe.enable_panel_replay=0 xe.enable_fbc=0
>   xe.enable_dc=0 xe.enable_sagv=0 xe.enable_dpt=0 xe.psr_safest_params=1
> 
> modprobe.d configuration:
>   options xe force_probe=7d55
>   blacklist i915
> 
> The firmware package firmware-intel-graphics 20250410-2 is installed.

Can you please provide a full kernel log with booting 6.12.69-1 with
the black screens?

Can you please test if the problem persists with 6.12.73-1 as released
via trixie-security?

Additionally, if the issue is still reproducible with 6.12.73-1, can
you please bisect the changes between 6.12.63-1 and 6.12.69-1 to
identify the problem? If you can do that will involve compiling and
testing a few kernels:

    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 the 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]

#91409

Control: tags -1 + moreinfo

Hi Stanislav,

On Thu, Feb 19, 2026 at 10:02:20AM +0100, Salvatore Bonaccorso wrote:
> Control: tags -1 + moreinfo
> 
> On Thu, Feb 19, 2026 at 10:36:57AM +0200, stanislav wrote:
> > Package: linux-image-6.12.69+deb13-amd64
> > Version: 6.12.69-1
> > Severity: important
> > 
> > After upgrading from kernel 6.12.63+deb13-amd64 to 6.12.69+deb13-amd64,
> > the system boots to a black screen with no Wayland/KDE Plasma session starting.
> > 
> > Hardware: Intel Meteor Lake-P [Intel Arc Graphics] (PCI ID 7d55, rev 08)
> > Driver: xe (with force_probe=7d55)
> > Desktop: KDE Plasma Wayland (kwin_wayland)
> > 
> > Kernel 6.12.63+deb13-amd64 works correctly with the same configuration.
> > Kernel 6.12.69+deb13-amd64 results in a completely black screen after boot.
> > 
> > Kernel parameters:
> >   xe.enable_psr=0 xe.enable_panel_replay=0 xe.enable_fbc=0
> >   xe.enable_dc=0 xe.enable_sagv=0 xe.enable_dpt=0 xe.psr_safest_params=1
> > 
> > modprobe.d configuration:
> >   options xe force_probe=7d55
> >   blacklist i915
> > 
> > The firmware package firmware-intel-graphics 20250410-2 is installed.
> 
> Can you please provide a full kernel log with booting 6.12.69-1 with
> the black screens?
> 
> Can you please test if the problem persists with 6.12.73-1 as released
> via trixie-security?
> 
> Additionally, if the issue is still reproducible with 6.12.73-1, can
> you please bisect the changes between 6.12.63-1 and 6.12.69-1 to
> identify the problem? If you can do that will involve compiling and
> testing a few kernels:
> 
>     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 the 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.

With this procedure, can you please still bisect the issue so we can
identify the breaking commit?

Regards,
Salvatore

[toc] | [prev] | [standalone]

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

csiph-web