Control: tags -1 + moreinfo Hi,
On Sat, Oct 17, 2026 at 09:27:19AM +0200, bug reports wrote: > Package: src:linux > Version: 6.12.113-1 > Severity: critical > Tags: ipv6 > Justification: breaks unrelated software > X-Debbugs-Cc: [email protected] > > Dear Maintainer, > > * What led up to the situation? > > Kernel upgrade, from previous stable to the last one > (linux-image-6.12.113+deb13-amd64) rendered '0cf3:9271 > Qualcomm Atheros Communications AR9271 802.11n' unusable, > breaking all networking. > > * What exactly did you do (or not do) that was effective (or > ineffective)? > > I have no time for bug chasing, I simply selected this working > kernel from GRUB booting menu. > > * What was the outcome of this action? > * What outcome did you expect instead? Please provide along the full kernel log from booting with the old and new kernel up to triggering the problem. I assume it is a regression from 6.12.111-1 to 6.12.113-1, so can you please bisect as well with the following 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.111 cp /boot/config-$(uname -r) .config yes '' | make localmodconfig make savedefconfig mv defconfig arch/x86/configs/my_defconfig # test 6.12.11 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.113 to ensure this is "bad" git checkout v6.12.113 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.111 git bisect bad v6.12.113 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. I found at least two related commits between 6.12.111 and 6.12.113 but the above procedure will point us as the culprit commit. Regards, Salvatore
