alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Mack <zonque-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Ankit Agarwal <ankitgenius90-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: alsa-devel-K7yf7f+aM1XWsZ/bQMPhNw@public.gmane.org,
	"linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [alsa-devel] alsa crash with “ ALSA sound/usb/urb.c:179 cannot submit urb (err = -27)” on imx6q sabrelite
Date: Wed, 11 Sep 2013 14:55:42 +0200	[thread overview]
Message-ID: <5230684E.6030900@gmail.com> (raw)
In-Reply-To: <CAFT5LgKjrYhZ4=cQE7PVBut6L3RvFsR3B16PUUtvEC5cqZLwpg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On 11.09.2013 14:53, Ankit Agarwal wrote:
> 
> On Sun, Sep 8, 2013 at 8:27 PM, Daniel Mack <zonque-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
> <mailto:zonque-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>> wrote:
> 
>     On 02.09.2013 12:51, Ankit Agarwal wrote:
>     > I am using alsa pcm player to listen to audio. The alsa pcm
>     crashes with
>     > the error: ALSA sound/usb/urb.c:179 cannot submit urb (err = -27).
>     I am
>     > able to hear the data initially but when other transaction begins
>     on HID
>     > report endpoint, alsa crashes with the mentioned error.
> 
>     -27 == -EFBIG, which seems to relate to a scheduling problem on the bus,
>     and hence probably rather to a host controller bug than an issue with
>     snd-usb.
> 
>     > I am working on imx6q board with linux kernel-3.0.35. I am using Apple
>     > device to get the digital audio.
> 
>     Please try with a more recent kernel, and see if you can find the
>     location where EFBIG is initially reported.
> 
> 
> I have found that EFBIG is being reported by ehci-host controller. It is
> coming from file ehci-sched.c under iso_stream_schedule() function. The
> error is thrown when the controller tries to schedule the urb too far
> into the future, ie, there is overflow of the scheduled URBs. I might be
> happening because the URBs are not scheduled properly.

Ok. What about trying a newer kernel? The issue might be fixed already.

In any case, this does not seem related to snd-usb, so I copied the usb
list.


Daniel


--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2013-09-11 12:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-02 10:51 alsa crash with “ ALSA sound/usb/urb.c:179 cannot submit urb (err = -27)” on imx6q sabrelite Ankit Agarwal
2013-09-08 14:57 ` Daniel Mack
     [not found]   ` <CAFT5LgKjrYhZ4=cQE7PVBut6L3RvFsR3B16PUUtvEC5cqZLwpg@mail.gmail.com>
     [not found]     ` <CAFT5LgKjrYhZ4=cQE7PVBut6L3RvFsR3B16PUUtvEC5cqZLwpg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-09-11 12:55       ` Daniel Mack [this message]
     [not found]         ` <5230684E.6030900-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-09-11 14:48           ` [alsa-devel] " Alan Stern

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=5230684E.6030900@gmail.com \
    --to=zonque-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=alsa-devel-K7yf7f+aM1XWsZ/bQMPhNw@public.gmane.org \
    --cc=ankitgenius90-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).