You are not logged in.

#1 2024-04-12 19:53:33

talbull
Member
Registered: 2024-04-12
Posts: 2

USB DAC (TEAC AI-101DA) USB connection issues - error -71

Hello,

I'm having a heck of a time troubleshooting a USB audio issue I'm having.

System:
- OS: Arch Linux x86_64
- Kernel: 6.8.2-zen2-1-zen
- DE: Plasma 6.0.3
- Memory: 5983MiB / 63493MiB
- CPU: AMD Ryzen 9 7950X (32) @ 5.881GHz
- GPU: NVIDIA GeForce RTX 3080 Ti
- MOBO: Asus PROART X670E-CREATOR WIFI

DAC:
- TEAC AI-101DA
- Has external power, not USB power

Symptoms:
- If I boot my computer with my DAC turned on it works flawlessly.
- If Arch is already booted and I turn the DAC on, I get "usb 3-2: device descriptor read/64, error -71".
- If I leave the DAC turned on, and then unplug and re-plug the USB cable it works fine again.
- Windows exhibits not of these symptoms.

Troubleshooting attempted so far, + logs:

> lsusb    
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub
Bus 003 Device 003: ID 0489:e0e2 Foxconn / Hon Hai Wireless_Device
Bus 003 Device 004: ID 05ac:024f Apple, Inc. Aluminium Keyboard (ANSI)
Bus 003 Device 005: ID 0b05:19af ASUSTek Computer, Inc. AURA LED Controller
Bus 003 Device 006: ID 045e:075d Microsoft Corp. LifeCam Cinema
Bus 003 Device 007: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 003 Device 008: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 003 Device 017: ID 0644:8051 TEAC Corp. TEAC AI-101 Audio <------------- The DAC
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 004 Device 002: ID 0bda:0411 Realtek Semiconductor Corp. Hub
Bus 004 Device 003: ID 0fd9:006a Elgato Systems GmbH Game Capture HD60 S+
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 002: ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub
Bus 005 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 006 Device 003: ID 0fd9:0066 Elgato Systems GmbH Cam Link 4K
Bus 006 Device 005: ID 0bda:0411 Realtek Semiconductor Corp. Hub
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 009 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 010 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 011 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 012 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> journalctl -b | grep pipewire
Apr 07 13:02:50 tal-pc pipewire-pulse[1258]: mod.protocol-pulse: client 0x5c32c65bfae0 [VLC media player (LibVLC 3.0.20)]: ERROR command:-1 (invalid) tag:4 error:25 (Input/output error)
Apr 07 20:56:55 tal-pc pipewire-pulse[1258]: mod.protocol-pulse: client 0x5c32c6469630 [kded6]: ERROR command:-1 (invalid) tag:4 error:25 (Input/output error)
>sudo alsa force-reload        
sudo: alsa: command not found
> systemctl --user status wireplumber.service 
● wireplumber.service - Multimedia Service Session Manager
     Loaded: loaded (/usr/lib/systemd/
user/wireplumber.service; enabled; preset: enabled)
     Active: active (running) since Sun 2024-04-07 11:14:14 MDT; 9h ago
   Main PID: 1257 (wireplumber)
      Tasks: 7 (limit: 76117)
     Memory: 23.6M (peak: 24.7M)
        CPU: 1.287s
     CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/wireplumber.service
             └─1257 /usr/bin/wireplumber

Apr 07 11:14:14 tal-pc systemd[1245]: Started Multimedia Service Session Manager.
Apr 07 11:14:14 tal-pc wireplumber[1257]: 0x5a2a429c08f0: no
 modules loaded from context.modules
Apr 07 11:14:17 tal-pc wireplumber[1257]: [0:01:00.928350276] [1257] ERROR IPAModule ipa_module.
cpp:172 Symbol ipaModuleInfo not found
Apr 07 11:14:17 tal-pc wireplumber[1257]: [0:01:00.928357966] [1257] ERROR IPAModule ipa_module.
cpp:292 v4l2-compat.so: IPA module has no valid info
Apr 07 11:14:17 tal-pc wireplumber[1257]: [0:01:00.928371986] [1257]  INFO Camera camera_manager
.cpp:284 libcamera v0.2.0
Apr 07 20:55:50 tal-pc wireplumber[1257]: "v4l2" calling after timer exp
iry for 20736:/dev/video0(uvc)
Apr 07 20:55:50 tal-pc wireplumber[1257]: "v4l2" calling after timer exp
iry for 20738:/dev/video2(uvc)
Apr 07 20:55:50 tal-pc wireplumber[1257]: "v4l2" calling after timer exp
iry for 20740:/dev/video4(uvc)
> systemctl --user status pipewire           
● pipewire.service - PipeWire Multimedia Service
     Loaded: loaded (/usr/lib/systemd/use
r/pipewire.service; enabled; preset: enabled)
     Active: active (running) since Sun 2024-04-07 11:14:14 MDT; 9h ago
TriggeredBy: ● pipewire.socket
   Main PID: 1256 (pipewire)
      Tasks: 3 (limit: 76117)
     Memory: 13.6M (peak: 14.3M)
        CPU: 6.358s
     CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire.service
             └─1256 /usr/bin/pipewire

Apr 07 11:14:14 tal-pc systemd[1245]: Started PipeWire Multimedia Service.
> systemctl --user status pipewire-pulse.service 
● pipewire-pulse.service - PipeWire PulseAudio
     Loaded: loaded (/usr/lib/syste
md/user/pipewire-pulse.service; enabled; preset: enabled)
     Active: active (running) since Sun 2024-04-07 11:14:14 MDT; 9h ago
TriggeredBy: ● pipewire-pulse.socket
   Main PID: 1258 (pipewire-pulse)
      Tasks: 3 (limit: 76117)
     Memory: 21.5M (peak: 23.7M)
        CPU: 11.209s
     CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire-pulse.service
             └─1258 /usr/bin/pipewire-pulse

Apr 07 11:14:14 tal-pc systemd[1245]: Started PipeWire PulseAudio.
Apr 07 13:02:50 tal-pc pipewire-pulse[1258]: mod.protocol-pu
lse: client 0x5c32c65bfae0 [VLC media player (LibVLC 3.0.20)]: ERROR command:-1 (invalid) tag:4 
error:25 (Input/output error)
Apr 07 20:56:55 tal-pc pipewire-pulse[1258]: mod.protocol-pu
lse: client 0x5c32c6469630 [kded6]: ERROR command:-1 (invalid) tag:4 error:25 (Input/output erro
r)
> systemctl --user status pipewire-media-session.service 
Unit pipewire-media-session.service could not be found.

Restarting pipewire, pipewire pulse, and wireplumber had no effect.
Rebooting with the DAC on fixes the problem.
Hotplugging the dac fixes the problem.

Reading DMESG logs is where I found the "usb 3-2: device descriptor read/64, error -71" error, pasted here with notes on what I did to trigger it:

[19363.250116] usb 3-3: USB disconnect, device number 10    <------------- I unplug usb
[19363.250281] usb 3-3: Unable to submit urb #5: -19 at snd_usb_queue_pending_output_urbs
[19368.911290] usb 3-3: new high-speed USB device number 11 using xhci_hcd  <------------- I plug usb back in
[19369.143289] usb 3-3: New USB device found, idVendor=0644, idProduct=8051, bcdDevice= 0.17
[19369.143295] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[19369.143297] usb 3-3: Product: TEAC AI-101 Audio
[19369.143299] usb 3-3: Manufacturer: TEAC
[19369.143300] usb 3-3: SerialNumber: ACEGIKMOQSUWY0  
[20118.060572] usb 3-3: USB disconnect, device number 11 <------------- I turn it off
[20118.060736] usb 3-3: cannot submit urb (err = -19)
[20128.348190] usb 3-3: new high-speed USB device number 12 using xhci_hcd <------------- I turn it on
[20129.048588] usb 3-3: device descriptor read/64, error -71 <------------- The error
[20129.387953] usb 3-3: New USB device found, idVendor=0644, idProduct=8051, bcdDevice= 0.17
[20129.387956] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[20129.387958] usb 3-3: Product: TEAC AI-101 Audio
[20129.387959] usb 3-3: Manufacturer: TEAC
[20129.387960] usb 3-3: SerialNumber: ACEGIKMOQSUWY0  
[20145.542210] usb 3-3: USB disconnect, device number 12 <------------- I unplug usb again
[20145.542374] usb 3-3: Unable to submit urb #3: -19 at snd_usb_queue_pending_output_urbs
[20152.890824] usb 3-3: new high-speed USB device number 13 using xhci_hcd <------------- I plug usb in again
[20153.122334] usb 3-3: New USB device found, idVendor=0644, idProduct=8051, bcdDevice= 0.17
[20153.122339] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[20153.122341] usb 3-3: Product: TEAC AI-101 Audio
[20153.122343] usb 3-3: Manufacturer: TEAC
[20153.122344] usb 3-3: SerialNumber: ACEGIKMOQSUWY0

At this point I'm COMPLETELY at a loss, I can't seem to find anyone else having a related problem. any help is appreciated.

Offline

#2 2024-08-22 15:15:51

nemonein
Member
Registered: 2024-08-22
Posts: 1

Re: USB DAC (TEAC AI-101DA) USB connection issues - error -71

Hi. I have the same amp(Teac AI-101DA) and the problem is also the same.
I've search the net, and I've found a work around..
USB rebinding

This worked for me, but.. Every time I turn on the amp, I have to run the script. That's not the actual solution, as well as the script needs root privilege.
By the way, the port address for AI-101DA is "8086:31a8".
So the SERIAL should be,

SERIAL=$(lspci -Dd "8086:31a8" | awk '{ print $1 }')

For me, this does not solve the issue.
I'm thinking about buying a new DAC.

By the way, I've been using this amp for a few years with Cubietruck(as mpd server), but there was no problem.
I've change the main board to a new one, Radxa X2L, and this one must be the curlprit.

Offline

#3 2024-08-22 16:02:56

ua4000
Member
Registered: 2015-10-14
Posts: 485

Re: USB DAC (TEAC AI-101DA) USB connection issues - error -71

or like this, I used for a buggy hdd case:

https://stackoverflow.com/questions/187 … vice-again
1st answer.

Offline

#4 2024-10-01 17:21:00

talbull
Member
Registered: 2024-04-12
Posts: 2

Re: USB DAC (TEAC AI-101DA) USB connection issues - error -71

Neither of those answers worked unfortunately.  I can see the device dropping off of the audio list when I unbind, but same issue, when I re-bind the USB device the light on the dac just stays flashing like it did before, no change from previous behaviour, same error -71 in dmesg.

Offline

#5 2024-10-02 09:37:30

ua4000
Member
Registered: 2015-10-14
Posts: 485

Re: USB DAC (TEAC AI-101DA) USB connection issues - error -71

A wild guess, have a look at usb powersaving:

https://wiki.archlinux.org/title/Power_ … utosuspend
https://docs.kernel.org/admin-guide/ker … eters.html

        usbcore.autosuspend=

And google came up for "error -71" with these three more kernel options:

        usbcore.old_scheme_first=
        usbcore.use_both_schemes=
        usbcore.authorized_default=

Offline

Board footer

Powered by FluxBB