Control: tags -1 + moreinfo upstream Hi,
On Fri, May 01, 2026 at 06:01:47AM +0200, F. Stoyan wrote: > Package: src:linux > Version: 6.12.85-1 > Severity: minor > > Dear Maintainer, > > after upgrading to linux-image-6.12.85+deb13-amd64 the kernel complains: > > $ journalctl -nall --no-h -g "AMD-Vi|Linux version" --no-p > -- Boot 04004cd52b4f4f6287941553bc9de5a2 -- > Apr 08 04:02:58 kernel: Linux version 6.12.74+deb13+1-amd64 > ([email protected]) (x86_64-linux-gnu-gcc-14 (Debian 14.2.0-19) > 14.2.0, GNU ld (GNU Binutils for Debian) 2.44) #1 SMP PREEMPT_DYNAMIC Debian > 6.12.74-2 (2026-03-08) > Apr 08 04:02:58 kernel: AMD-Vi: Using global IVHD EFR:0x206d73ef22254ade, > EFR2:0x0 > Apr 08 04:02:58 kernel: pci 0000:00:00.2: AMD-Vi: IOMMU performance counters > supported > Apr 08 04:02:58 kernel: AMD-Vi: Extended features (0x206d73ef22254ade, 0x0): > PPR X2APIC NX GT IA GA PC GA_vAPIC > Apr 08 04:02:58 kernel: AMD-Vi: Interrupt remapping enabled > Apr 08 04:02:58 kernel: AMD-Vi: X2APIC enabled > Apr 08 04:02:58 kernel: AMD-Vi: Virtual APIC enabled > -- Boot 5a40468eb6a2462097dd701acf7bd280 -- > May 01 04:06:28 kernel: Linux version 6.12.85+deb13-amd64 > ([email protected]) (x86_64-linux-gnu-gcc-14 (Debian 14.2.0-19) > 14.2.0, GNU ld (GNU Binutils for Debian) 2.44) #1 SMP PREEMPT_DYNAMIC Debian > 6.12.85-1 (2026-04-30) > May 01 04:06:28 kernel: AMD-Vi: Using global IVHD EFR:0x206d73ef22254ade, > EFR2:0x0 > May 01 04:06:28 kernel: pci 0000:00:00.2: AMD-Vi: IOMMU performance counters > supported > May 01 04:06:28 kernel: AMD-Vi: Extended features (0x206d73ef22254ade, 0x0): > PPR X2APIC NX GT IA GA PC GA_vAPIC > May 01 04:06:28 kernel: AMD-Vi: Interrupt remapping enabled > May 01 04:06:28 kernel: AMD-Vi: X2APIC enabled > May 01 04:06:28 kernel: AMD-Vi: Virtual APIC enabled > May 01 04:11:24 kernel: AMD-Vi: Completion-Wait loop timed out > May 01 04:12:47 kernel: AMD-Vi: Completion-Wait loop timed out > May 01 04:13:12 kernel: AMD-Vi: Completion-Wait loop timed out > May 01 04:15:32 kernel: AMD-Vi: Completion-Wait loop timed out > May 01 04:19:24 kernel: AMD-Vi: Completion-Wait loop timed out > May 01 04:22:04 kernel: AMD-Vi: Completion-Wait loop timed out > May 01 04:22:46 kernel: AMD-Vi: Completion-Wait loop timed out > May 01 04:22:57 kernel: AMD-Vi: Completion-Wait loop timed out > May 01 04:24:48 kernel: AMD-Vi: Completion-Wait loop timed out > May 01 04:43:31 kernel: AMD-Vi: Completion-Wait loop timed out > May 01 04:43:45 kernel: AMD-Vi: Completion-Wait loop timed out > May 01 04:47:17 kernel: AMD-Vi: Completion-Wait loop timed out > May 01 04:48:40 kernel: AMD-Vi: Completion-Wait loop timed out > May 01 04:49:44 kernel: AMD-Vi: Completion-Wait loop timed out > May 01 04:51:07 kernel: AMD-Vi: Completion-Wait loop timed out > May 01 05:07:06 kernel: AMD-Vi: Completion-Wait loop timed out > May 01 05:10:41 kernel: AMD-Vi: Completion-Wait loop timed out > May 01 05:39:53 kernel: AMD-Vi: Completion-Wait loop timed out > > I haven't noticed any functional issues so far, except for the log spam. I'm sorry to hear about this regression caused with the lastest urgent security update for the kernel. Would you be able to bisect the changes between 6.12.74 and 6.12.85 to identify which commit triggers this specifically? Do you need instructions on how to do it? Let me just paste our set of instruction to explain that otherwise, feel free to ignore if this is already good for you. So bisect 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.74 cp /boot/config-$(uname -r) .config yes '' | make localmodconfig make savedefconfig mv defconfig arch/x86/configs/my_defconfig # test 6.12.74 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.85 to ensure this is "bad" git checkout v6.12.85 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.74 git bisect bad v6.12.85 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 and 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
