Re: [FFADO-user] [FFADO-devel] Experience with Edirol FA-101 / jack2

[Stefan R. <st...@s5...>]

Tomasz Grzelak wrote:
> 2010/3/26 Thomas Orgis <tho...@or...>
>> What I ask: How is it possible that jackd enters a non-recoverable state
>> anyway? I guess it must hang in a system call.

"strace -p PID", with PID being the process ID of jackd (obtained from
"ps x" or whatever) shows which sycalls jackd enters and leaves --- or
is being stuck in when it hangs.

Even more informative is the kernel log:  Start watching it with "tail
-f /var/log/messages" or switch to console 12 which on several
distributions is configured to show the kernel log, the press
[Alt][SysRq][w].  This sends a call trace of any blocked task to the
kernel log.  [Alt][SysRq][h] shows what other SysRq key combinations are
available.  (Not all systems are configured to support SysRq though.)

...
> I'm curious about the new firewire stack as well - I've never tried to use
> it before.
> Can anyone confirm or deny its readiness for FFADO 2.0?

Apart from what Arnold wrote, kernel 2.6.32 or later and libraw1394
2.0.5 are required for FFADO.
-- 
Stefan Richter
-=====-==-=- --== ==-=-
http://arcgraph.de/sr/