* ALSA error : frame 0 active: -75 @ 2010-11-12 8:35 Rajul Kumar 2010-11-12 8:46 ` Clemens Ladisch 0 siblings, 1 reply; 6+ messages in thread From: Rajul Kumar @ 2010-11-12 8:35 UTC (permalink / raw) To: alsa-devel; +Cc: tiwai, clemens Hi , we are doing audio streaming using linux usb audio class interface . sometimes when we start usb audio streaming , we get first this error : ALSA sound/usb/usbaudio.c:354: frame 0 active: -75 which is followed by coninous loop of below messages : ALSA sound/usb/usbaudio.c:354: frame 0 active: -71 ALSA sound/usb/usbaudio.c:354: frame 0 active: -71 ALSA sound/usb/usbaudio.c:354: frame 0 active: -71 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 ...... and so on can i be suggested regarding the significance of error : -75 , and the way to resolve this error . Thanx & Regards Rajul ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: ALSA error : frame 0 active: -75 2010-11-12 8:35 ALSA error : frame 0 active: -75 Rajul Kumar @ 2010-11-12 8:46 ` Clemens Ladisch 2010-11-12 9:02 ` Rajul Kumar 0 siblings, 1 reply; 6+ messages in thread From: Clemens Ladisch @ 2010-11-12 8:46 UTC (permalink / raw) To: Rajul Kumar; +Cc: tiwai, alsa-devel Rajul Kumar wrote: > ALSA sound/usb/usbaudio.c:354: frame 0 active: -75 -75 = -EOVERFLOW > which is followed by coninous loop of below messages : > > ALSA sound/usb/usbaudio.c:354: frame 0 active: -71 -71 = -EPROTO > ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 -18 = -EXDEV Documentation/usb/error-codes.txt says: | -EOVERFLOW (*) The amount of data returned by the endpoint was | greater than either the max packet size of the | endpoint or the remaining buffer size. "Babble". | -EPROTO (*, **) a) bitstuff error | b) no response packet received within the | prescribed bus turn-around time | c) unknown USB error | -EXDEV ISO transfer only partially completed | look at individual frame status for details | (*) Error codes like -EPROTO, -EILSEQ and -EOVERFLOW normally indicate | hardware problems such as bad devices (including firmware) or cables. Regards, Clemens ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: ALSA error : frame 0 active: -75 2010-11-12 8:46 ` Clemens Ladisch @ 2010-11-12 9:02 ` Rajul Kumar 2010-11-12 10:00 ` Irfan Shaikh 0 siblings, 1 reply; 6+ messages in thread From: Rajul Kumar @ 2010-11-12 9:02 UTC (permalink / raw) To: Clemens Ladisch; +Cc: tiwai, alsa-devel Hi , Thanx for the reply . i have a few more queries . please find time to guide regarding these . 1) is it possible to have some software solution from audio class driver for -EOVERFLOW condition ? 2) As depicted from error-codes.txt , -EOVERFLOW can be indicative of hardware problem also . Can we be suggested how we can make sure that problem lies in the hardware only ( i mean via some code in usb stack or anything else ) . 3) Are there some mandatory H/W requirements for iso transfer usb signal which may not be required for bulk or other transfers , without which iso transfers can report H/W errors anytime ? how can usb signal be improved so as to perfectly support iso transfers ? Thanx & Regards Rajul On Fri, Nov 12, 2010 at 2:16 PM, Clemens Ladisch <clemens@ladisch.de> wrote: > Rajul Kumar wrote: >> ALSA sound/usb/usbaudio.c:354: frame 0 active: -75 > > -75 = -EOVERFLOW > >> which is followed by coninous loop of below messages : >> >> ALSA sound/usb/usbaudio.c:354: frame 0 active: -71 > > -71 = -EPROTO > >> ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 > > -18 = -EXDEV > > Documentation/usb/error-codes.txt says: > | -EOVERFLOW (*) The amount of data returned by the endpoint was > | greater than either the max packet size of the > | endpoint or the remaining buffer size. "Babble". > > | -EPROTO (*, **) a) bitstuff error > | b) no response packet received within the > | prescribed bus turn-around time > | c) unknown USB error > > | -EXDEV ISO transfer only partially completed > | look at individual frame status for details > > | (*) Error codes like -EPROTO, -EILSEQ and -EOVERFLOW normally indicate > | hardware problems such as bad devices (including firmware) or cables. > > > Regards, > Clemens > ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: ALSA error : frame 0 active: -75 2010-11-12 9:02 ` Rajul Kumar @ 2010-11-12 10:00 ` Irfan Shaikh 2010-11-12 10:10 ` Rajul Kumar 0 siblings, 1 reply; 6+ messages in thread From: Irfan Shaikh @ 2010-11-12 10:00 UTC (permalink / raw) To: Rajul Kumar, Clemens Ladisch; +Cc: tiwai@suse.de, alsa-devel@alsa-project.org Increase the size of your Capture Buffer in capture device (USB audio class) I guess this would help you in solving the Overrun problem ________________________________________ From: alsa-devel-bounces@alsa-project.org [alsa-devel-bounces@alsa-project.org] On Behalf Of Rajul Kumar [rajul.manit1@gmail.com] Sent: Friday, November 12, 2010 2:32 PM To: Clemens Ladisch Cc: tiwai@suse.de; alsa-devel@alsa-project.org Subject: Re: [alsa-devel] ALSA error : frame 0 active: -75 Hi , Thanx for the reply . i have a few more queries . please find time to guide regarding these . 1) is it possible to have some software solution from audio class driver for -EOVERFLOW condition ? 2) As depicted from error-codes.txt , -EOVERFLOW can be indicative of hardware problem also . Can we be suggested how we can make sure that problem lies in the hardware only ( i mean via some code in usb stack or anything else ) . 3) Are there some mandatory H/W requirements for iso transfer usb signal which may not be required for bulk or other transfers , without which iso transfers can report H/W errors anytime ? how can usb signal be improved so as to perfectly support iso transfers ? Thanx & Regards Rajul On Fri, Nov 12, 2010 at 2:16 PM, Clemens Ladisch <clemens@ladisch.de> wrote: > Rajul Kumar wrote: >> ALSA sound/usb/usbaudio.c:354: frame 0 active: -75 > > -75 = -EOVERFLOW > >> which is followed by coninous loop of below messages : >> >> ALSA sound/usb/usbaudio.c:354: frame 0 active: -71 > > -71 = -EPROTO > >> ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 > > -18 = -EXDEV > > Documentation/usb/error-codes.txt says: > | -EOVERFLOW (*) The amount of data returned by the endpoint was > | greater than either the max packet size of the > | endpoint or the remaining buffer size. "Babble". > > | -EPROTO (*, **) a) bitstuff error > | b) no response packet received within the > | prescribed bus turn-around time > | c) unknown USB error > > | -EXDEV ISO transfer only partially completed > | look at individual frame status for details > > | (*) Error codes like -EPROTO, -EILSEQ and -EOVERFLOW normally indicate > | hardware problems such as bad devices (including firmware) or cables. > > > Regards, > Clemens > _______________________________________________ Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel SASKEN BUSINESS DISCLAIMER: This message may contain confidential, proprietary or legally privileged information. In case you are not the original intended Recipient of the message, you must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message and you are requested to delete it and inform the sender. Any views expressed in this message are those of the individual sender unless otherwise stated. Nothing contained in this message shall be construed as an offer or acceptance of any offer by Sasken Communication Technologies Limited ("Sasken") unless sent with that express intent and with due authority of Sasken. Sasken has taken enough precautions to prevent the spread of viruses. However the company accepts no liability for any damage caused by any virus transmitted by this email. Read Disclaimer at http://www.sasken.com/extras/mail_disclaimer.html ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: ALSA error : frame 0 active: -75 2010-11-12 10:00 ` Irfan Shaikh @ 2010-11-12 10:10 ` Rajul Kumar 2010-11-12 10:42 ` Irfan Shaikh 0 siblings, 1 reply; 6+ messages in thread From: Rajul Kumar @ 2010-11-12 10:10 UTC (permalink / raw) To: Irfan Shaikh; +Cc: tiwai@suse.de, alsa-devel@alsa-project.org, Clemens Ladisch Hi , Thanx for your reply . We are simply using audio class driver and linux usb host stack . Can u let me know more regarding which capture buffer size to increase we are doing usb audio streaming on usb host side . Thanx & Regards Rajul On Fri, Nov 12, 2010 at 3:30 PM, Irfan Shaikh <irfan.shaikh@sasken.com> wrote: > Increase the size of your Capture Buffer in capture device (USB audio class) > I guess this would help you in solving the Overrun problem > ________________________________________ > From: alsa-devel-bounces@alsa-project.org [alsa-devel-bounces@alsa-project.org] On Behalf Of Rajul Kumar [rajul.manit1@gmail.com] > Sent: Friday, November 12, 2010 2:32 PM > To: Clemens Ladisch > Cc: tiwai@suse.de; alsa-devel@alsa-project.org > Subject: Re: [alsa-devel] ALSA error : frame 0 active: -75 > > Hi , > > Thanx for the reply . > i have a few more queries . please find time to guide regarding these . > > 1) > is it possible to have some software solution from audio class driver > for -EOVERFLOW condition ? > > 2) > As depicted from error-codes.txt , -EOVERFLOW can be indicative of > hardware problem also . > > Can we be suggested how we can make sure that problem lies in the hardware only > ( i mean via some code in usb stack or anything else ) . > > 3) > > Are there some mandatory H/W requirements for iso transfer usb signal > which may not be required for bulk or other transfers , > without which iso transfers can report H/W errors anytime ? > > how can usb signal be improved so as to perfectly support iso transfers ? > > > Thanx & Regards > Rajul > > > > > On Fri, Nov 12, 2010 at 2:16 PM, Clemens Ladisch <clemens@ladisch.de> wrote: >> Rajul Kumar wrote: >>> ALSA sound/usb/usbaudio.c:354: frame 0 active: -75 >> >> -75 = -EOVERFLOW >> >>> which is followed by coninous loop of below messages : >>> >>> ALSA sound/usb/usbaudio.c:354: frame 0 active: -71 >> >> -71 = -EPROTO >> >>> ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 >> >> -18 = -EXDEV >> >> Documentation/usb/error-codes.txt says: >> | -EOVERFLOW (*) The amount of data returned by the endpoint was >> | greater than either the max packet size of the >> | endpoint or the remaining buffer size. "Babble". >> >> | -EPROTO (*, **) a) bitstuff error >> | b) no response packet received within the >> | prescribed bus turn-around time >> | c) unknown USB error >> >> | -EXDEV ISO transfer only partially completed >> | look at individual frame status for details >> >> | (*) Error codes like -EPROTO, -EILSEQ and -EOVERFLOW normally indicate >> | hardware problems such as bad devices (including firmware) or cables. >> >> >> Regards, >> Clemens >> > _______________________________________________ > Alsa-devel mailing list > Alsa-devel@alsa-project.org > http://mailman.alsa-project.org/mailman/listinfo/alsa-devel > > SASKEN BUSINESS DISCLAIMER: This message may contain confidential, proprietary or legally privileged information. In case you are not the original intended Recipient of the message, you must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message and you are requested to delete it and inform the sender. Any views expressed in this message are those of the individual sender unless otherwise stated. Nothing contained in this message shall be construed as an offer or acceptance of any offer by Sasken Communication Technologies Limited ("Sasken") unless sent with that express intent and with due authority of Sasken. Sasken has taken enough precautions to prevent the spread of viruses. However the company accepts no liability for any damage caused by any virus transmitted by this email. > Read Disclaimer at http://www.sasken.com/extras/mail_disclaimer.html > ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: ALSA error : frame 0 active: -75 2010-11-12 10:10 ` Rajul Kumar @ 2010-11-12 10:42 ` Irfan Shaikh 0 siblings, 0 replies; 6+ messages in thread From: Irfan Shaikh @ 2010-11-12 10:42 UTC (permalink / raw) To: Rajul Kumar; +Cc: tiwai@suse.de, alsa-devel@alsa-project.org, Clemens Ladisch usb audio class device itself should be your capture device. i guess you should be opening same audio usb device at time of snd_pcm_open ________________________________________ From: Rajul Kumar [rajul.manit1@gmail.com] Sent: Friday, November 12, 2010 3:40 PM To: Irfan Shaikh Cc: Clemens Ladisch; tiwai@suse.de; alsa-devel@alsa-project.org Subject: Re: [alsa-devel] ALSA error : frame 0 active: -75 Hi , Thanx for your reply . We are simply using audio class driver and linux usb host stack . Can u let me know more regarding which capture buffer size to increase we are doing usb audio streaming on usb host side . Thanx & Regards Rajul On Fri, Nov 12, 2010 at 3:30 PM, Irfan Shaikh <irfan.shaikh@sasken.com> wrote: > Increase the size of your Capture Buffer in capture device (USB audio class) > I guess this would help you in solving the Overrun problem > ________________________________________ > From: alsa-devel-bounces@alsa-project.org [alsa-devel-bounces@alsa-project.org] On Behalf Of Rajul Kumar [rajul.manit1@gmail.com] > Sent: Friday, November 12, 2010 2:32 PM > To: Clemens Ladisch > Cc: tiwai@suse.de; alsa-devel@alsa-project.org > Subject: Re: [alsa-devel] ALSA error : frame 0 active: -75 > > Hi , > > Thanx for the reply . > i have a few more queries . please find time to guide regarding these . > > 1) > is it possible to have some software solution from audio class driver > for -EOVERFLOW condition ? > > 2) > As depicted from error-codes.txt , -EOVERFLOW can be indicative of > hardware problem also . > > Can we be suggested how we can make sure that problem lies in the hardware only > ( i mean via some code in usb stack or anything else ) . > > 3) > > Are there some mandatory H/W requirements for iso transfer usb signal > which may not be required for bulk or other transfers , > without which iso transfers can report H/W errors anytime ? > > how can usb signal be improved so as to perfectly support iso transfers ? > > > Thanx & Regards > Rajul > > > > > On Fri, Nov 12, 2010 at 2:16 PM, Clemens Ladisch <clemens@ladisch.de> wrote: >> Rajul Kumar wrote: >>> ALSA sound/usb/usbaudio.c:354: frame 0 active: -75 >> >> -75 = -EOVERFLOW >> >>> which is followed by coninous loop of below messages : >>> >>> ALSA sound/usb/usbaudio.c:354: frame 0 active: -71 >> >> -71 = -EPROTO >> >>> ALSA sound/usb/usbaudio.c:354: frame 0 active: -18 >> >> -18 = -EXDEV >> >> Documentation/usb/error-codes.txt says: >> | -EOVERFLOW (*) The amount of data returned by the endpoint was >> | greater than either the max packet size of the >> | endpoint or the remaining buffer size. "Babble". >> >> | -EPROTO (*, **) a) bitstuff error >> | b) no response packet received within the >> | prescribed bus turn-around time >> | c) unknown USB error >> >> | -EXDEV ISO transfer only partially completed >> | look at individual frame status for details >> >> | (*) Error codes like -EPROTO, -EILSEQ and -EOVERFLOW normally indicate >> | hardware problems such as bad devices (including firmware) or cables. >> >> >> Regards, >> Clemens >> > _______________________________________________ > Alsa-devel mailing list > Alsa-devel@alsa-project.org > http://mailman.alsa-project.org/mailman/listinfo/alsa-devel > > SASKEN BUSINESS DISCLAIMER: This message may contain confidential, proprietary or legally privileged information. In case you are not the original intended Recipient of the message, you must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message and you are requested to delete it and inform the sender. Any views expressed in this message are those of the individual sender unless otherwise stated. Nothing contained in this message shall be construed as an offer or acceptance of any offer by Sasken Communication Technologies Limited ("Sasken") unless sent with that express intent and with due authority of Sasken. Sasken has taken enough precautions to prevent the spread of viruses. However the company accepts no liability for any damage caused by an y virus transmitted by this email. > Read Disclaimer at http://www.sasken.com/extras/mail_disclaimer.html > ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2010-11-12 10:44 UTC | newest] Thread overview: 6+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2010-11-12 8:35 ALSA error : frame 0 active: -75 Rajul Kumar 2010-11-12 8:46 ` Clemens Ladisch 2010-11-12 9:02 ` Rajul Kumar 2010-11-12 10:00 ` Irfan Shaikh 2010-11-12 10:10 ` Rajul Kumar 2010-11-12 10:42 ` Irfan Shaikh
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.