[alsa-devel] snd-usb-usx2y (Tascam US-122) sequence errors
I'm on debian jessie,
Linux arial 3.10-3-686-pae #1 SMP Debian 3.10.11-1 (2013-09-10) i686 GNU/Linux
with a Tascam us-122 that has recently stopped working.
When I try to capture with anything, there is a few hundred ms of audio then the capture process stalls and the following dmesg appears:
[ 462.596296] Sequence Error!(hcd_frame=0 ep=8in;wait=1024,frame=0). [ 462.596296] Most probably some urb of usb-frame 1024 is still missing. [ 462.596296] Cause could be too long delays in usb-hcd interrupt handling. [ 477.959230] Sequence Error!(hcd_frame=0 ep=8in;wait=1024,frame=0). [ 477.959230] Most probably some urb of usb-frame 1024 is still missing. [ 477.959230] Cause could be too long delays in usb-hcd interrupt handling.
Before this kernel, the box worked OK. The only think that leads me to believe it might be my fault is that for a very long time, I've had to plug the box in:
[ 445.529271] usb 2-1.6: new full-speed USB device number 5 using ehci-pci [ 445.622076] usb 2-1.6: New USB device found, idVendor=1604, idProduct=8006 [ 445.622086] usb 2-1.6: New USB device strings: Mfr=0, Product=0, SerialNumber=0
then unplug it and plug it in again:
[ 445.972743] usb 2-1.6: USB disconnect, device number 5 [ 447.621519] usb 2-1.6: new full-speed USB device number 6 using ehci-pci [ 447.714462] usb 2-1.6: New USB device found, idVendor=1604, idProduct=8007 [ 447.714471] usb 2-1.6: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 447.834852] usbcore: registered new interface driver snd-usb-usx2y [ 455.194314] usb 2-1.6: USB disconnect, device number 6 [ 457.487433] usb 2-1.6: new full-speed USB device number 7 using ehci-pci [ 457.579960] usb 2-1.6: New USB device found, idVendor=1604, idProduct=8006 [ 457.579969] usb 2-1.6: New USB device strings: Mfr=0, Product=0, SerialNumber=0
to get the firmware to load
[ 457.888884] usb 2-1.6: USB disconnect, device number 7 [ 459.379782] usb 2-1.6: new full-speed USB device number 8 using ehci-pci [ 459.472516] usb 2-1.6: New USB device found, idVendor=1604, idProduct=8007 [ 459.472526] usb 2-1.6: New USB device strings: Mfr=0, Product=0, SerialNumber=0
(green USB light comes on here).
I'm not sure about how to start debugging this; there are many things that could be wrong. If it will help, I'll try and file a bug report; if not please tell me to shut up (prefereably after pointing me at the solution :) )
Nick/.
I found this in Linux Audio Users:
http://linuxaudio.org/mailarchive/lau/2013/5/20/200177
which would indicate that the issue has been current since May, and possibly impacts upon many different sound cards.
Does this still persist with kernel 3.10? My symptoms certainly agree exactly with this. Using alas-tools 1.0.27 with kernel 3.10-3.
Nick/.
On Saturday 28 September 2013 15:30:04 Dr Nicholas J Bailey wrote:
I'm on debian jessie,
Linux arial 3.10-3-686-pae #1 SMP Debian 3.10.11-1 (2013-09-10) i686 GNU/Linux
with a Tascam us-122 that has recently stopped working.
When I try to capture with anything, there is a few hundred ms of audio then the capture process stalls and the following dmesg appears:
[ 462.596296] Sequence Error!(hcd_frame=0 ep=8in;wait=1024,frame=0). [ 462.596296] Most probably some urb of usb-frame 1024 is still missing. [ 462.596296] Cause could be too long delays in usb-hcd interrupt handling. [ 477.959230] Sequence Error!(hcd_frame=0 ep=8in;wait=1024,frame=0). [ 477.959230] Most probably some urb of usb-frame 1024 is still missing. [ 477.959230] Cause could be too long delays in usb-hcd interrupt handling.
Before this kernel, the box worked OK. The only think that leads me to believe it might be my fault is that for a very long time, I've had to plug the box in:
[ 445.529271] usb 2-1.6: new full-speed USB device number 5 using ehci-pci [ 445.622076] usb 2-1.6: New USB device found, idVendor=1604, idProduct=8006 [ 445.622086] usb 2-1.6: New USB device strings: Mfr=0, Product=0, SerialNumber=0
then unplug it and plug it in again:
[ 445.972743] usb 2-1.6: USB disconnect, device number 5 [ 447.621519] usb 2-1.6: new full-speed USB device number 6 using ehci-pci [ 447.714462] usb 2-1.6: New USB device found, idVendor=1604, idProduct=8007 [ 447.714471] usb 2-1.6: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 447.834852] usbcore: registered new interface driver snd-usb-usx2y [ 455.194314] usb 2-1.6: USB disconnect, device number 6 [ 457.487433] usb 2-1.6: new full-speed USB device number 7 using ehci-pci [ 457.579960] usb 2-1.6: New USB device found, idVendor=1604, idProduct=8006 [ 457.579969] usb 2-1.6: New USB device strings: Mfr=0, Product=0, SerialNumber=0
to get the firmware to load
[ 457.888884] usb 2-1.6: USB disconnect, device number 7 [ 459.379782] usb 2-1.6: new full-speed USB device number 8 using ehci-pci [ 459.472516] usb 2-1.6: New USB device found, idVendor=1604, idProduct=8007 [ 459.472526] usb 2-1.6: New USB device strings: Mfr=0, Product=0, SerialNumber=0
(green USB light comes on here).
This was in fact reported in May, but the fix suggested by Guido Aulisi in reply to Julien Claassen on Linux Audio User in May hasn't yet made it into kernel 3.10.
Applying the patch suggested here:
http://linuxaudio.org/mailarchive/lau/2013/5/20/200177
resolved the problem for me.
It is only 4 characters to change. I would very much appreciate it if somebody could do that officially because I don't like building custom kernels. Also, I don't really understand what this patch is doing (except literally, of course) so having somebody who does look at it and accept it would be just great.
Nick/.
On Saturday 28 September 2013 15:30:04 Dr Nicholas J Bailey wrote:
I'm on debian jessie,
Linux arial 3.10-3-686-pae #1 SMP Debian 3.10.11-1 (2013-09-10) i686 GNU/Linux
with a Tascam us-122 that has recently stopped working.
When I try to capture with anything, there is a few hundred ms of audio then the capture process stalls and the following dmesg appears:
[ 462.596296] Sequence Error!(hcd_frame=0 ep=8in;wait=1024,frame=0). [ 462.596296] Most probably some urb of usb-frame 1024 is still missing. [ 462.596296] Cause could be too long delays in usb-hcd interrupt handling. [ 477.959230] Sequence Error!(hcd_frame=0 ep=8in;wait=1024,frame=0). [ 477.959230] Most probably some urb of usb-frame 1024 is still missing. [ 477.959230] Cause could be too long delays in usb-hcd interrupt handling.
Before this kernel, the box worked OK. The only think that leads me to believe it might be my fault is that for a very long time, I've had to plug the box in:
[ 445.529271] usb 2-1.6: new full-speed USB device number 5 using ehci-pci [ 445.622076] usb 2-1.6: New USB device found, idVendor=1604, idProduct=8006 [ 445.622086] usb 2-1.6: New USB device strings: Mfr=0, Product=0, SerialNumber=0
then unplug it and plug it in again:
[ 445.972743] usb 2-1.6: USB disconnect, device number 5 [ 447.621519] usb 2-1.6: new full-speed USB device number 6 using ehci-pci [ 447.714462] usb 2-1.6: New USB device found, idVendor=1604, idProduct=8007 [ 447.714471] usb 2-1.6: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 447.834852] usbcore: registered new interface driver snd-usb-usx2y [ 455.194314] usb 2-1.6: USB disconnect, device number 6 [ 457.487433] usb 2-1.6: new full-speed USB device number 7 using ehci-pci [ 457.579960] usb 2-1.6: New USB device found, idVendor=1604, idProduct=8006 [ 457.579969] usb 2-1.6: New USB device strings: Mfr=0, Product=0, SerialNumber=0
to get the firmware to load
[ 457.888884] usb 2-1.6: USB disconnect, device number 7 [ 459.379782] usb 2-1.6: new full-speed USB device number 8 using ehci-pci [ 459.472516] usb 2-1.6: New USB device found, idVendor=1604, idProduct=8007 [ 459.472526] usb 2-1.6: New USB device strings: Mfr=0, Product=0, SerialNumber=0
(green USB light comes on here).
I'm not sure about how to start debugging this; there are many things that could be wrong. If it will help, I'll try and file a bug report; if not please tell me to shut up (prefereably after pointing me at the solution :) )
Nick/.
Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
On 30.09.2013 19:07, Dr Nicholas J Bailey wrote:
This was in fact reported in May, but the fix suggested by Guido Aulisi in reply to Julien Claassen on Linux Audio User in May hasn't yet made it into kernel 3.10.
Applying the patch suggested here:
http://linuxaudio.org/mailarchive/lau/2013/5/20/200177
resolved the problem for me.
Ok. I have no such device, but if you say the patch works for you, I can cook a patch.
It is only 4 characters to change. I would very much appreciate it if somebody could do that officially because I don't like building custom kernels. Also, I don't really understand what this patch is doing (except literally, of course) so having somebody who does look at it and accept it would be just great.
I can take care for that.
Thanks, Daniel
participants (2)
-
Daniel Mack -
Dr Nicholas J Bailey