Re: [Jack-Devel] Jack 1.9.7 on ARM crashes when killing a client

PrevNext  Index
DateSat, 19 Feb 2011 14:22:26 +0100
From Robin Gareus <[hidden] at gareus dot org>
Totorbenh <[hidden] at gmx dot de>, Stéphane Letz <[hidden] at grame dot fr>
Cc"[hidden] at lists dot jackaudio dot org List" <[hidden] at lists dot jackaudio dot org>
In-Reply-Totorbenh Re: [Jack-Devel] Jack 1.9.7 on ARM crashes when killing a client
Follow-Uptorbenh Re: [Jack-Devel] Jack 1.9.7 on ARM crashes when killing a client
Follow-UpStéphane Letz Re: [Jack-Devel] Jack 1.9.7 on ARM crashes when killing a client
On 02/18/2011 12:23 PM, torbenh wrote:
> On Thu, Feb 17, 2011 at 02:01:06PM +0100, Robin Gareus wrote:
[..]
>> 
>> 
>> while you're at it: Would it be unreasonable to ask looking into 
>> ignoring device disconnect?  f.i. have jackd survive and not crash
>> when an interface (eg ALSA-USB) goes away.
>> 
>> No further action should be taken by JACK (well, maybe some
>> hook-script could be invoked or a d-bus command send); some 3rd
>> party software could issue d-bus commands to switch backends.
> 
> i basically did this with tschack. using pyjackd this should be
> working. not well tested, as i dont have an usb soundcard with me
> very often.

I've updated jackdmp and tschack to latest svn/git and check this with a
USB UA-25. annotated logs attached.


	tschack (git 7b7a48d)
terminates with exit 0 if the interface goes away.


	jack2d 1.9.7~svn4120 ( --classic --dbus )
keeps running when the USB/ALSA interface goes away - it no longer
live-locks or crashes. - All JACK clients stall.
With the dbus-version: the backend can be changed. After switching to a
new backend (here: internal card) JACK resumes to run nicely.

After the device had been disconnected, the current port-connections can
no longer be queried (jack_lsp can not connect) until the backend is
re-initialized with `jack_control sm`.
Calling 'switch-master' re-creates the physical output ports and the
information about previous port-connections to the outputs are lost.



Anyway, to come back to the Subject:

svn rev 4119: "Valerio Pilo second CAS for ARMv7 patch." introduces a
problem with jackdbus. All requests time out and it is not possible to
connect to jackdbus at all:
  "JackEngine::ClientActivate wait error ref = 2 name = dbusapi"

reverting the notification behavior in JackEngine.cpp removes that
problem. I assume you may know what's going on; I've just bisected and
not analyzed it.

ciao,
robin

-- 
Robin Gareus
web: http://gareus.org/                mail: [hidden]
lab: http://citu.fr/                   chat: xmpp:[hidden]

Public Key at http://pgp.mit.edu/  http://gareus.org/public.asc
Fingerprint : 7107 840B 4DC9 C948 076D 6359 7955 24F1 4F95 2B42

* Attachment: 'jackd2-svn4120_dbusfix.diff'
content-type: text/x-patch
* Attachment: 'jackd2-svn4120_unplug_device.log'
content-type: text/x-log
* Attachment: 'tschack-7b7a48d_unplug_device.log'
content-type: text/x-log
PrevNext  Index

1298121766.797_0.ltw:2,a <4D5FC412.2070201 at gareus dot org>