Summary: | ASTERISK-09510: Kernel crashes when loading Zaptel with TE410P with HW echocan | ||
Reporter: | Juan Carlos Castro y Castro (jccyc) | Labels: | |
Date Opened: | 2007-05-24 16:37:17 | Date Closed: | 2007-05-29 10:39:11 |
Priority: | Critical | Regression? | No |
Status: | Closed/Complete | Components: | Core/General |
Versions: | Frequency of Occurrence | ||
Related Issues: | |||
Environment: | Attachments: | ||
Description: | I compile Zaptel 1.4.2.1, install it, and when I start it, I get a kernel crash. Upon restarting the machine, I get another crash when it's in the "loading udev" phase. I have to boot from the CD and erase /etc/zaptel.conf then it can boot again. When I start the service from the console, the last "good" message from the driver is: "VPM: Echo cancellation for 128 channels" -- then kaboom, kernel panic messages whiz by, too fast for me to read. (As I type this, I'm downloading the necessary files to follow the tutorial at http://fedoraproject.org/wiki/FC6KdumpKexecHowTo so I can give you guys better info) When there's no /etc/zaptel.conf (or if it only contains loadzone = us and defaultzone=us), all four spans show correctly as "unconfigured" on zttool and nothing bad ever happens. Oh, and the card is jumpered to E1 since I'm in Brazil. Here's my specs and the (I think) relevant files and outputs. Please CC me if you reply. Thanks in advance. Dell PowerEdge 1950, Fedora Core 6, kernel 2.6.20-1.2948.fc6, 1 GB RAM, stock Zaptel 1.4.2.1 compiled with no changes to zconfig.h. The same thing happens with the latest zaptel 1.2. ****** ADDITIONAL INFORMATION ****** /etc/zaptel.conf (if I have this, kaboom) ---------------------------------------------------------------------- span=1,1,0,ccs,hdb3 span=2,2,0,ccs,hdb3 span=3,3,0,ccs,hdb3 span=4,4,0,ccs,hdb3 #span=4,4,0,ccs,hdb3,crc4 bchan=1-15 dchan=16 bchan=17-31 bchan=32-46 dchan=47 bchan=48-62 bchan=63-77 dchan=78 bchan=79-93 bchan=94-108 dchan=109 bchan=110-124 loadzone = us defaultzone=us ---------------------------------------------------------------------- /proc/cpuinfo: ---------------------------------------------------------------------- processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Xeon(R) CPU 5110 @ 1.60GHz stepping : 6 cpu MHz : 1596.097 cache size : 4096 KB physical id : 0 siblings : 2 core id : 0 cpu cores : 2 fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc pni monitor ds_cpl vmx tm2 ssse3 cx16 xtpr dca lahf_lm bogomips : 3194.20 clflush size : 64 processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Xeon(R) CPU 5110 @ 1.60GHz stepping : 6 cpu MHz : 1596.097 cache size : 4096 KB physical id : 0 siblings : 2 core id : 1 cpu cores : 2 fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc pni monitor ds_cpl vmx tm2 ssse3 cx16 xtpr dca lahf_lm bogomips : 3192.08 clflush size : 64 processor : 2 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Xeon(R) CPU 5110 @ 1.60GHz stepping : 6 cpu MHz : 1596.097 cache size : 4096 KB physical id : 3 siblings : 2 core id : 0 cpu cores : 2 fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc pni monitor ds_cpl vmx tm2 ssse3 cx16 xtpr dca lahf_lm bogomips : 3192.12 clflush size : 64 processor : 3 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Xeon(R) CPU 5110 @ 1.60GHz stepping : 6 cpu MHz : 1596.097 cache size : 4096 KB physical id : 3 siblings : 2 core id : 1 cpu cores : 2 fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc pni monitor ds_cpl vmx tm2 ssse3 cx16 xtpr dca lahf_lm bogomips : 3192.15 clflush size : 64 ---------------------------------------------------------------------- lspci: ---------------------------------------------------------------------- 00:00.0 Host bridge: Intel Corporation 5000X Chipset Memory Controller Hub (rev 12) 00:02.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 2 (rev 12) 00:03.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 3 (rev 12) 00:04.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 4 (rev 12) 00:05.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 5 (rev 12) 00:06.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x8 Port 6-7 (rev 12) 00:07.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 7 (rev 12) 00:10.0 Host bridge: Intel Corporation 5000 Series Chipset Error Reporting Registers (rev 12) 00:10.1 Host bridge: Intel Corporation 5000 Series Chipset Error Reporting Registers (rev 12) 00:10.2 Host bridge: Intel Corporation 5000 Series Chipset Error Reporting Registers (rev 12) 00:11.0 Host bridge: Intel Corporation 5000 Series Chipset Reserved Registers (rev 12) 00:13.0 Host bridge: Intel Corporation 5000 Series Chipset Reserved Registers (rev 12) 00:15.0 Host bridge: Intel Corporation 5000 Series Chipset FBD Registers (rev 12) 00:16.0 Host bridge: Intel Corporation 5000 Series Chipset FBD Registers (rev 12) 00:1c.0 PCI bridge: Intel Corporation 631xESB/632xESB/3100 Chipset PCI Express Root Port 1 (rev 09) 00:1d.0 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #1 (rev 09) 00:1d.1 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #2 (rev 09) 00:1d.2 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #3 (rev 09) 00:1d.7 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset EHCI USB2 Controller (rev 09) 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev d9) 00:1f.0 ISA bridge: Intel Corporation 631xESB/632xESB/3100 Chipset LPC Interface Controller (rev 09) 00:1f.1 IDE interface: Intel Corporation 631xESB/632xESB IDE Controller (rev 09) 01:00.0 PCI bridge: Intel Corporation 6702PXH PCI Express-to-PCI Bridge A (rev 09) 02:08.0 SCSI storage controller: LSI Logic / Symbios Logic SAS1068 PCI-X Fusion-MPT SAS (rev 01) 03:00.0 PCI bridge: Broadcom EPB PCI-Express to PCI-X Bridge (rev c3) 04:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet (rev 12) 05:00.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Upstream Port (rev 01) 05:00.3 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express to PCI-X Bridge (rev 01) 06:00.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E1 (rev 01) 06:01.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E2 (rev 01) 07:00.0 PCI bridge: Broadcom EPB PCI-Express to PCI-X Bridge (rev c3) 08:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet (rev 12) 0a:01.0 Communication controller: Digium, Inc. Wildcard TE410P Quad-Span togglable E1/T1/J1 card 3.3v (rev 02) 0b:00.0 PCI bridge: Intel Corporation 6702PXH PCI Express-to-PCI Bridge A (rev 09) 10:0d.0 VGA compatible controller: ATI Technologies Inc ES1000 (rev 02) ---------------------------------------------------------------------- | ||
Comments: | By: Juan Carlos Castro y Castro (jccyc) 2007-05-24 23:24:54 Dell's BIOS setup sucks. The Digium card is forced to share the same interrupt with the hard disk controller AND BOTH NICs! Can this have anything to do with the problem? And: happens also in Zaptel 1.4 SVN 2549. By: Juan Carlos Castro y Castro (jccyc) 2007-05-24 23:26:21 Oh, and I couldn't get kexec to work so no kernel backtrace. (It complains that it can't determine the file type of Fedora's kdump kernel) By: Matthew Fredrickson (mattf) 2007-05-24 23:43:29 Somehow you need to find out how to give a backtrace, or I can't do anything with this. By: Matthew Fredrickson (mattf) 2007-05-24 23:44:21 Does it have the problem with 1.2 also? By: Juan Carlos Castro y Castro (jccyc) 2007-05-25 08:07:45 Yes it does, with the latest 1.2 release. By: Juan Carlos Castro y Castro (jccyc) 2007-05-25 08:23:53 Let me do this: I'll compile the kernel from sources, ditto for the kexec tools, and try again. By: Juan Carlos Castro y Castro (jccyc) 2007-05-25 15:24:30 I still can't get at /proc/vmcore -- it doesn't go to a prompt after the panic. I'm doing something wrong. Anyway, I was able to copy this from the screen. Is it of any help? Process ztcfg (pid: 3507, ti=ede24000 task=f70787f0 task.ti=ede25000) Stack: c0427aa0 c06d78e4 ede24e70 ede24e70 0000000f 00000000 0000000b ede24ef0 00000000 c06af419 00000046 c0405530 c06a64dc 00004067 fffe4ef9 f70787f0 00000000 c0427aa0 c06af408 ede24eb4 ede24eb4 00004067 fffe4ef9 f70787f0 Call Trace: [<c0427aa0>] printk+0x1f/0x95 [<c0405530>] die+0x21b/0x240 [<c0427aa0>] printk+0x1f/0x95 [<c0621ee3>] do_page_fault+0x407/0x4da [<c0621adc>] do_page_fault+0x0/0x4da [<c0620744>] error_code+0x7c/0x84 [<c04f4fb2>] dump_trace+0x5c/0x93 [<c0405001>] show_trace_log_lvl+0x18/0x2c [<c04050b0>] show_stack_log_lvl+0x9b/0xa3 [<c0405246>] show_registers+0x18e/0x25d [<c0621fcf>] notifier_call_chain+0x19/0x29 [<c0405443>] die+0x12e/0x240 [<c0621ee3>] do_page_fault+0x407/0x4da ======================= Code: 00 89 f8 e8 02 6b 09 00 85 ed 74 19 8b 87 4c 04 00 00 83 b8 94 00 00 00 00 74 0a b8 01 00 00 00 e8 58 da 10 00 8b 47 04 8b 40 04 <8b> 40 24 e8 fc 51 01 00 8b 87 8c 00 00 00 85 c0 74 08 8b 40 04 EIP: [<c0429b38>] do_exit+0x2ed/0x6f6 SS:ESP 0068:ede24e48 <1>Fixing recursive fault but reboot is needed! By: Juan Carlos Castro y Castro (jccyc) 2007-05-25 15:26:50 Tell me if something more could help combined with the trace above (like the kernel binary, the zaptel module binaries, the ztcfg binary, etc) By: Juan Carlos Castro y Castro (jccyc) 2007-05-25 15:27:58 Another thing: If I unplug the echo canceling daughtercard, all problems disappear. By: Joshua C. Colp (jcolp) 2007-05-29 10:39:10 Please contact Digium Technical Support at support@digium.com - you may have a non-working echo cancellation module that may need to be replaced. Thanks! |