From: Thomas O. <tho...@or...> - 2010-03-26 09:08:01
|
Am Thu, 25 Mar 2010 08:00:29 +0100 schrieb Tomasz Grzelak <tgr...@gm...>: > But... since the beginning have I had stability problems with the FFADO > driver. It's quite rare, however from time to time it happens (let's say > once per a day or two), no matter whether I fully utilize all my > applications, or just do nothing, and no programs are running. The error I > get is: > > --- > firewire ERR: wait status < 0! (= -1) > DRIVER NT: could not run driver cycle > jack main caught signal 12 > no message buffer overruns > --- That looks familiar... I'm not sure if the most recent freeze is the same (well the first two lines). I more remember this message when trying to start jack and it doesn't work (the Edirol in a bad state or whatnot... reboot helps usually). > I don't know if the error is only Edirol-related or concerns other audio > units as well. > On the mailing list FFADO developers have claimed it's unreproducable. This is the kind of random stability issue that of course is hard to reproduce. Perhaps that is also why I didn't yet try a definite bug report (or perhaps it's more because the box where this happens doesn't have regular internet and while it happens the band is usually standing behind me and waiting for things to run, not for me investigating breakages). What I ask: How is it possible that jackd enters a non-recoverable state anyway? I guess it must hang in a system call. > I have tried different kernels so far with RT patches (2.6.24.x, 2.6.26.x, > and now I run 2.6.29.6) - the situation is still the same. I even changed my > hardware completely a year ago - moved from Asus to Gigabyte, from Athlon to > Intel - unfortunately no joy, the problem persists. (But now I know the > issue is not hardware related :)) Yeah, I also had a lot of combinations... will try the freshest rt kernel now, too (2.6.33.1-rt11). > Now I'm going to make some other checks to clarify whether the problem is > related to FFADO drivers or just my OS (maybe some bugged library or > something...). This is a really frustrating aspect for me: Who to put the blame on? Is it 1. ffado 2. jack 3. kernel ? I suppose that at least the unkillable hang-state can only happen when the kernel firewire code hangs? That may suggest that one should try the new firewire stack... but I get mixed information about this. Perhaps ffado devs can clean that up: Is the new stack supposed (and experienced) to work with ffado 2.0 and recent libraw1394? VCS revisions? Or do I simply experience bugs in the RT kernel patches? > And this is what I would suggest to you as well - try to download and > install a few different audio distributions. The problem with custom distros > is that they may have some incorrect libs, drivers, irq priorities, etc..., > and I assume audio dedicated systems have been tested and configured > correctly to be used in such demanding environments as audio > recording/producing. Well, I'll try to boot AVlinux as live system, perhaps install ubuntu studio on a second partition (sadly, booting from my USB drives doesn't seem to work on this asrock board:-/). But actually, I don't have too high hopes there... What I would like to ask the list: > firewire ERR: wait status < 0! (= -1) > DRIVER NT: could not run driver cycle Isn't there a way for jackd to recover from that point? Reset the firewire device? I know this one as failure pattern that is only resolved by rebooting the machine... Alrighty then, Thomas. |