alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Guido Aulisi <guido.aulisi@gmail.com>
To: Daniel Mack <zonque@gmail.com>
Cc: tiwai@suse.de, alsa-devel@alsa-project.org,
	nicholas.bailey@glasgow.ac.uk
Subject: Re: [PATCH v2] ALSA: snd-usb-usx2y: remove bogus frame checks
Date: Sun, 06 Oct 2013 10:29:23 +0200	[thread overview]
Message-ID: <1381048163.1974.5.camel@yoda.heavyware> (raw)
In-Reply-To: <1380728990-8443-1-git-send-email-zonque@gmail.com>

> Next time, when detecting such problems, please consider sending a
patch
> to alsa-devel, so fixes make it to the users eventually :)

You are right, but I thought it was a problem with a broken/weird usb
controller, because it worked with my old laptop.
When I saw another user with the same problem, I sent the patch to LAU
(the only mailing list I've subscribed to).

Now I remember why I did that patch: if you see my dmesg output without
that patch, you can see that the driver is comparing 1024 to 0. If you
check the history of the driver, you can see that this check has already
been narrowed with the bit AND operation; I tried to narrow the check a
little more, so I chose 0x3ff because 1024 & 0x3ff = 0.
But I forgot about my Tascam (because I bought a RME Raydat) and never
tested that patch, but I was quite confident that it should work.

[  669.312765] ALSA sound/usb/usx2y/usbusx2yaudio.c:141 should not be
here with counts=42
[  669.329821] ALSA sound/usb/usx2y/usbusx2yaudio.c:141 should not be
here with counts=42
[  669.345854] ALSA sound/usb/usx2y/usbusx2yaudio.c:141 should not be
here with counts=42
[  669.471627] ALSA sound/usb/usx2y/usbusx2yaudio.c:311 Sequence
Error!(hcd_frame=3 ep=10out;wait=1024,frame=0).
Most probably some urb of usb-frame 1024 is still missing.
Cause could be too long delays in usb-hcd interrupt handling.
[ 1203.531392] ALSA sound/usb/usx2y/usbusx2yaudio.c:311 Sequence
Error!(hcd_frame=4 ep=8in;wait=1025,frame=1).
Most probably some urb of usb-frame 1025 is still missing.
Cause could be too long delays in usb-hcd interrupt handling.
[ 1218.908160] ALSA sound/usb/usx2y/usbusx2yaudio.c:311 Sequence
Error!(hcd_frame=5 ep=8in;wait=1026,frame=2).
Most probably some urb of usb-frame 1026 is still missing.

Ciao a tutti
Guido

  parent reply	other threads:[~2013-10-06  8:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-02 15:49 [PATCH v2] ALSA: snd-usb-usx2y: remove bogus frame checks Daniel Mack
2013-10-03 10:25 ` [PATCH v2] ALSA: snd-usb-usx2y: remove bogus frame checks -- SUCCESS Dr Nicholas J Bailey
2013-10-07  7:35   ` Takashi Iwai
2013-10-06  8:29 ` Guido Aulisi [this message]
2013-10-07  7:41   ` [PATCH v2] ALSA: snd-usb-usx2y: remove bogus frame checks Takashi Iwai
2013-10-07 14:58   ` Dr Nicholas J Bailey
2013-10-07 15:11     ` Daniel Mack
2013-10-07 15:35       ` Takashi Iwai
2013-10-07 15:34         ` Daniel Mack
2013-10-07 16:20           ` Dr Nicholas J Bailey
2013-10-07 16:31           ` Dr Nicholas J Bailey

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=1381048163.1974.5.camel@yoda.heavyware \
    --to=guido.aulisi@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=nicholas.bailey@glasgow.ac.uk \
    --cc=tiwai@suse.de \
    --cc=zonque@gmail.com \
    /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).