FreeBSD 7 and zaptel-bsd

not yet its to early. .0 in beta 1 come on  give us time. 

On Friday 02 November 2007 01:55:58 Tony wrote:
> FreeBSD 7.0 is now in beta[1] . Has anybody had any
luck getting
> zaptel-bsd to work under FreeBSD 7?
>
> I have compiled it up but I seem to be getting a
hanging / lockup
> problem similar to what is described back here -
> http://lists.digium.com/pipermail/asterisk-
bsd/2005-March/000681.html .
>
> Running with zttest with ztdummy loaded works fine
until I attempt to
> CTRL-C to exit. At this point the process hangs and is
unkillable. The
> "ps" command shows it in state "D"
which is "Marks a process in disk
> (or other short term, uninteruptible) wait." . The
main asterisk
> process also locks up and becomes unkillable if it
tryed to use the
> ztdummy timer. Same configuration works fine under
FreeBSD 6.
>
> Has anybody else seen this problem and if so, is there
a solution?
>
>    Tony
>
> Links:
> ------
> [1] http://www
.freebsd.org/where.html#helptest



-- 
Welcome to the World. An the World gets smaller.

_______________________________________________
--Bandwidth and Colocation Provided by http://www.api-digital.c
om--

Asterisk-BSD mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-bsd

Em Sex, 2007-11-02 ās 12:55 +1100, Tony escreveu:
> 
> FreeBSD 7.0 is now in beta . Has anybody had any luck
getting
> zaptel-bsd to work under FreeBSD 7?
The zaptel module as version 1.4.6  (in the ports) really
locks in the
kernel in the "destroy" function. 
In release freebsd prior to 7.0 the destroy does not
"destroy"  de
entries in /dev and silent ignores it... But in 7.0 it waits
for
something (may be to free/unlock) all the resources.. 
A rapid solution is to ignore the destroy call in zaptel
close
routine...
=======================================







--- zaptel/zaptel.c.orig        2007-01-26
08:51:48.000000000 +0000
+++ zaptel/zaptel.c     2007-11-10 13:15:51.000000000 +0000
 -396,7
+396,7 
 
 int schluffen(void *q)
 {
-       int rc = tsleep(q, PZERO | PCATCH,
"schluffen", 0);
+       int rc = tsleep(q, PZERO | PCATCH,
"schluffen", 10);
        switch(rc)
        {
                case EINTR:
 -675,7
+675,7 
        /* Free dev_info, if exist */
        if(dev->si_drv2) free(dev->si_drv2, M_ZAP);
        dev->si_drv2 = NULL;
-       destroy_dev(dev);
+//     destroy_dev(dev);
        return res;
 }
 













_______________________________________________
--Bandwidth and Colocation Provided by http://www.api-digital.c
om--

Asterisk-BSD mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-bsd

User Lenzi wrote:
> Em Sex, 2007-11-02 ās 12:55 +1100, Tony escreveu:
>   
>> FreeBSD 7.0 is now in beta . Has anybody had any
luck getting
>> zaptel-bsd to work under FreeBSD 7?
>>     
> The zaptel module as version 1.4.6  (in the ports)
really locks in the
> kernel in the "destroy" function. 
> In release freebsd prior to 7.0 the destroy does not
"destroy"  de
> entries in /dev and silent ignores it... But in 7.0 it
waits for
> something (may be to free/unlock) all the resources.. 
> A rapid solution is to ignore the destroy call in
zaptel close
> routine...
>   
    destroy_dev_sched should do the trick. I've upgraded my
development 
system to 7.0-BETA3 and
is testing zaptel-bsd-ng branch right now.

-- 
gonzo

_______________________________________________
--Bandwidth and Colocation Provided by http://www.api-digital.c
om--

Asterisk-BSD mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-bsd