I've got a voicemail server I made from four X100P cards (off eBay), Fedora Core 4, connected to a Toshiba DK40 system. I'm using Asterisk 1.0.9, and Zaptel 1.0.9.2. It works great, except the card which receives a majority of the activity occationally will go into a 'Red' alarm and then Asterisk won't answer calls on any of the cards, eventhough the other cards are not in an alarm state. If I reboot the server, all it well again. I've switched around the ports in case of a hardware issue, but the same thing happened on a different card (again, it was handling a majority of the calls). I don't see anything in the logs, but I may not know what to look for. Is this a known issue? Thanks! Phil
Are you running off the rpms or compiled version?
> I've got a voicemail server I made from four X100P cards (off eBay), > Fedora Core 4, connected to a Toshiba DK40 system. I'm using > Asterisk 1.0.9, and Zaptel 1.0.9.2. > > It works great, except the card which receives a majority of the > activity occationally will go into a 'Red' alarm and then Asterisk > won't answer calls on any of the cards, eventhough the other cards > are not in an alarm state. If I reboot the server, all it well > again. I've switched around the ports in case of a hardware issue, > but the same thing happened on a different card (again, it was > handling a majority of the calls). > > I don't see anything in the logs, but I may not know what to look for. > > Is this a known issue?About a year and a half ago when I was running a couple of x100p's there was an issue associated with disconnecting the pstn line from the card. If I recall correctly, if the pstn line was removed for more then a second or so (a couple of times), the card would go into some unknown state and it had to be restarted. The comments/fix at the time were oriented around "don't do that" instead of fixing the code to recognizing it. I don't have a clue whether that is still an issue with the x100p code or not. You might try using a regular old voltmeter on the tip/ring of the line going to the Toshiba and watch what happens at the end of a VM call. It is possible the Toshiba is opening/disconnecting the line for some rather lengthy period (disconnect supervision).
Tzafrir Cohen wrote:>[...]wcfxo is the driver for the X100P cards. >FYI-I just had another crash. This time I got an oops dump: ------------[ cut here ]------------ kernel BUG at mm/rmap.c:493! invalid operand: 0000 [#1] Modules linked in: loop wcfxo(U) zaptel(U) crc_ccitt ipv6 parport_pc lp parport autofs4 it87 eeprom i2c_sensor i2c_isa sunrpc video button battery ac ohci_hcd i2c_sis630 i2c_core snd_trident gameport snd_ac97_codec snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd_page_alloc snd_util_mem snd_mpu401_uart snd_rawmidi snd_seq_device snd soundcore 8139too mii dm_snapshot dm_zero dm_mirror ext3 jbd dm_mod CPU: 0 EIP: 0060:[<c018dc74>] Not tainted VLI EFLAGS: 00010286 (2.6.13-1.1532_FC4) EIP is at page_remove_rmap+0x36/0x40 eax: ffffffff ebx: c6800924 ecx: c04eaa78 edx: c13aa240 esi: c13aa240 edi: 00000020 ebp: 00249000 esp: ce0d4e60 ds: 007b es: 007b ss: 0068 Process gawk (pid: 8941, threadinfo=ce0d4000 task=d994e000) Stack: c01814c4 00000000 0025e000 c04eaa78 d635d000 0025e000 0025e000 0025dfff c018165a 0025e000 00000000 c04eaa78 0001a000 0025e000 d8c51754 00400000 c018182f 0025e000 00000000 d13d8f8c c10d0260 06813067 b7fe3000 c01814d6 Call Trace: [<c01814c4>] zap_pte_range+0xd6/0x1e9 [<c018165a>] unmap_page_range+0x83/0xb7 [<c018182f>] unmap_vmas+0x1a1/0x45d [<c01814d6>] zap_pte_range+0xe8/0x1e9 [<c018a32b>] exit_mmap+0x12e/0x36d [<c0179b2e>] __pagevec_lru_add_active+0x31e/0x47c [<c01241c5>] mmput+0x25/0x317 [<c012d5b4>] do_exit+0xe0/0x942 [<c0164c71>] audit_syscall_entry+0x130/0x15e [<c012df6d>] do_group_exit+0x12b/0x349 [<c0109b52>] do_syscall_trace+0xef/0x123 [<c0104465>] syscall_call+0x7/0xb Code: 08 ff 0f 98 c0 84 c0 75 01 c3 8b 42 08 83 c0 01 78 19 ba ff ff ff ff b8 10 00 00 00 e9 5e 30 fe ff 0f 0b ea 01 9e 74 41 c0 eb d3 <0f> 0b ed 01 9e 74 41 c0 eb dd 55 57 56 53 83 ec 24 89 c7 89 d3 <3>Debug: sleeping function called from invalid context at include/linux/rwsem.h:43 in_atomic():1, irqs_disabled():0 [<c012a4e3>] profile_task_exit+0x13/0x48 [<c012d4ef>] do_exit+0x1b/0x942 [<c0104622>] common_interrupt+0x1a/0x20 [<c01051fa>] die+0x2e5/0x3bd [<c011edd3>] fixup_exception+0xb/0x28 [<c0105516>] do_invalid_op+0x0/0xab [<c01055b8>] do_invalid_op+0xa2/0xab [<c018dc74>] page_remove_rmap+0x36/0x40 [<c016c4cf>] generic_file_buffered_write+0x37d/0x616 [<c0170778>] __alloc_pages+0xe7/0x3ff [<c0131f9d>] current_fs_time+0x4e/0x69 [<c010467f>] error_code+0x4f/0x54 [<c018dc74>] page_remove_rmap+0x36/0x40 [<c01814c4>] zap_pte_range+0xd6/0x1e9 [<c018165a>] unmap_page_range+0x83/0xb7 [<c018182f>] unmap_vmas+0x1a1/0x45d [<c01814d6>] zap_pte_range+0xe8/0x1e9 [<c01055b8>] do_invalid_op+0xa2/0xab [<c018dc74>] page_remove_rmap+0x36/0x40 [<c016c4cf>] generic_file_buffered_write+0x37d/0x616 [<c0170778>] __alloc_pages+0xe7/0x3ff [<c0131f9d>] current_fs_time+0x4e/0x69 [<c010467f>] error_code+0x4f/0x54 [<c018dc74>] page_remove_rmap+0x36/0x40 [<c01814c4>] zap_pte_range+0xd6/0x1e9 [<c018165a>] unmap_page_range+0x83/0xb7 [<c018182f>] unmap_vmas+0x1a1/0x45d [<c01814d6>] zap_pte_range+0xe8/0x1e9 [<c018a32b>] exit_mmap+0x12e/0x36d [<c0179b2e>] __pagevec_lru_add_active+0x31e/0x47c [<c01241c5>] mmput+0x25/0x317 [<c012d5b4>] do_exit+0xe0/0x942 [<c0164c71>] audit_syscall_entry+0x130/0x15e [<c012df6d>] do_group_exit+0x12b/0x349 [<c0109b52>] do_syscall_trace+0xef/0x123 [<c0104465>] syscall_call+0x7/0xb Fixing recursive fault but reboot is needed! scheduling while atomic: gawk/0x00000001/8941 [<c03ff83e>] schedule+0x6ee/0x938 [<c0104465>] syscall_call+0x7/0xb [<c014b526>] __kernel_text_address+0x1c/0x27 [<c0104b79>] show_trace+0x2a/0x78 [<c0104465>] syscall_call+0x7/0xb [<c012dbcb>] do_exit+0x6f7/0x942 [<c01051fa>] die+0x2e5/0x3bd [<c011edd3>] fixup_exception+0xb/0x28 [<c0105516>] do_invalid_op+0x0/0xab [<c01055b8>] do_invalid_op+0xa2/0xab [<c018dc74>] page_remove_rmap+0x36/0x40 [<c016c4cf>] generic_file_buffered_write+0x37d/0x616 [<c0170778>] __alloc_pages+0xe7/0x3ff [<c0131f9d>] current_fs_time+0x4e/0x69 [<c010467f>] error_code+0x4f/0x54 [<c018dc74>] page_remove_rmap+0x36/0x40 [<c01814c4>] zap_pte_range+0xd6/0x1e9 [<c018165a>] unmap_page_range+0x83/0xb7 [<c018182f>] unmap_vmas+0x1a1/0x45d [<c01814d6>] zap_pte_range+0xe8/0x1e9 [<c018a32b>] exit_mmap+0x12e/0x36d [<c0179b2e>] __pagevec_lru_add_active+0x31e/0x47c [<c01241c5>] mmput+0x25/0x317 [<c012d5b4>] do_exit+0xe0/0x942 [<c0164c71>] audit_syscall_entry+0x130/0x15e [<c012df6d>] do_group_exit+0x12b/0x349 [<c0109b52>] do_syscall_trace+0xef/0x123 [<c0104465>] syscall_call+0x7/0xb