Hello Jason, On Fri, Jan 17, 2025 at 05:25:20PM -0500, Jason McCormick wrote: > Package: src:linux > Version: 6.1.124-1 > Severity: important > > Dear Maintainer, > > * What led up to the situation? > > Number of Debian bookworm (stable) systems were upgraded > to 6.1.0-30 as part of the 12.9 release. Upon reboot, > Asterisk/app_rpt audo has a choppy pulse noise for any > played audio. Asterisk/app_rpt uses the snd_pcm_oss module > for USB device access. > > Example: https://www.youtube.com/watch?v=1NFvY0KV7-I > Forum Thread: > https://community.allstarlink.org/t/after-kernel-update-debian12-asl3-distortion-choppy-audio-on-simpleusb-tx-audio-especially-telemetry/22684/50 > > * What exactly did you do (or not do) that was effective (or > ineffective)? > > Reverting the system to linux-images-6.1.0-28-amd64 > > * What was the outcome of this action? > > Audio works as expected. Reinstalling -29 or -30 > leads the the same artifact.
6.1.0-28 corresponds to 6.1.119 upstream
6.1.0-29 corresponds to 6.1.123 upstream
6.1.0-30 corresponds to 6.1.124 upstream
Looking through the changes beween 6.1.119 and 6.1.123 I don't spot
something obviously suspicious. There were no changes in sound/core/oss.
Can you please try to bisect the problem? The relevant commit must be
between 6.1.119 and 6.1.123. So the rough procedure is:
- init:
git clone
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
cd linux
git checkout v6.1.119
cp /boot/config-$(uname -r) .config
make localmodconfig
cp .config arch/x86/configs/my_defconfig
- test:
make -j10 my_defconfig bindeb-pkg
.. install the generated kernel image and test
- test the new end:
git checkout v6.1.123
goto test
Assuming also with upstream v6.1.119 is good and v6.1.123 is bad, you
can start the actual bisection:
git bisect start v6.1.123 v6.1.119
Until the problematic commit isn't found git checks out a revision to
test in each step. Do that (i.e. build the kernel image using bindeb-pkg
like above, install and test) and depending on the outcome run:
git bisect good
or
git bisect bad
If a revision fails to compile or boot such that you cannot diagnose if
your problem exists, run:
git bisect skip
After roughly 10 iterations that should identify the first bad commit.
Please report that.
Best regards
Uwe
signature.asc
Description: PGP signature
