Bug#1125375: linux-image-6.12.63+deb13-amd64: PCIe AER error storm on Intel Raptor Lake PCIe 5.0 root port with RTX 3070 Ti

[Salvatore Bonaccorso <carnil@debian.org>]

Hi Zacharie,

On Mon, Jan 12, 2026 at 09:22:28PM +0100, Zacharie Monnet wrote:
> Package: src:linux
> Version: 6.12.63-1
> Severity: normal
> X-Debbugs-Cc: none, zacmo-dev@axynth.ch
> 
> Boot symptoms:
> - Journal flooded with tens of thousands of lines:
>     pcieport 0000:00:01.0: AER: Multiple Correctable error message received
>     pcieport 0000:00:01.0: PCIe Bus Error: severity=Correctable, type=Physical 
> Layer
>     [ 0] RxErr
> 
> - systemd-modules-load.service fails
> 
> Working kernel:
> - linux-image-6.11.57 (from Debian 13 early builds) boots cleanly

As you have a reange of working and non working version, and can as I
understand easily reproduce the errors quickly, can you do a bisect?

I assume in the above this was not present in 6.**12**.57 (6.11.57
does not exist). So this would 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.57
    cp /boot/config-$(uname -r) .config
    yes '' | make localmodconfig
    make savedefconfig
    mv defconfig arch/x86/configs/my_defconfig

    # test 6.12.57 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.63 to ensure this is "bad"
    git checkout v6.12.63
    make my_defconfig
    make -j $(nproc) bindeb-pkg
    ... install the resulting .deb package and confirm problem is present.

With that confirmed, the bisection can start:

    git bisect start
    git bisect good v6.12.57
    git bisect bad v6.12.63

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, try to boot / 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