Bug#601657: libffado2 thread crashes with assertion failure

Max Kellermann max at duempel.org
Thu Oct 28 09:41:50 UTC 2010

reopen 601657

On 2010/10/28 11:08, Adrian Knoth <adi at drcomp.erfurt.thur.de> wrote:
> On Thu, Oct 28, 2010 at 09:31:48AM +0200, Max Kellermann wrote:
> > The attached test program can trigger a (timing?) bug in libffado2,
> Welcome to userlevel device drivers. For some reasons, the packets were
> not delivered or received in time.
> Might be a combination of period-size (lower is sometimes better),
> firewire controllers and so on.
> As always, svn trunk might have a fix if it's really a device specific
> error, i.e. misunderstanding of the samplerate in use.
> > ERROR: messagebuffer not initialized: 1250338856611: Warning
> > (ffado.cpp)[ 121] ffado_streaming_init: Realtime scheduling is not
> > enabled. This will cause significant reliability issues.
> You're running it without realtime priorities? Now I see why you get
> the timing issues mentioned above.

You seem to be misunderstanding the problem here.  This is not about a
buffer xrun because the application didn't submit enough PCM samples
in time; this is about a crash due to an assertion failure, i.e. a bug
in libffado2.

Please do not close this bug report until there is a new Debian
revision which does not crash (or until there is evidence that my test
program is bugged, indirectly causing the crash).


More information about the pkg-multimedia-maintainers mailing list