Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #86417 > unrolled thread

Bug#1100105: linux-image-amd64: Issues with Framework audio module

Back to article view | Back to linux.debian.kernel

Contents

  Bug#1100105: linux-image-amd64: Issues with Framework audio module Richard <rrosner5@gmail.com> - 2025-03-11 13:50 +0100
    Bug#1100105: linux-image-amd64: Issues with Framework audio module Richard <rrosner5@gmail.com> - 2025-03-24 19:50 +0100
    Bug#1100105: linux-image-amd64: Issues with Framework audio module Uwe Kleine-König <ukleinek@debian.org> - 2025-03-30 18:10 +0200
      Bug#1100105: linux-image-amd64: Issues with Framework audio module Richard <rrosner5@gmail.com> - 2025-03-30 19:00 +0200
        Bug#1100105: linux-image-amd64: Issues with Framework audio module Uwe Kleine-König <ukleinek@debian.org> - 2025-04-08 19:10 +0200
    Bug#1100105: linux-image-amd64: Issues with Framework audio module Richard <rrosner5@gmail.com> - 2025-05-25 16:10 +0200
      Bug#1100105: linux-image-amd64: Issues with Framework audio module Uwe Kleine-König <u.kleine-koenig@baylibre.com> - 2025-05-29 18:40 +0200
    Bug#1100105: linux-image-amd64: Issues with Framework audio module Richard <rrosner5@gmail.com> - 2025-07-21 19:00 +0200
    Bug#1100105: linux-image-amd64: Issues with Framework audio module Richard <rrosner5@gmail.com> - 2025-09-20 20:50 +0200

#86417 — Bug#1100105: linux-image-amd64: Issues with Framework audio module

[Multipart message — attachments visible in raw view] — view raw

Package: linux-image-amd64
Version: 6.12.17-1
Severity: normal

Dear Maintainer,

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


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.


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.


[1]: https://community.frame.work/t/responded-audio-expansion-card-connection-sometimes-unreliable/62951/20

-- System Information:
Debian Release: trixie/sid
   APT prefers testing
   APT policy: (990, 'testing'), (50, 'experimental'), (50, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.13.6-falcot (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages linux-image-amd64 depends on:
ii  linux-image-6.12.17-amd64  6.12.17-1

linux-image-amd64 recommends no packages.

linux-image-amd64 suggests no packages.

-- no debconf information

[toc] | [next] | [standalone]

#86594

Something I just noticed, while Firefox refuses to play back any media
when this happens, mpv does, but playback seems a bit distorted, and
these messages now appear in the user logs:


Mär 24 18:59:29 pipewire[2927]: spa.alsa: set_hw_params: Connection timed out
Mär 24 18:59:29 pipewire[2927]: pw.node:
(alsa_output.usb-Framework_Audio_Expansion_Card-00.analog-stereo-71)
suspended -> error (Start error: Connection timed out)
Mär 24 18:59:29 wireplumber[2934]: wp-event-dispatcher:
<WpAsyncEventHook:0x55fad05c03d0> failed:
<WpSiStandardLink:0x55fad09f9100> link failed: item deactivated before
format was set
Mär 24 18:59:54 pipewire[2927]: spa.alsa: set_hw_params: Connection timed out
Mär 24 18:59:54 pipewire[2927]: pw.node:
(alsa_output.usb-Framework_Audio_Expansion_Card-00.analog-stereo-71)
suspended -> error ((null))
Mär 24 18:59:54 pipewire[2927]: pw.link: 0x559101476130: one of the
nodes is in error out:idle in:error
Mär 24 18:59:54 pipewire[2927]: pw.link: 0x559101360b60: one of the
nodes is in error out:idle in:error
Mär 24 18:59:56 mpv[10872]: pw.conf: setting config.name to
client-rt.conf is deprecated, using client.conf
Mär 24 18:59:56 xdg-desktop-por[3882]: Realtime error: Could not get
pidns: Could not fstatat ns/pid: Not a directory
Mär 24 18:59:56 gnome-shell[3248]:
meta_window_set_stack_position_no_sync: assertion
'window->stack_position >= 0' failed
Mär 24 18:59:56 pipewire[2927]: pw.link: 0x55910157f5b0: one of the
nodes is in error out:suspended in:error
Mär 24 18:59:56 pipewire[2927]: pw.link: 0x55910157d590: one of the
nodes is in error out:suspended in:error
Mär 24 19:00:28 pipewire[2927]: spa.alsa: set_hw_params: Connection timed out
Mär 24 19:00:28 pipewire[2927]: pw.node:
(alsa_output.usb-Framework_Audio_Expansion_Card-00.analog-stereo-71)
suspended -> error (Start error: Connection timed out)


and playback in Firefox seems to be broken due to these messages:

Mär 24 18:54:47 pipewire[2927]: spa.alsa: set_hw_params: Connection timed out
Mär 24 18:54:47 pipewire[2927]: pw.node:
(alsa_output.usb-Framework_Audio_Expansion_Card-00.analog-stereo-71)
suspended -> error (Start error: Connection timed out)
Mär 24 18:54:51 firefox-beta.desktop[7437]: [Child 7437,
MediaDecoderStateMachine #4] WARNING: 7f33ca3b73a0 OpenCubeb() failed
to init cubeb: file
/builds/worker/checkouts/gecko/dom/media/AudioStream.cpp:284
Mär 24 18:54:51 firefox-beta.desktop[7437]: [Child 7437,
MediaDecoderStateMachine #4] WARNING: Decoder=7f33d511a700
[OnMediaSinkAudioError]: file
/builds/worker/checkouts/gecko/dom/media/MediaDecoderStateMachine.cpp:4633


During these time stamps, the Kernel keeps spamming

Mär 24 18:59:44 kernel: usb 5-1: clock source 9 is not valid, cannot use
Mär 24 18:59:49 kernel: usb 5-1: 1:3: cannot get freq (v2/v3): err -11
0
Mär 24 18:59:54 kernel: usb 5-1: 1:3: cannot set freq 48000 (v2/v3): err -110
Mär 24 19:00:07 kernel: usb 5-1: 1:0: usb_set_interface failed (-110)
Mär 24 19:00:12 kernel: usb 5-1: 1:0: usb_set_interface failed (-110)
Mär 24 19:00:18 kernel: usb 5-1: uac_clock_source_is_valid(): cannot
get clock validity for id 9
Mär 24 19:00:18 kernel: usb 5-1: clock source 9 is not valid, cannot use
Mär 24 19:00:23 kernel: usb 5-1: 1:3: cannot get freq (v2/v3): err -11
0


(during both user space errors). So something on a low level seems
off. This occured on Kernel 6.14.

[toc] | [prev] | [next] | [standalone]

#86676

[Multipart message — attachments visible in raw view] — view raw

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

[toc] | [prev] | [next] | [standalone]

#86677

Hi Uwe,


On 30.03.25 18:01, Uwe Kleine-König wrote:
> Hello Richard,
> 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).


Good call, I'll forward that to Framework when I talk to them the next time

> 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?


Exactly. Recently it's usually between Fridays and Mondays where it will just randomly not 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)?


It's usually when I plug in my headphone cable. Sometimes that's the first time on that boot or sometimes it worked before. Then no audio device will work at all. Also, in the Gnome system settings, either all audio devices vanish or they are still there, but if I e.g. open that channel test applet and try to play audio through either channel, nothing plays and it seems the applet freezes.


Something I recently  noticed, while Firefox refuses to play back any media when this happens, mpv does, but playback seems a bit distorted, and these messages now appear in the user logs:

Mär 24 18:59:29 pipewire[2927]: spa.alsa: set_hw_params: Connection timed out
Mär 24 18:59:29 pipewire[2927]: pw.node: (alsa_output.usb-Framework_Audio_Expansion_Card-00.analog-stereo-71) suspended -> error (Start error: Connection timed out)
Mär 24 18:59:29 wireplumber[2934]: wp-event-dispatcher: WpAsyncEventHook:0x55fad05c03d0 failed: WpSiStandardLink:0x55fad09f9100 link failed: item deactivated before format was set
Mär 24 18:59:54 pipewire[2927]: spa.alsa: set_hw_params: Connection timed out Mär 24 18:59:54 pipewire[2927]: pw.node: (alsa_output.usb-Framework_Audio_Expansion_Card-00.analog-stereo-71) suspended -> error ((null))
Mär 24 18:59:54 pipewire[2927]: pw.link: 0x559101476130: one of the nodes is in error out:idle in:error
Mär 24 18:59:54 pipewire[2927]: pw.link: 0x559101360b60: one of the nodes is in error out:idle in:error
Mär 24 18:59:56 mpv[10872]: pw.conf: setting config.name to client-rt.conf is deprecated, using client.conf
Mär 24 18:59:56 xdg-desktop-por[3882]: Realtime error: Could not get pidns: Could not fstatat ns/pid: Not a directory
Mär 24 18:59:56 gnome-shell[3248]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed
Mär 24 18:59:56 pipewire[2927]: pw.link: 0x55910157f5b0: one of the nodes is in error out:suspended in:error
Mär 24 18:59:56 pipewire[2927]: pw.link: 0x55910157d590: one of the nodes is in error out:suspended in:error
Mär 24 19:00:28 pipewire[2927]: spa.alsa: set_hw_params: Connection timed out
Mär 24 19:00:28 pipewire[2927]: pw.node: (alsa_output.usb-Framework_Audio_Expansion_Card-00.analog-stereo-71) suspended -> error (Start error: Connection timed out)


and playback in Firefox seems to be broken due to these messages:

Mär 24 18:54:47 pipewire[2927]: spa.alsa: set_hw_params: Connection timed out
Mär 24 18:54:47 pipewire[2927]: pw.node: (alsa_output.usb-Framework_Audio_Expansion_Card-00.analog-stereo-71) suspended -> error (Start error: Connection timed out)
Mär 24 18:54:51 firefox-beta.desktop[7437]: [Child 7437,MediaDecoderStateMachine #4] WARNING: 7f33ca3b73a0 OpenCubeb() failed to init cubeb: file /builds/worker/checkouts/gecko/dom/media/AudioStream.cpp:284
Mär 24 18:54:51 firefox-beta.desktop[7437]: [Child 7437, MediaDecoderStateMachine #4] WARNING: Decoder=7f33d511a700 [OnMediaSinkAudioError]: file /builds/worker/checkouts/gecko/dom/media/MediaDecoderStateMachine.cpp:4633


During these time stamps, the Kernel keeps spamming

Mär 24 18:59:44 kernel: usb 5-1: clock source 9 is not valid, cannot use Mär 24 18:59:49 kernel: usb 5-1: 1:3: cannot get freq (v2/v3): err -110 Mär 24 18:59:54 kernel: usb 5-1: 1:3: cannot set freq 48000 (v2/v3): err -110
Mär 24 19:00:07 kernel: usb 5-1: 1:0: usb_set_interface failed (-110)
Mär 24 19:00:12 kernel: usb 5-1: 1:0: usb_set_interface failed (-110)
Mär 24 19:00:18 kernel: usb 5-1: uac_clock_source_is_valid(): cannot get clock validity for id 9
Mär 24 19:00:18 kernel: usb 5-1: clock source 9 is not valid, cannot use
Mär 24 19:00:23 kernel: usb 5-1: 1:3: cannot get freq (v2/v3): err -110


(during both user space errors). So something on a low level seems off.


Only rebooting helps. I'm currently trying not use the headphone jack expansion module, but the normal USB C module and a USB C to jack adapter I had lying around, that way I can test out if this may be an issue with the expansion card. I also had the battery run empty, remove SSD, RAM, battery and all modules a few days ago after that was recommended by Framework support, but the results are still not in.


> Does the bookworm kernel work on this machine? You could try that then.
> Or the Ubuntu kernel might be worth a try.

I would prefer to use a newer Kernel since on one hand features like VRR are missing from 6.1 (also I don't even know how far that would boot, I did install bookworm originally because at that time the Calamares installer was missing from testing ISO, but I think I at least updated Kernel and Firmware to backports/upstream) and bookworm-backports is probably still missing quite a lot of fixes for various amdgpu issues. And since I'm currently on Kernel 6.14, compiled from source based on the config from 6.12.15, I don't know if another Debian Kernel would be enough.


But yes, trying the Kernel from one of the officially supported Ubuntu or Fedora distros was also recommended by the support, so that would be Ubuntu 22.04, 24.04 or Fedora 41. With Ubuntu, can I just install their .deb package? I would still have to ask Framework support which Kernel they recommend, generic seems to be only v6.8 in 24.04, linux-image-generic-hwe-24.04 is v6.11.0, linux-oem-24.04b is another version of 6.11.0. Though, because of newer Kernel version, I had asked them if they happened to know where I could get sources and config for the latest Kernel in Fedora 41, so I could just put that through "make bindeb-get" and install that one. But they haven't come back to me yet with that one. But if you think that could also be worth a try and happen to know where I can get the parts (or can tell me where I can get their rpm and install the Kernel with that manually), I would try that, at least after verifying the current tests.


Best

Richard

[toc] | [prev] | [next] | [standalone]

#86789

[Multipart message — attachments visible in raw view] — view raw

Hello Richard,

On Sun, Mar 30, 2025 at 06:50:26PM +0200, Richard wrote:
> Only rebooting helps. I'm currently trying not use the headphone jack
> expansion module, but the normal USB C module and a USB C to jack
> adapter I had lying around, that way I can test out if this may be an
> issue with the expansion card. I also had the battery run empty,
> remove SSD, RAM, battery and all modules a few days ago after that was
> recommended by Framework support, but the results are still not in.

Maybe it's worth to try to reload the usb bus driver in the broken
state. Something like:

	# cd -P /sys/bus/usb/devices/usb5/../driver/
	# echo 0000:02:00.0 > unbind
	# echo 0000:02:00.0 > bind

(where 0000:02:00.0 is a link in the directory that the first command
cd'd into). Note that 

a) there might be several device links in that directory, try

	ls -ld /sys/bus/usb/devices/usb5

   to determine the right one.

b) While I expect that the format of the device string matches mine, it
   might also be something completely different.

c) When unbinding the usb bus driver your USB keyboard might stop
   working. So either do bind and unbind in a single line (and hope that
   binding works again :-), or do that via network (or with a PS/2
   keyboard).

> > Does the bookworm kernel work on this machine? You could try that then.
> > Or the Ubuntu kernel might be worth a try.
> 
> I would prefer to use a newer Kernel since on one hand features like
> VRR are missing from 6.1 (also I don't even know how far that would
> boot, I did install bookworm originally because at that time the
> Calamares installer was missing from testing ISO, but I think I at
> least updated Kernel and Firmware to backports/upstream) and
> bookworm-backports is probably still missing quite a lot of fixes for
> various amdgpu issues. And since I'm currently on Kernel 6.14,
> compiled from source based on the config from 6.12.15, I don't know if
> another Debian Kernel would be enough.
> 
> 
> But yes, trying the Kernel from one of the officially supported Ubuntu
> or Fedora distros was also recommended by the support, so that would
> be Ubuntu 22.04, 24.04 or Fedora 41. With Ubuntu, can I just install
> their .deb package? I would still have to ask Framework support which
> Kernel they recommend, generic seems to be only v6.8 in 24.04,
> linux-image-generic-hwe-24.04 is v6.11.0, linux-oem-24.04b is another
> version of 6.11.0. Though, because of newer Kernel version, I had
> asked them if they happened to know where I could get sources and
> config for the latest Kernel in Fedora 41, so I could just put that
> through "make bindeb-get" and install that one. But they haven't come
> back to me yet with that one. But if you think that could also be
> worth a try and happen to know where I can get the parts (or can tell
> me where I can get their rpm and install the Kernel with that
> manually), I would try that, at least after verifying the current
> tests.

I tried installing an Ubuntu (noble) kernel in a Debian 12 VM. While
this worked and produced a booting system, it pulled in quite some
dependencies, so it might get hard to restore an all-Debian system
afterwards.

Best regards
Uwe

[toc] | [prev] | [next] | [standalone]

#87677

[Multipart message — attachments visible in raw view] — view raw

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

[toc] | [prev] | [next] | [standalone]

#87767

[Multipart message — attachments visible in raw view] — view raw

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

[toc] | [prev] | [next] | [standalone]

#88480

Hi Uwe,

I've got some interesting news. I now used Fedora 42 for 12 days without any issues. So today I started booting Ubuntu 25.04 from USB, and after just over an hour of usage the issue appeared. So whatever the cause is, it seems to be limited to Debian and its derivatives. while Fedora doesn't seem to be affected at all. So whatever the cause is, it's not due to anything I did, it's there by default.

I also tried your recommendations: aplay -l did in fact still show the expansion card, and so did lsusb. systemctl soft-reboot did not fix anything, though I'll check out both again the next time this issue happens on my Debian system.


Best regards

Richard

[toc] | [prev] | [next] | [standalone]

#89331

[Multipart message — attachments visible in raw view] — view raw

And another thing I noted: while it seems this issue can also affect USB-to-jack adapters, plugging in one into the laptop while the headphone jack module is down, it will work. So it doesn't seem to take down the whole audio system with it,


Best regards

Richard

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web