Hello Richard, On Tue, Jun 24, 2025 at 06:09:05PM +0200, Richard wrote: > Hi Uwe, > > it looks like I've spoken too soon. It just happened again on 6.15.3. I'm back to 6.15.2 again to check if it happens there or if something was reintroduced in 6.15.3 that triggers this. > > > Jun 24 17:40:17 kernel: SCSI subsystem initialized > Jun 24 17:40:19 kernel: hid-generic 0003:32AC:0003.0009: hiddev0,hidraw2: USB HID v1.11 Device [Framework DisplayPort Expansion Card] on usb-0000:c1:00.3-1/input1 > Jun 24 17:40:45 kernel: usbhid 1-2.2:1.2: can't add hid device: -110 > Jun 24 17:40:45 kernel: usbhid 1-2.2:1.2: probe with driver usbhid failed with error -110 > Jun 24 17:40:56 kernel: usb 1-4.1: reset full-speed USB device number 7 using xhci_hcd > Jun 24 17:40:56 kernel: usb 1-4.1: reset full-speed USB device number 7 using xhci_hcd > Jun 24 17:41:20 kernel: usb 1-2.2: USB disconnect, device number 9 > Jun 24 17:41:25 kernel: usb 1-2.2: new high-speed USB device number 10 using xhci_hcd > Jun 24 17:41:25 kernel: usb 1-2.2: New USB device found, idVendor=32ac, idProduct=0010, bcdDevice= 0.02 > Jun 24 17:41:25 kernel: usb 1-2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 > Jun 24 17:41:25 kernel: usb 1-2.2: Product: Audio Expansion Card > Jun 24 17:41:25 kernel: usb 1-2.2: Manufacturer: Framework > Jun 24 17:41:25 kernel: 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.000A/input/input19 > Jun 24 17:41:25 kernel: hid-generic 0003:32AC:0010.000A: input,hidraw7: USB HID v1.11 Device [Framework Audio Expansion Card] on usb-0000:c1:00.3-2.2/input2 > Jun 24 17:41:30 kernel: usb 1-2.2: uac_clock_source_is_valid(): cannot get clock validity for id 9 > Jun 24 17:41:30 kernel: usb 1-2.2: clock source 9 is not valid, cannot use > Jun 24 17:41:35 kernel: usb 1-2.2: 1:1: cannot get freq (v2/v3): err -110 > Jun 24 17:41:40 kernel: usb 1-2.2: 1:1: cannot set freq 48000 (v2/v3): err -110 > Jun 24 17:41:46 kernel: usb 1-2.2: uac_clock_source_is_valid(): cannot get clock validity for id 9 > Jun 24 17:41:46 kernel: usb 1-2.2: clock source 9 is not valid, cannot use > Jun 24 17:41:51 kernel: usb 1-2.2: 1:1: cannot get freq (v2/v3): err -110 > Jun 24 17:41:51 kernel: usbhid 1-2.2:1.2: can't add hid device: -110 > Jun 24 17:41:51 kernel: usbhid 1-2.2:1.2: probe with driver usbhid failed with error -110 > Jun 24 17:41:56 kernel: usb 1-2.2: 1:1: cannot set freq 48000 (v2/v3): err -110 > Jun 24 17:42:01 kernel: usb 1-2.2: uac_clock_source_is_valid(): cannot get clock validity for id 9 > Jun 24 17:42:01 kernel: usb 1-2.2: clock source 9 is not valid, cannot use > Jun 24 17:42:06 kernel: usb 1-2.2: 1:1: cannot get freq (v2/v3): err -110 > Jun 24 17:42:11 kernel: usb 1-2.2: 1:1: cannot set freq 48000 (v2/v3): err -110 > Jun 24 17:42:16 kernel: usb 1-2.2: uac_clock_source_is_valid(): cannot get clock validity for id 9 > Jun 24 17:42:16 kernel: usb 1-2.2: clock source 9 is not valid, cannot use > Jun 24 17:42:21 kernel: usb 1-2.2: 1:1: cannot get freq (v2/v3): err -110 > Jun 24 17:42:27 kernel: usb 1-2.2: 1:1: cannot set freq 48000 (v2/v3): err -110 > > > This time around though, not the whole audio systems seems to crash. Audio output via speakers is still available. > > > Sadly, rebinding the driver doesn't seem to be an option still. Upon plugging in headphones to the audio expansion card, I see a new device under /sys/class/sound: > > > card2 -> ../../devices/pci0000:00/0000:00:08.1/0000:c1:00.3/usb1/1-2/1-2.2/1-2.2:1.0/sound/card2 > > > So technically I should be able to do > > > cd -P /sys/class/sound/card2/device/driver > > echo 0000:c1:00.3 > unbind > > > but that only gives me > > > -bash: echo: write error: No such device I would expect echo 1-2.2:1.0 > unbind instead. As long as the device is bound, there is a symlink in the driver dir with the device that you can echo into unbind. As example from my machine: I have /sys/class/sound/card0 pointing to ../../devices/pci0000:00/0000:00:1f.3/sound/card0. uwe@taurus:~$ cd -P /sys/class/sound/card0/device/driver uwe@taurus:/sys/bus/pci/drivers/snd_hda_intel$ ls 0000:00:1f.3 bind module new_id remove_id uevent unbind So I could do: echo 0000:00:1f.3 > /sys/bus/pci/drivers/snd_hda_intel/unbind echo 0000:00:1f.3 > /sys/bus/pci/drivers/snd_hda_intel/bind . > So, not sure what the cause is. You mentioned I could also try to restart the driver of the whole hub. But how would I do so? The expansion card is on bus 1 with three entries: from the data you provided I would expect that you can do that with: cd -P /sys/devices/pci0000:00/0000:00:08.1/driver echo 0000:00:08.1 > unbind echo 0000:00:08.1 > bind Best regards Uwe
Attachment:
signature.asc
Description: PGP signature