XPost: linux.debian.bugs.dist
Hello Richard,
On Tue, Mar 11, 2025 at 01:41:06PM +0100, Richard wrote:
as of a couple of months ago I have regular issues with the USB C to
audio jack module from Framework, and any error logs of the time this
happens point to the Kernel. E.g. I compiled 6.13.4 from source, based
on the config Debian shipped with the 6.12.15 Kernel (updated with
make olddefconfig), there it shows these messages:
Mär 01 17:31:43 kernel: usb 1-2.2: 1:1: cannot set freq 48000 (v2/v3): err -110
Mär 01 17:31:48 kernel: usb 1-2.2: uac_clock_source_is_valid(): cannot get clock validity for id 9
Mär 01 17:31:48 kernel: usb 1-2.2: clock source 9 is not valid, cannot use Mär 01 17:31:53 kernel: usb 1-2.2: 1:1: cannot get freq (v2/v3): err -110
I guess the problem is that the USB messages that the USB clock driver (sound/usb/clock.c) is sending don't get a reply in time. (-110 =
ETIMEDOUT).
These issues started at some point late last years, possibly since
6.12 was introduced into testing. I've tested up until 6.13.6 now,
with no change, only a varying degree of information in the logs. A
detailed thread can be found in [1]. What should be mentioned,
originally, when this happened, all audio devices would vanish from
Gnome settings audio page. But with 6.13, they still all show up, but
e.g. if you open the little audio channel test widget and try to test
a channel, the widget just freezes up.
Framework themselves can't to further debugging, as they only
officially support Ubuntu and Fedora. Running any of them as a live
distro is simply not feasible, as this issue can't just be triggered
and only appears about once a week.
Do I understand correctly that audio usually works, just about once per
week the above mentioned lines are found in the kernel log and then it
doesn't work?
Do these messages happen during boot? Or when you start using audio?
Does a reboot help then? Or replugging the audio hardware (or is this an internal USB-C device)?
Is there something else to help finding out, where the issue is
located, or even rule out a software issue? I'm already testing out
the other USB C ports of my Framework 16, but the point is that I
don't have any other device capable of USB C and using that audio
module.
Does the bookworm kernel work on this machine? You could try that then.
Or the Ubuntu kernel might be worth a try.
Best regards
Uwe
-----BEGIN PGP SIGNATURE-----
iQEzBAABCgAdFiEEP4GsaTp6HlmJrf7Tj4D7WH0S/k4FAmfpasoACgkQj4D7WH0S /k41JQf/SE0rVTY+Oa/VzV9/jKaReZ0e/8YzbgMrL7ICxgp6YAPLbsBh6zME1XL1 wE28kx9aT21fThynVkqmUpt4l/LKdF9mCinAT8yZREXB0qw0REscsGTMxBDlqH0J jz0QcYolCrMz6rs5QLlkxRAojKQOia5MPvl6OO12Qfk/I/UkrAZoaw0g7kIbRrtf lhAJ42aZ9zSo4+0eyFNUJUE3W+0oFQiaF79RWbuxC7dMNqilhWyspPIHBQUTmZJC tA+koEwtkHDe6OQahr2e/wO7B8Uhg4f8vbU4HCx0HIgtaPZXBN8UCSJ5J+4pur4j pkiy9bleKf8B0oZA4rtvboOiZ/WkZQ==
=YXZa
-----END PGP SIGNATURE-----
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)