Re: 9.2 panic with wcb4xxp (dahdi-kmod26-2.6.1.r10738)
Harald Schmalzbauer <[email protected]> Mon, 23 Sep 2013 17:00:39 +0200
| Newsgroups | gmane.os.freebsd.devel.isdn,gmane.os.freebsd.stable |
|---|---|
| Organization | OmniLAN |
| Message-ID | <[email protected]> |
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigF001B03F6AB0ED02DC1351D8 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Bez=FCglich Amitabh Kant's Nachricht vom 21.09.2013 03:24 (localtime): > On Thu, Sep 19, 2013 at 7:35 PM, Harald Schmalzbauer > <[email protected] <mailto:[email protected]>> wrote: > > Hello, > > unloading the kernel module of dahdi-kmod26-2.6.1.r10738 leads to t= his > panic: > > > <snip> > > wcb4xxp0: <6>Did not do the highestorder stuff > <6>dahdi: Detected time shift. > <5>dahdi_echocan_mg2: Registered echo canceler 'MG2' > > Starting asterisk afterwards also leads to panic. > I guess dahdi development stalled, but I wanted to try it because I= 'd > prefer freeswitch and need BRI support... > Is somebody familiar with dahdi and interested in making it work wi= th > FreeBSD 9.2? > > Thanks, > > -Harry (not subscribed to isdn@) > > > > Have you been able to solve the problem? I am running Freeswitch (from > git, not port) and dahdi/dahdi-kmod26 (from port) with PRI line > (Digium 8 span and single span) without any problems on 9.1. Will test > it on 9.2 and get back to you if I see a panic . Hello Amitabh, couldn't solve my problem. First, dahdi_scan doesn't detect ports jumpered to NT mode. I need 2 port= s in NT mode, so trying anything else with dahdi before my settings get c= orrectly recognized is probably not worth the time. Also I have to investigate if it is still true that libpri doesn't suppor= t ptmp in NT mode!?! In general, the freebsd dahdi port doesn't seem to be in good shape; Coul= dn't find any docs about sysctls (dahdi.wcb4xxp.teignorered, '-d' shows n= othing :-( ), no man page =96 hard to find out anything about dahdi in Fr= eeBSD, not even the supported hardwhere seems to be documentend anywhere.= =2E. Any hints highly appreciated, although I think the better way was to teac= h FreeTDM speaking CAPI. HPS does a great job keeping all kind of ISDN ha= rdware supported by i4b (ISDN4BSD)! Or to make chan_capi work with asterisk11 =96 the lesser evil than fighti= ng dahid... Thanks, -Harry --------------enigF001B03F6AB0ED02DC1351D8 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iEYEARECAAYFAlJAV5cACgkQLDqVQ9VXb8gsiACeMGNFGvcvxrdGwAYozpzZ2YKS SbAAoMkPiPFp03l1xibo+Z6XuwFQ5G7T =DyeN -----END PGP SIGNATURE----- --------------enigF001B03F6AB0ED02DC1351D8--