From: Jonathan W. <jw...@ju...> - 2012-05-19 06:23:28
|
Hi all On Fri, May 18, 2012 at 04:48:37PM +0200, Yves Grenier wrote: > I am pursuing these tests with Saffire Pro 24 and svn (rev 2149) and am > facing yet another problem. > > My Pro 24 is powered, jack is not yet started, I start the command > "ffado-test BusReset". It prints several lines up to "Doing busreset on > port 0" and then nothing... Never gives back control to the terminal! Hmm, this is most interesting because of something else that I've noted recently. I'm presently running a preempt 3.2.4 kernel, and I've noticed that if I carry out the following steps with a Fireface 800 the computer locks hard: 1) Boot PC 2) Power up ff800 3) Start jack. It runs normally. 4) Ctrl-C jack. It exits just fine with no errors. 5) Turn off the FF800 6) Within 10 seconds the computer has locked up I'm yet to test whether steps 3 and 4 are necessary - it's on my list of things to do. Similarly, I haven't tested other interfaces to see if they give rise to similar problems. I mention this because turning a device off will produce a bus reset, and it seems I'm seeing some odd behaviour in connection with this, as Yves is. I have no idea whether this observation is linked to what Yves is seeing or not. There is a point in common - bus resets - but I'll see if I can narrow things down further over the coming days. My workaround at present is to simply not power the FF800 off. > A side effect is that I may start jack in a terminal with "jackd -d > firewire" but I cannot start jack with qjackctl, since qjackctl gets > blocked and does not respond after I clicked on start. I need to kill > qjackctl, qjackctl.real before I can start jackd again inthe terminal. That's odd. I can't see how any of this would affect qjackctl and yet not jackd itself. Hmm. Regards jonathan |