Control: tags -1 + moreinfo upstream Hi Benjamin,
On Mon, Nov 02, 2026 at 10:14:00PM +0100, Benjamin Scherrer wrote: > Package: src:linux > Version: 6.12.115-2 > Severity: normal > X-Debbugs-Cc: [email protected] > > Dear Maintainer, > > I am experiencing a reproducible USB audio regression with a MOTU M4 interface > on current Debian 13. > > The interface has worked reliably for years. After rebooting into kernel > 6.12.115+deb13.1-amd64, audio playback stopped working. > > Booting the same system with kernel 6.12.113 restores normal operation. No > other configuration changes were made. Sorry about the breakage with the security update needed. As you can cleary identify when system is regression, could you please bisect the changes between 6.12.113 and 6.12.115 upstream with the following procedure to identify the culprit please? 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.113 cp /boot/config-$(uname -r) .config yes '' | make localmodconfig make savedefconfig mv defconfig arch/x86/configs/my_defconfig # test 6.12.113 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.115 to ensure this is "bad" git checkout v6.12.35 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.113 git bisect bad v6.12.115 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
