The reason I suggested aplay is only because it terminates after a finite time, reducing the amount of output produced. Today I found that I have similar issues if I plug my audio dongle into one particular Asmedia USB 3.1 controller. I quickly confirmed your finding that aplay has different symptoms - audio is slowed down and distorted, but no errors in dmesg. Same for Jack in playback only mode. I need to use Jack in full duplex to reproduce your symptoms. I automatically stop Jack with timeout to control dmesg pollution: timeout -s KILL 0.1 jackd -d alsa -d hw:3 -p 48 -n 2 The root cause appears to be that there are those "missed service" and "underrun" errors in the first place. One means that the controller failed to execute a transfer in its scheduled (micro)frame for internal reasons or that the transfer was queued too late by software, the other means that the controller ran out of queued data to send. I could believe that maybe we are scheduling transfers too late, causing these problems, but no idea why it only happens on particular "bad" host controller, while othres are OK even on the same machine. In my case, I don't observe the sequence of "missed service" followed by "underrun" and I don't see the subsequent "WARNs" either. However, I produced a patch which should fix this problem. I produced a second patch which improves handling of "missed service" errors, by reporting them faster to the audio driver. My hope was that *maybe* this would speed up recovery from such condition and reduce the disruption created, but it frankly doesn't seem to make much difference. If you would like to play with the patches, I recommend using the distribution's kernel config (/lib/modules/`uname -r`/build/.config) because doing 'make menuconfig' from scratch takes a while nowadays. Regards, Michal
