karl156 wrote: >> I suspect this is the making of mISDN. Is this reproducable when mISDN >> is blacklisted?
main suspect is zaphfc! > It also happens when mISDN_core and hfcpci are blacklisted and the dadhi > drivers are started during system startup. The kernel warning then > occurs 4 - 5 seconds after system start. I only blacklisted hfcpci, thus mISDN doesn't get loaded. > I could solve the TEI problem with a newer upstream version of vzaphfc. > There is a version specially for dahdi 2.3.0. (A version for 2.4.0 is > also available). Nice! I can also confirm that the TEI problem can be solved by patching dahdi-source 2.3.0.1+dfsg-1 zaphfc/base.c with upstream's r8=r9 branch 2.3 (http://zaphfc.googlecode.com/svn). > But the kernel warning problem remains. Maybe dahdi 2.4.0 can solve that > problem? In my case, it is even better than karl's report, as it also got rid of the warn_slowpath_common. This has been tested on 2 different machines (w/ and w/o shared irq), although with the same HFC card. I'm using stock squeeze kernel package (linux-image-2.6.32-5-686 2.6.32-23). I can make & receive calls over the dahdi channels, so everything looks good to me. I can even see the callerid being received properly in the logs (although my dialplan needs more tweaking to handle the callerid changes occurred since asterisk 1.2, but you don't care). I didn't try dahdi 2.4 or any other kernel version. I just want a standard system I can forget and update without thinking too much... Smallish changes: $ diff /usr/src/modules/dahdi/drivers/dahdi/zaphfc/base.c /usr/src/zaphfc-googlecode/branches/2.3/zaphfc/base.c 34a35 > #if (LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 32)) 35a37 > #endif 659a662 > hfccard->span.owner = THIS_MODULE; 701c704 < hfccard->sigchan = &hfccard->chans[D]; --- > hfccard->sigchan = &hfccard->chans[DAHDI_D]; -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
