Jonathan Hunter
2007-Aug-28 22:42 UTC
[asterisk-users] Zaptel causes kernel crash - zt_init_tone_state
Hi, I've been avoiding investigating this issue for a while; I used to revert to a previously compiled version of zaptel & a previous kernel (as at some point I think I stopped being able to compile the older zaptel against the newer kernels) and all was well. However I've now upgraded kernels again and it seems silly to hide from the problem - here goes, let's try and fix it! At some point (and I'm afraid the exact point is lost in the mists of time) I upgraded zaptel as per normal, but that time the upgrade wasn't entirely successful and the new zaptel installation caused frequent crashes of my server. I think this was around the time of Zaptel 1.4.1 / 1.4.2, but I can't be entirely sure. A kernel call trace of when my system crashes, along with copies of various config files, is here: http://pastebin.ca/674091 but I have included highlights below. I'm a little bit stuck really, as I don't know where to start with debugging this. I'd really appreciate any clues or suggestions - I've configured my kernel for serial port console so that I can capture the call traces, and the problem is reproducible by simply picking up a Zap channel handset. Sometimes it takes longer to crash, sometimes it's quicker - and I'm getting some really strange "dialtones" varying from complete silence, through loud single tones, right up to weird multiple tones similar to a fax or modem. I'm running a stock FC6 system, and I don't believe it's a hardware issue as it has always worked fine under previous versions of zaptel. My hardware is a TDM400 with an (unused) X100P as well - see below for output when my machine boots up. Any suggestions gratefully received - where do I start?! Thanks, Jonathan -- "If we knew what it was we were doing, it would not be called research, would it?" - Albert Einstein Zaptel Echo Canceller: MG2 Freshmaker version: 71 Freshmaker passed register test Module 0: Installed -- AUTO FXS/DPO Module 1: Installed -- AUTO FXS/DPO Module 2: Installed -- AUTO FXS/DPO Module 3: Installed -- AUTO FXS/DPO Found a Wildcard TDM: Wildcard TDM400P REV E/F (4 modules) wcfxo: DAA mode is 'FCC' Found a Wildcard FXO: Wildcard X101P Zaptel Transcoder support loaded Call Trace: [<f89ae977>] __zt_transmit_chunk+0x38d/0x10ff [zaptel] [<f8822173>] uhci_scan_schedule+0x6c7/0x75f [uhci_hcd] [<f89b503f>] zt_transmit+0x3a1/0x48e [zaptel] [<f89b50b4>] zt_transmit+0x416/0x48e [zaptel] [<f89897d2>] wctdm_interrupt+0x91f/0x9b5 [wctdm] [<f895eb18>] wcfxo_interrupt+0x2ee/0x5e3 [wcfxo] [<c04541e6>] handle_IRQ_event+0x1a/0x3f [<c04553f5>] handle_fasteoi_irq+0x64/0x98 [<c0455391>] handle_fasteoi_irq+0x0/0x98 [<c04071f7>] do_IRQ+0xac/0xd1 [<c041ad1f>] smp_apic_timer_interrupt+0x74/0x80 [<c040592b>] common_interrupt+0x23/0x28 [<c0403281>] mwait_idle_with_hints+0x3b/0x3f [<c0403285>] mwait_idle+0x0/0xa [<c04033c9>] cpu_idle+0x96/0xb7 [<c0764a8e>] start_kernel+0x316/0x31e [<c0764227>] unknown_bootoption+0x0/0x202 ======================Code: 40 54 00 00 00 00 c7 40 58 00 00 00 00 eb 14 89 50 44 c7 40 50 00 00 00 00 89 48 54 8b 44 24 08 89 43 58 5b c3 c7 00 00 00 00 00 <8b> 4a 04 89 48 04 8b 4a 08 c7 40 0c 00 00 00 00 89 48 08 8b 4a EIP: [<f89ab285>] zt_init_tone_state+0x6/0x2c [zaptel] SS:ESP 0068:c07cbf10 Kernel panic - not syncing: Fatal exception in interrupt
Tzafrir Cohen
2007-Aug-28 23:04 UTC
[asterisk-users] Zaptel causes kernel crash - zt_init_tone_state
On Tue, Aug 28, 2007 at 11:42:09PM +0100, Jonathan Hunter wrote:> A kernel call trace of when my system crashes, along with copies of > various config files, is here: http://pastebin.ca/674091 but I have > included highlights below.What version of zaptel is that?> > I'm a little bit stuck really, as I don't know where to start with > debugging this. I'd really appreciate any clues or suggestions - I've > configured my kernel for serial port console so that I can capture the > call traces, and the problem is reproducible by simply picking up a > Zap channel handset. Sometimes it takes longer to crash, sometimes > it's quicker - and I'm getting some really strange "dialtones" varying > from complete silence, through loud single tones, right up to weird > multiple tones similar to a fax or modem. > > I'm running a stock FC6 system, and I don't believe it's a hardware > issue as it has always worked fine under previous versions of zaptel. > My hardware is a TDM400 with an (unused) X100P as well - see below for > output when my machine boots up.-- Tzafrir Cohen icq#16849755 jabber:tzafrir at jabber.org +972-50-7952406 mailto:tzafrir.cohen at xorcom.com http://www.xorcom.com iax:guest at local.xorcom.com/tzafrir