[alsa-devel] ALSA error : frame 0 active: -75
rajul.manit1 at gmail.com
Fri Nov 12 10:02:20 CET 2010
Thanx for the reply .
i have a few more queries . please find time to guide regarding these .
is it possible to have some software solution from audio class driver
for -EOVERFLOW condition ?
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 ) .
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
On Fri, Nov 12, 2010 at 2:16 PM, Clemens Ladisch <clemens at 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.
More information about the Alsa-devel