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)

XPost: linux.debian.bugs.dist
From: [email protected]

This is a multi-part message in MIME format.
So, it has been a while, here a little update. As I couldn't figure out - and didn't have the time to do so - how to compile Fedora's kernel sources with their config through make bindeb-pkg, I didn't even bother trying with Ubuntu's kernel. I have now
used the Fedora 41 live USB for the past two weekends and the most part of the past week, yet the issue didn't show up once. And since I very much doubt that to be a coincidence and the issue just fixed itself, the issue must be located in some place
inside what Trixie has been shipping for roughly the last 6 months (I first reported this in early January to the Framework community, but that's just when it became frequent enough and had been around already for at least a month if not more, I'd say.


The only additional information I can provide at this point is logs I gathered with a script the Framework support gave me [1] that I sent them for analysis. But I'm not convinced they'll show anything of importance, as otherwise the FW guys could have
already spotted it. But if anyone has any additional ideas on how to figure out the cause, do let me know.


Best

Richard


[1]: https://raw.githubusercontent.com/FrameworkComputer/linux-docs/main/log-helper/combined.sh

<!DOCTYPE html>
<html data-lt-installed="true">
<head>

<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body style="padding-bottom: 1px;">
<p>So, it has been a while, here a little update. As I couldn't
figure out - and didn't have the time to do so - how to compile
Fedora's kernel sources with their config through make bindeb-pkg,
I didn't even bother trying with Ubuntu's kernel. I have now used
the Fedora 41 live USB for the past two weekends and the most part
of the past week, yet the issue didn't show up once. And since I
very much doubt that to be a coincidence and the issue just fixed
itself, the issue must be located in some place inside what Trixie
has been shipping for roughly the last 6 months (I first reported
this in early January to the Framework community, but that's just
when it became frequent enough and had been around already for at
least a month if not more, I'd say.</p>
<p><br>
</p>
<p>The only additional information I can provide at this point is
logs I gathered with a script the Framework support gave me [1]
that I sent them for analysis. But I'm not convinced they'll show
anything of importance, as otherwise the FW guys could have
already spotted it. But if anyone has any additional ideas on how
to figure out the cause, do let me know.</p>
<p><br>
</p>
<p>Best</p>
<p>Richard</p>
<p><br>
</p>
<p>[1]:
<a class="moz-txt-link-freetext" href="https://raw.githubusercontent.com/FrameworkComputer/linux-docs/main/log-helper/combined.sh">https://raw.githubusercontent.com/FrameworkComputer/linux-docs/main/log-helper/combined.sh</a></p>
</body>
<lt-container></lt-container>
</html>

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)

XPost: linux.debian.bugs.dist
From: [email protected]

On Sun, May 25, 2025 at 04:07:19PM +0200, Richard wrote:

So, it has been a while, here a little update. As I couldn't figure
out - and didn't have the time to do so - how to compile Fedora's
kernel sources with their config through make bindeb-pkg, I didn't
even bother trying with Ubuntu's kernel. I have now used the Fedora 41
live USB for the past two weekends and the most part of the past week,
yet the issue didn't show up once. And since I very much doubt that to
be a coincidence and the issue just fixed itself, the issue must be
located in some place inside what Trixie has been shipping for roughly
the last 6 months (I first reported this in early January to the
Framework community, but that's just when it became frequent enough
and had been around already for at least a month if not more, I'd say.

Which version of the Fedora kernel are you using? Can you test the base version, too? (So if Fedora uses a modified 6.13.7, test on a vanilla
6.13.7. That allows to determine if there is something in the Fedora
patch stack that helps or if it's just a different base version that is improved compared to the 6.12.17 kernel that you reported this issue
against.)

Best regards
Uwe

-----BEGIN PGP SIGNATURE-----

iQEzBAABCgAdFiEEP4GsaTp6HlmJrf7Tj4D7WH0S/k4FAmg4jDYACgkQj4D7WH0S /k6m2wf/cK7FckWl8glqsqiNrHR/8PIVN92bhev2ejb/9cXzmRs5QEKPvYzj7nWr 3lE1UWtiFUOoS+sw/3TB6oqka+iQXDX726e/xdFeKejFjFQ1UkWTqcbskkaWBhwM +vEKQCb57Dq3lCa3j4luCs8VjEu3QwtvsYI2XoEShJ5x+CLnjJRwHtEXbHN6nPYO C6Nb04hMuRI0vX4MBw99Oh3y0V3LPtIRMZ+gojXKV8Omx+W25mTZJaANDaChSH2t hW0EI+ZbnoEpMrvTAF/9yjxtmFFW4LL/98I00KEJ9OG85x6LFRkGjutJX1ezgu1J 0SrAg1RCKAvSTw/5TvJc7C4Vwxx5Bg==
=NoF5
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)