Date: Wed, 24 Feb 2016 00:13:16 +0100 From: Andreas Longwitz <longwitz@incore.de> To: Hans Petter Selasky <hps@selasky.org> Cc: freebsd-isdn@freebsd.org Subject: Re: chan_capi error after update Message-ID: <56CCE78C.1020509@incore.de> In-Reply-To: <56CAB08C.7000309@selasky.org> References: <56C6E0D4.5060603@incore.de> <56C74704.6060606@selasky.org> <56C83752.6080708@selasky.org> <56C87494.6020605@incore.de> <56C87F06.1070504@selasky.org> <56C88301.3060104@selasky.org> <56C89326.4030803@incore.de> <56C895EA.5000404@selasky.org> <56CA4059.7060601@incore.de> <56CAB08C.7000309@selasky.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Hans,
the message that bothered me was
ERROR[8810] chan_capi.c: CAPI error sending CAPI_FACILITY_REQ ...
with error code 0x1101 (= CAPI_ERROR_INVALID_APPLICATION_ID).
In chan_capi 2.0.3 the application was registered with capi20_register()
on startup direct from load_module() via capi_application_alloc(), that
worked fine.
In chan_capi 2.0.17 the application will be registered with
capi20_register() in the capi_do_monitor thread in function
capi_application_restart(). Therefore the main thread should wait until
registration is done. After introducing the following patch all error
messages on startup are gone:
--- chan_capi.c.orig 2016-02-20 15:55:36.000000000 +0100
+++ chan_capi.c 2016-02-23 21:38:15.144667154 +0100
@@ -8309,6 +8309,9 @@
*/
capi_application[0] = p_app;
+ /* wait until capi_do_monitor has called capi20_register() */
+ sleep(2);
+
cc_mutex_lock(&p_app->lock);
app_locked = 1;
--
Thanks again for help, with kindly regards
Andreas Longwitz
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?56CCE78C.1020509>