Control: tags -1 + moreinfo Hi Emilio
On Tue, Sep 08, 2026 at 10:29:22PM +0200, Emilio wrote: > Package: linux-image-amd64 > Version: 6.12.107-1 > Severity: normal > X-Debbugs-Cc: [email protected], [email protected] > User: [email protected] > Usertags: amd64 > > Dear Maintainer, > > Audio crackling/dropout on Meteor Lake HDA (Asus Zenbook UX3405MA) after > upgrading kernel 6.12.94 -> 6.12.107. Powered studio monitors connected via > headphone jack, wobble/dropout occurs intermittently when a second audio > stream plays while typing. Ruled out ground loop (persists on battery), > pinned PipeWire quantum to 1024 (no change), no RT scheduling errors in > journalctl. Kernel 6.12.94 does not exhibit the issue; 6.12.107 does. For this one similar to #1147252 I propose to bisect the issue. As you can clearly assert when the problem exists, can you please bisect the issue? First it is best to narrow further down the affected range, between 6.12.94-1 and 6.12.107-1 we had a couple of releases: 6.12.107-1 6.12.105-1 6.12.101-1 6.12.100-1 6.12.96-1 6.12.95-1 6.12.94-1 So let's first identify the range where on Debian releases the problem is introduced. You can fetch older linux-image deb's from https://snapshot.debian.org/package/linux-signed-amd64/ . Assuming you have identified the regression is hypotetically between 6.12.96-1 and 6.12.100-1, then start the bisection as follows: 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.96 cp /boot/config-$(uname -r) .config yes '' | make localmodconfig make savedefconfig mv defconfig arch/x86/configs/my_defconfig # test 6.12.96 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.100- to ensure this is "bad" git checkout v6.12.100 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.96 git bisect bad v6.12.100 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. After that we will ideally have pointed out the breraking commit where we can continue investigating and/or report upstream. Regards, Salvatore
