JACK, ffado, unhandled xruns

I’ve been consistently having unhandled xrun problems on a system I just installed. I’m hoping someone can help me figure out how to take care of it. Here’s the entire qjackctl message output from start to stop:

19:32:36.598 JACK is starting... 19:32:36.598 /usr/bin/jackd -dfirewire -r96000 -p2048 -n3 Cannot connect to server socket err = No such file or directory Cannot connect to server socket jack server is not running or cannot be started no message buffer overruns no message buffer overruns no message buffer overruns jackdmp 1.9.8 Copyright 2001-2005 Paul Davis and others. Copyright 2004-2011 Grame. jackdmp comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details JACK server starting in realtime mode with priority 10 19:32:36.635 JACK was started with PID=25098. libffado 2.1.0- built Nov 8 2012 19:31:50 19:32:44.930 JACK connection change. 19:32:44.931 Server configuration saved to "/home/audiodef/.jackdrc". 19:32:44.931 Statistics reset. 19:32:44.942 Client activated. 19:32:44.967 JACK connection graph change. libiec61883 warning: Established connection on channel 0. You may need to manually set the channel on the receiving node. libiec61883 warning: Established connection on channel 1. You may need to manually set the channel on the transmitting node. libiec61883 warning: Established connection on channel 2. You may need to manually set the channel on the receiving node. libiec61883 warning: Established connection on channel 3. You may need to manually set the channel on the transmitting node. JackFFADODriver::ffado_driver_wait - unhandled xrun firewire ERR: wait status < 0! (= -1) JackProcessSync::LockedTimedWait error usec = 5000000 err = Connection timed out Driver is not running Cannot create new client 20:27:45.025 Client deactivated. 20:27:45.027 JACK is stopping... JackProcessSync::LockedTimedWait error usec = 426660 err = Connection timed out JackEngine::ClientDeactivate wait error ref = 2 name = qjackctl JackProcessSync::LockedTimedWait error usec = 85332 err = Connection timed out JackEngine::ClientCloseAux wait error ref = 2 jack main caught signal 15 WARNING: 1 message buffer overruns! no message buffer overruns 20:27:45.331 JACK was stopped successfully.

Just curious; What exactly were those ‘better options’?

I don’t think any of that applies, but anyway, after recompiling my kernel with better options, the problem seems to have gone away.

It would be good to have more details of your setup - what is the firewire device, firewire chipset on the computer, OS details, output from ffado-diag, ffado-test Discover, etc. Have you checked the ffado site for compatibility of you firewire device and chipset (http://www.ffado.org/?q=devicesupport/list and http://subversion.ffado.org/wiki/HostControllers). For firewire questions it is good to post questions to the ffado users list (see http://www.ffado.org/?q=contact)

Just curious; What exactly were those ‘better options’?

Yes, I’m curious as well. I have been having similar problems with my Focusrite Saffire. The interface seems to start up fine, but when I launch a media player such as GNOME Mplayer or try to play a video on youtube, I get the following errors:

Sun Mar 24 12:19:13 2013: e[1me[31mERROR: JackFFADODriver::ffado_driver_wait - unhandled xrune[0m
Sun Mar 24 12:19:13 2013: e[1me[31mERROR: firewire ERR: wait status < 0! (= -1)e[0m
Sun Mar 24 12:19:13 2013: e[1me[31mERROR: JackAudioDriver::ProcessAsync: read error, stopping…e[0m
Sun Mar 24 12:19:13 2013: Jack: JackPosixThread::ThreadHandler : exit

Also, the system was outputting sound at one point, even playing mp3s using Banshee. However, it is very unstable.

it might be an idea to take this to the ffado mailing list… the devs and users are pretty responsive, and it may be of wider benefit to ffado users.