Control: tags -1 + moreinfo

Hi Benjamin,

On Tue, Nov 17, 2026 at 09:26:55AM +0100, [email protected] wrote:
> Package: linux-image-7.3.4+deb14-amd64
> Version: 7.3.4-1
> Severity: normal
> 
> Dear Maintainer,
> 
> I am reporting a graphics regression affecting my Intel Meteor Lake-P
> system after upgrading from Debian kernel 7.3.3 to 7.3.4.
> 
> Booting 7.3.3+deb14-amd64 restores, graphics are fine. With
> 7.3.4+deb14-amd64, graphics malfunction under X11 and the kernel repeatedly
> reports i915 display plane faults on pipes A, B and C. Sometimes, I enocunter 
> severe flickering, sometimes, only a few seconds in X, kernels panics.
> 
> Last known working kernel:
>   7.3.3+deb14-amd64
> 
> First known failing kernel:
>   7.3.4+deb14-amd64
>   Debian package version: 7.3.4-1
> 
> Hardware:
>   Intel Corporation Meteor Lake-P [Intel Graphics] [8086:7d45] (rev 08)
>   Subsystem: Dell Device [1028:0cb2]
>   Kernel driver in use: i915
> 
> Display manager, WM etc.:
>   LightDM, with an X11 session in i3 with picom
> 
> Both boots use the following additional kernel parameters:
>   i915.fastboot=0 i915.enable_psr=0 i915.enable_fbc=0
>   i915.enable_dc=0 thunderbolt.host_reset=false
> 
> (Fastboot is ignored, but shouldn't matter here.)
> 
> During an exemplary failing boot, the LightDM greeter session opens at 
> 08:27:59,
> and my user session opens at 08:28:09. At 08:28:20, the kernel starts
> reporting repeated display plane faults:
> 
>   i915 0000:00:02.0: [drm] *ERROR* [CRTC:271:pipe B][PLANE:154:plane 1B] 
> fault (CTL=0x84000000, SURF=0x6f45000, SURFLIVE=0x6f45000)
> 
>   i915 0000:00:02.0: [drm] *ERROR* [CRTC:152:pipe A][PLANE:35:plane 1A] fault 
> (CTL=0x84000000, SURF=0x6f44000, SURFLIVE=0x6f44000)
> 
>   i915 0000:00:02.0: [drm] *ERROR* [CRTC:390:pipe C][PLANE:273:plane 1C] 
> fault (CTL=0x84000000, SURF=0x6f48000, SURFLIVE=0x6f48000)
> 
>   handle_plane_fault: 41 callbacks suppressed
> 
> The failing boot also reports these initialization errors:
> 
>   i915 0000:00:02.0: [drm] *ERROR* GT1: GSC proxy component didn't bind 
> within the expected timeout
> 
>   i915 0000:00:02.0: [drm] *ERROR* GT1: GSC proxy handler failed to init
> 
> The mei_gsc_proxy component subsequently binds:
> 
>   mei_gsc_proxy 0000:00:16.0-0f73db04-97ab-4125-b893-e904ad0d5464:
>   bound 0000:00:02.0 (ops i915_gsc_proxy_component_ops [i915])
> 
> I do not know whether the GSC proxy initialization timeout is related
> to the display plane faults.
> 
> The supplied working 7.3.3 boot log does not show these errors.
> I am currently using 7.3.3 as a workaround.
> 
> I attached a log of my current good boot under 7.3.3 and a bas boot under 
> 7.3.4. Anything else needed?
> 
> Kind regards, thanks a lot for your work!
> Benjamin

If possible, could you bisect the changes between 7.3.3 and 7.3.4 to
identify the breaking commit? If doing so the procedure wuld be as
follows and test a couple of kernels:

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

    # test 7.3.3 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 7.3.4 to ensure this is "bad"
    git checkout v7.3.4
    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 --first-parent
    git bisect good v7.3.3
    git bisect bad v7.3.4

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.

There is a chance as well that it is fixed in 7.3.5 as there some
related changes. But it would be great if we can identify the breaking
commit in 7.3.4 and then if the fix is in 7.3.5.

Regards,
Salvatore

Reply via email to