alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Dr Nicholas J Bailey <nicholas.bailey@glasgow.ac.uk>
To: alsa-devel@alsa-project.org
Subject: Re: snd-usb-usx2y (Tascam US-122) sequence errors
Date: Mon, 30 Sep 2013 12:09:39 +0100	[thread overview]
Message-ID: <2157722.DYiUDh07P6@arial> (raw)
In-Reply-To: <1879797.EMyhs7R6HO@arial>

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).
> 

  reply	other threads:[~2013-09-30 11:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-28 14:30 snd-usb-usx2y (Tascam US-122) sequence errors Dr Nicholas J Bailey
2013-09-30 11:09 ` Dr Nicholas J Bailey [this message]
2013-09-30 17:07 ` snd-usb-usx2y (Tascam US-122) sequence errors -- PLEASE FIX Dr Nicholas J Bailey
2013-10-02 13:38   ` Daniel Mack

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2157722.DYiUDh07P6@arial \
    --to=nicholas.bailey@glasgow.ac.uk \
    --cc=alsa-devel@alsa-project.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).