id summary reporter owner description type status priority milestone component version resolution keywords cc device_name 332 FP10 XRuns shuberts I have a "new-everything" setup which I am tying to use with a Presonus FP10, and am seeing XRuns when recording with Ardour. I sometimes experience a JACK shutdown because of an FFADO assert, and I sometimes see a runaway stream of errors which (even on a four-processor system) almost completely lock the system up.\r\n\r\nHere is my ffado-diag output: http://www.pastebay.com/121136 . More info on request.\r\n\r\nI do not see these XRuns when recording through an ALSA device (a USB-based Tascam US-122) or through the motherboard sound system.\r\n\r\nI have downloaded, compiled, and installed the current stable ffado library, and would be more than happy to cooperate with any investigation or debugging exercises that will help resolve this.\r\n\r\nHere is an example failure:\r\n\r\n xxxxx@yyyyy:~$ $SHELL -x .jackdrc 2>&1 | tee jackd.log\r\n 1 + /usr/bin/jackd -P70 -dfirewire -r96000 -p128 -n3\r\n 2 no message buffer overruns\r\n 3 no message buffer overruns\r\n 4 jackdmp 1.9.6\r\n 5 Copyright 2001-2005 Paul Davis and others.\r\n 6 Copyright 2004-2010 Grame.\r\n 7 jackdmp comes with ABSOLUTELY NO WARRANTY\r\n 8 This is free software, and you are welcome to redistribute it\r\n 9 under certain conditions; see the file COPYING for details\r\n 10 JACK server starting in realtime mode with priority 70\r\n 11 00881323442: (ffado.cpp)[ 92] ffado_streaming_init: libffado 2.999.0-1983 built Apr 20 2011 22:16:30\r\n 12 Unknown destination port in attempted (dis)connection src_name [Hydrogen:out_L] dst_name [alsa_pcm:playback_1]\r\n 13 JackEngine::XRun: client = Hydrogen was not run: state = 1\r\n 14 JackEngine::XRun: client Hydrogen finished after current callback\r\n 15 JackPosixMutex::Unlock res = 1\r\n 16 JackAudioDriver::ProcessAsync Process error\r\n 17 JackPosixMutex::Unlock res = 1\r\n 18 JackAudioDriver::ProcessAsync: read error, skip cycle\r\n 19 JackPosixMutex::Unlock res = 1\r\n 20 JackEngine::XRun: client Hydrogen finished after current callback\r\n 21 JackPosixMutex::Unlock res = 1\r\n 22 JackPosixMutex::Unlock res = 1\r\n 23 JackAudioDriver::ProcessAsync Process error\r\n 24 JackFFADODriver::ffado_driver_wait - unhandled xrun\r\n 25 firewire ERR: wait status < 0! (= -1)\r\n 26 JackAudioDriver::ProcessAsync: read error, skip cycle\r\n 27 JackFFADODriver::ffado_driver_wait - unhandled xrun\r\n 28 firewire ERR: wait status < 0! (= -1)\r\n 29 JackAudioDriver::ProcessAsync: read error, skip cycle\r\n 30 JackFFADODriver::ffado_driver_wait - unhandled xrun\r\n 31 firewire ERR: wait status < 0! (= -1)\r\n (flood of above three lines ensues, locking the machine up)\r\n\r\n\r\n\r\nGiven my hardware, I wouldn't expect to see any XRuns at all.\r\n\r\nAny help?\r\n\r\nThanks in advance!\r\n\r\nChris\r\n\r\nP.S. I posted this to ffado-devel list, but thought that I had ought to post it here. bug closed major generic FFADO 2.0.1 worksforme ffado, FP10, XRun flood