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).
This is what I just got as a tip from a Debian maintainer. Maybe someone can take a look at that driver. Experiments still continue.
Happens to me with Debian running Linux 6.12.27.
Was using the expansion card with earphones, everything worked, and boom, everything freezed (including gnome).
After a restart here’s what I notice:
Everything related to audio is frozen (vlc freeze soon, Firefox freezes when it starts to play audio, can’t open pavucontrol) when my jack is plugged-in my expansion card.
When I unplug the jack, everything unfreeze.
The logs:
[ 509.675021] input: Framework Audio Expansion Card Consumer Control as /devices/pci0000:00/0000:00:08.1/0000:c1:00.3/usb1/1-2/1-2.2/1-2.2:1.3/0003:32AC:0010.000D/input/input20
[ 509.731343] hid-generic 0003:32AC:0010.000D: input,hidraw3: USB HID v1.11 Device [Framework Audio Expansion Card] on usb-0000:c1:00.3-2.2/input3
[ 514.995423] usb 1-2.2: uac_clock_source_is_valid(): cannot get clock validity for id 9
[ 514.995443] usb 1-2.2: clock source 9 is not valid, cannot use
[ 520.115188] usb 1-2.2: 1:1: cannot get freq (v2/v3): err -110
[ 525.235271] usb 1-2.2: 1:1: cannot set freq 48000 (v2/v3): err -110
[ 530.359821] usb 1-2.2: uac_clock_source_is_valid(): cannot get clock validity for id 9
[ 530.359842] usb 1-2.2: clock source 9 is not valid, cannot use
[ 535.475307] usbhid 1-2.2:1.3: can't add hid device: -110
[ 535.475312] usb 1-2.2: 1:1: cannot get freq (v2/v3): err -110
[ 535.475340] usbhid 1-2.2:1.3: probe with driver usbhid failed with error -110
[ 540.595214] usb 1-2.2: 1:1: cannot set freq 48000 (v2/v3): err -110
[ 545.715067] usb 1-2.2: uac_clock_source_is_valid(): cannot get clock validity for id 9
[ 545.715083] usb 1-2.2: clock source 9 is not valid, cannot use
[ 550.834887] usb 1-2.2: 1:1: cannot get freq (v2/v3): err -110
[ 555.954979] usb 1-2.2: 1:1: cannot set freq 48000 (v2/v3): err -110
Maybe can this be related to defective jack? My earphone is quite old, the jack works thanks to duck tape, and I won’t be surprised if it’s dead now.
After another reboot, but with jack unpluged, I’m back to a clean situation: clean logs, no freeze, good audio.
If it’s the same issue as mine, it can’t. My current guess is a software issue, as even a replacement headphone jack module couldn’t fix it. I have used a Fedora 41 live USB to boot from since last weekend, yet it hasn’t happened again yet, while it used to be happening roughly weekly. The big question is just what exactly is causing this.
Do you still run into that issue? If so, try installing Linux 6.15. It’s available in experimental.
Running into the same issue on Debian testing with kernel 6.16.3.
[ 3567.868639] usb 1-2.1: new high-speed USB device number 20 using xhci_hcd
[ 3568.008821] usb 1-2.1: New USB device found, idVendor=32ac, idProduct=0010, bcdDevice= 0.02
[ 3568.008828] usb 1-2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 3568.008830] usb 1-2.1: Product: Audio Expansion Card
[ 3568.008832] usb 1-2.1: Manufacturer: Framework
[ 3568.393562] input: Framework Audio Expansion Card Consumer Control as /devices/pci0000:00/0000:00:08.1/0000:c1:00.3/usb1/1-2/1-2.1/1-2.1:1.3/0003:32AC:0010.001A/input/input41
[ 3568.448782] hid-generic 0003:32AC:0010.001A: input,hidraw3: USB HID v1.11 Device [Framework Audio Expansion Card] on usb-0000:c1:00.3-2.1/input3
[ 3573.788757] usb 1-2.1: uac_clock_source_is_valid(): cannot get clock validity for id 9
[ 3573.788765] usb 1-2.1: clock source 9 is not valid, cannot use
[ 3578.904657] usb 1-2.1: 1:1: cannot get freq (v2/v3): err -110
[ 3584.028734] usb 1-2.1: 1:1: cannot set freq 48000 (v2/v3): err -110
[ 3589.149315] usb 1-2.1: uac_clock_source_is_valid(): cannot get clock validity for id 9
[ 3589.149331] usb 1-2.1: clock source 9 is not valid, cannot use
[ 3594.265514] usbhid 1-2.1:1.3: can’t add hid device: -110
[ 3594.265642] usbhid 1-2.1:1.3: probe with driver usbhid failed with error -110
[ 3594.269081] usb 1-2.1: 1:1: cannot get freq (v2/v3): err -110
[ 3599.389369] usb 1-2.1: 1:1: cannot set freq 48000 (v2/v3): err -110
[ 3604.505381] usb 1-2.1: uac_clock_source_is_valid(): cannot get clock validity for id 9
I’ve tried turning off USB autosuspend as well as unloading and reloading snd_usb_audio with different settings. As with others, nothing besides a reboot seems to fix it, and then only for a while. Has anybody been able to figure out a solution?
Nothing even close to that, but at least some progress has been made. It is now known that both Debian and Ubuntu are affected, yet somehow Fedora (most likely unknowingly) found a fix that sadly hasn’t been upstreamed yet.
Also it’s now known that while the kernel version greatly influences the likelyhood of this happens, it doesn’t seem to be a module hanging or something like that. Besides a full reboot, systemctl soft-reboot has a chance to suffice as a fix - including unplugging the audio jack module and plugging it back in afterwards. Sadly even with the -f parameter it recently takes a long time for the soft-reboot to commence, so long as I’ll just hard reset the system. But the fact that this process that only restarts user space helps does give clues. And it explains why reloading the kernel driver has no effect.
I am having this issue as well.
My Audio Expansion Card, today, is causing a lot of problems on my machine. The entire machine hangs - like, Firefox stops responding - while the audio expansion card is plugged in. I also cannot get any audio whatsoever.
When I plug the audio expansion card out, however, the computer instantly “unhangs” itself.
lsusb hangs for 30 seconds right before enumerating the Audio Expansion Card.
DMESG logs:
[ 266.392876] usb 1-2.2: USB disconnect, device number 14
[ 415.577625] usb 1-2.2: new high-speed USB device number 15 using xhci_hcd
[ 415.690623] usb 1-2.2: New USB device found, idVendor=32ac, idProduct=0010, bcdDevice= 0.02
[ 415.690636] usb 1-2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 415.690643] usb 1-2.2: Product: Audio Expansion Card
[ 415.690648] usb 1-2.2: Manufacturer: Framework
[ 415.931843] input: Framework Audio Expansion Card Consumer Control as /devices/pci0000:00/0000:00:08.1/0000:c1:00.3/usb1/1-2/1-2.2/1-2.2:1.2/0003:32AC:0010.0015/input/input34
[ 415.982958] hid-generic 0003:32AC:0010.0015: input,hidraw15: USB HID v1.11 Device [Framework Audio Expansion Card] on usb-0000:c1:00.3-2.2/input2
[ 416.465837] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
[ 420.242667] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
[ 421.332624] usb 1-2.2: uac_clock_source_is_valid(): cannot get clock validity for id 9
[ 421.332637] usb 1-2.2: clock source 9 is not valid, cannot use
[ 426.452601] usb 1-2.2: 1:1: cannot get freq (v2/v3): err -110
[ 431.573608] usb 1-2.2: 1:1: cannot set freq 48000 (v2/v3): err -110
[ 436.692976] usb 1-2.2: uac_clock_source_is_valid(): cannot get clock validity for id 9
[ 436.692989] usb 1-2.2: clock source 9 is not valid, cannot use
[ 441.812612] usb 1-2.2: 1:1: cannot get freq (v2/v3): err -110
[ 441.812693] usbhid 1-2.2:1.2: can't add hid device: -110
[ 441.812796] usbhid 1-2.2:1.2: probe with driver usbhid failed with error -110
[ 446.933378] usb 1-2.2: 1:1: cannot set freq 48000 (v2/v3): err -110
[ 451.012803] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
[ 452.052666] usb 1-2.2: uac_clock_source_is_valid(): cannot get clock validity for id 9
[ 452.052678] usb 1-2.2: clock source 9 is not valid, cannot use
[ 457.172918] usb 1-2.2: 1:1: cannot get freq (v2/v3): err -110
[ 462.292608] usb 1-2.2: 1:1: cannot set freq 48000 (v2/v3): err -110
[ 467.413334] usb 1-2.2: uac_clock_source_is_valid(): cannot get clock validity for id 9
[ 467.413342] usb 1-2.2: clock source 9 is not valid, cannot use
[ 472.532586] usb 1-2.2: 1:1: cannot get freq (v2/v3): err -110
[ 473.541588] ucsi_acpi USBC000:00: unknown error 256
[ 473.541660] ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)
[ 477.653075] usb 1-2.2: 1:1: cannot set freq 48000 (v2/v3): err -110
[ 482.773100] usb 1-2.2: uac_clock_source_is_valid(): cannot get clock validity for id 9
[ 482.773115] usb 1-2.2: clock source 9 is not valid, cannot use
[ 487.893392] usb 1-2.2: 1:1: cannot get freq (v2/v3): err -110
[ 493.013879] usb 1-2.2: 1:1: cannot set freq 48000 (v2/v3): err -110
[ 498.133103] usb 1-2.2: uac_clock_source_is_valid(): cannot get clock validity for id 9
[ 498.133119] usb 1-2.2: clock source 9 is not valid, cannot use
[ 503.252592] usb 1-2.2: 1:1: cannot get freq (v2/v3): err -110
[ 508.373698] usb 1-2.2: 1:1: cannot set freq 48000 (v2/v3): err -110
[ 513.493440] usb 1-2.2: uac_clock_source_is_valid(): cannot get clock validity for id 9
[ 513.493454] usb 1-2.2: clock source 9 is not valid, cannot use
[ 518.613865] usb 1-2.2: 1:1: cannot get freq (v2/v3): err -110
[ 523.732711] usb 1-2.2: 1:1: cannot set freq 48000 (v2/v3): err -110
[ 528.852597] usb 1-2.2: uac_clock_source_is_valid(): cannot get clock validity for id 9
[ 528.852657] usb 1-2.2: clock source 9 is not valid, cannot use
[ 529.223456] i2c_hid_acpi i2c-FRMW0003:00: failed to get a report from device: -121
[ 533.973239] usb 1-2.2: 1:1: cannot get freq (v2/v3): err -110
[ 539.093013] usb 1-2.2: 1:1: cannot set freq 48000 (v2/v3): err -110
[ 544.212596] usb 1-2.2: uac_clock_source_is_valid(): cannot get clock validity for id 9
[ 544.212613] usb 1-2.2: clock source 9 is not valid, cannot use
[ 549.018226] usb 1-4.1: reset full-speed USB device number 9 using xhci_hcd
[ 549.180579] usb 1-4.1: reset full-speed USB device number 9 using xhci_hcd
[ 549.332708] usb 1-2.2: 1:1: cannot get freq (v2/v3): err -110
Really annoying. My PC just doesn’t work anymore with this expansion card plugged in!
System info:
Reboot does not fix anything.
Do you have the same problem on an LTS kernel? If not, then I would open a bug report with the kernel maintainers.
It seems to be the same issue, though a bit different. That has been around since probably 6.10 or 6.11. So you’ll have to go back to 6.6 LTS to excape this (which I’m doing right now, the newer Kernels just have way too many issues at this time, especially with amdgpu.
I’ve got some bad news, that may be good though for figuring out what exactly is wrong. I went back to kernel 6.6.106 because of this and several issues with the amdgpu driver, and it just happened again. So the cause of this must be in some code that was backported to 6.6. I originally set up my FW with Debian 12 (very hacky but doable) and immediately went to testing last year in late april last year. While I don’t remember when exactly this first started to appear, it was definitely in the second half of 2024, most likely Q4. So that would be 6.9 or 6.10. I believe it was even 6.10 or 6.11.
Very curious. My machine was also originally on bookworm, and it only started when I switched to trixie when that became the new stable(I switched to testing in hopes that the issue was fixed upstream, shame on me). I have also tested both pipewire and pulseaudio, and the issue occurs in both. Perhaps it’s a problem with a common dependency like libasound? Though admittedly that’s rampant speculation on my part and I don’t know enough about ALSA to check.
No idea. The only thing I do know is that it’s not the fault of the module (got a replacement, didn’t change anything, also tried a very simple USB C to jack adapter, still same issue), it deeply depends on the Kernel version if the issue appears and how bad it is (actually 6.6.106 have me that issue again just few hours later, and Fedora’s Kernel at least carries some fix that isn’t upstreamed, though that isn’t clear as I have yet to find a way and the time to compile their sources for Debian, not to mention compiling the upstream sources with their config to see if that may be a cause), but if you manage to soft-reboot the system without getting stuck on the dmesg output - which will only reboot the user space - and unplug the jack module and plug it back in, it will work again. Also, aplay will be able to still see the audio device - with Gnome settings it’s very much hit or miss - but fail to do playbacks in various ways.
A lot of information, yet I know way too like about Linux to hazard any guess what the cause could be.
Do you know what the DAC in the dongle you mentioned was? IIRC, the framework audio card uses a Conexant CX31993. If it’s the same chip, that might narrow things down a little
No clue, I don’t even know if it had a DAC. Most likely not, it was basically just a cheap Anker adapter. So I’d have to try it out a proper DAC for that. I can do that at a later point, right now I’m trying out to use Fedora’s Kernel on Debian and next week I’ll be traveling, so it will be a while before I get to this.
If it’s the A8195, which is the USB-C to 3.5mm one, the product page says it does have an integrated DAC, just not which one unfortunately. I’ll need to do a little digging about it.
Yeah, looks like it. No clue if you can tell what DAC it uses without taking it apart. The alternative that I have is a CREATIVE Sound Blaster Play! 4. All I can find out about it is that it supposedly has a Realtek DAC. So if that’s true, it’s definitely something different from FW’s DAC, no matter what’s the exact chip.
I managed to get my hands on a cheapo adapter(an AB136T I believe) and switched to the 6.12 kernel temporarily, since that’s had a pretty high incidence rate in my testing. Once the expansion card died, I switched to the dongle and it still played audio. It was a USB-A to 3.5mm but I don’t think that matters.
An interesting behavior(which may not be relevant) was that the dongle remained a valid audio output even while my headset wasn’t plugged in, in contrast to the expansion card. I have USB autosuspend turned off systemwide as a previous attempt at mitigation but maybe there’s some inbuilt behavior of the expansion card that I’m not aware of?
Amazing, I just tested it myself as my jack module also just stopped working yet again and plugged in the Sound Blaster and it works. And for all I know I didn’t disable USB autosuspend (at least I didn’t set the modprobe option for that).
I just started getting these errors for my audio expansion card too. It’s been working fine for 18 months and now suddenly it starts glitching out.
[ 5803.186322] usb 1-2.3: uac_clock_source_is_valid(): cannot get clock validity for id 9
[ 5803.186338] usb 1-2.3: clock source 9 is not valid, cannot use
[ 5808.306241] usb 1-2.3: 1:3: cannot get freq (v2/v3): err -110
[ 5813.426319] usb 1-2.3: 1:3: cannot set freq 48000 (v2/v3): err -110
I tried rebooting and it didn’t help. I’m on Ubuntu 25.04 with it’s default kernel 6.14.0-29-generic #29-Ubuntu. I’ve been using the latest version of Ubuntu since I got my FW16 in March 2024.
I have another audio expansion card so I will swap it out and see if it has the same problem.
That won’t have any effect. The only thing you can do is plug that one in (no idea if swapping it out can help or if you’ll have to plug it into a USB C module - or if you actually need something completely different) once this appears.
To everyone in this thread, please contact Framework support with this. It seems to me they aren’t really interested in this yet as they seem to believe it doesn’t affect that many people. When they see that more people are affected, maybe they’ll finally talk to the Fedora maintainers to figure out what they are doing differently to prevent this from happening. I’ve had a months long conversation with them, in the end I could tell them it won’t happen with Fedora but not only is Debian affected which they don’t officially support, but Ubuntu is affected too. And now that the trigger of this issue has been backported to at least kernel 6.6, there’s basically no way for users to fix it themselves. And I’m not sure if a bug report to the upstream kernel bug tracker will yield any results.