Summary:ASTERISK-11938: Non freed channel then kernel panic
Reporter:Cédric Chantepie (cchantep)Labels:
Date Opened:2008-04-29 08:04:54Date Closed:2011-06-07 14:00:48
Versions:Frequency of
Environment:Attachments:( 0) P1020796.JPG
Description:In some case, maybe related to RxFax reception/sending, a digital ISDN channel is not freed. Then when trying to unload mISDN (after having stopped asterisk) a kernel panic is fired.
Comments:By: Cédric Chantepie (cchantep) 2008-04-29 08:26:03

Channel list when channel is locked (before trying to unload mISDN)

Chan List: 0x824e488
* Pid:8 Prt:1 Ch:1 Mode:TE Org:* dad:0243829799 oad: rad: ctx:isdn state:CONNECTED
* Pid:9 Prt:1 Ch:2 Mode:TE Org:I dad:9799 oad:0243829797 rad: ctx:isdn state:CONNECTED

By: Cédric Chantepie (cchantep) 2008-04-29 10:48:40

I'm using a kernel 2.6.17 with digium BRI card b410p (te_ptmp/Euro ISDN)
+ zaptel 1.4.10

By: Russell Bryant (russell) 2008-04-29 11:15:45

We do not maintain the mISDN kernel drivers

By: Cédric Chantepie (cchantep) 2008-04-29 11:40:44

Even if mISDN drivers are involved, I think initial cause came from chan_misdn (not freed channel). I'm ok kernel panic is caused by driver unloaded, but I'm not convinced channel management bug is due to driver.

By: crich (crich) 2008-09-17 02:53:45

cchantep: you need to enable chan_misdn debugging in the misdn.conf (level 5) and to trace the situation. then attach /var/log/asterisk/misdn.log if it happens again.

By: Tilghman Lesher (tilghman) 2009-01-13 15:28:43.000-0600

No response from reporter.