[alsa-devel] overrun in case of record

Mark Brown broonie at opensource.wolfsonmicro.com
Tue Sep 6 20:01:38 CEST 2011

On Tue, Sep 06, 2011 at 03:04:44PM +0530, Rajeev kumar wrote:

> I am using arecord for capturing data.
> #arecord -f dat > t
> overrun!!! (at least 32.949 ms long)
> Overrun issue: The issue is only reproducible if we try to record
> for more than 40 sec.The strange part is that Instead of overrun
> condition generated,
> it will record complete data for 10sec.(This is verified with the
> number of bytes recorded).
> So could you please let me know whether this is an error condition
> or just a warning.

An overrun means that your driver is producing data faster than the
application is reading it and ran out of buffer space.  This may mean
that you're running at the wrong sample rate, or it may mean that your
system is just too slow to do recordings.

> pcm_read error: For this I have seen a bug is locked in the
> bugzila(*Bug 472469* <show_bug.cgi?id=472469> -arecord: input/output
> error ). and the status  is closed saying insufficient data.
> Could you please let me know what is the meaning of this bug? Is it
> like, data is not available in the buffer and pcm_read from the user
> space fails? But why this situation will
> arise?

You'll need to investigate the bug.

More information about the Alsa-devel mailing list