[Asterisk-Users] TE405P takes ~5mins to load.
Derrick Knight
derrick at freerangeminds.com
Tue Apr 5 12:26:48 MST 2005
Can you refresh my memory on the Linux rev (Slackware 2.4.26?) and
Zaptel driver version? I am currently running Slackware 10.0 (2.4.26)
with Asterisk 1.0.7 and zaptel 1.0.7. I am seeing boot times of well
under 1 minute.
Also, where exactly are you seeing the "delay" during the boot process.
You noted the point where you were at 5-15 minutes, but wasn't sure
where it started to get slow. Is it quickly getting to the zaptel driver
and then slowing down or is it slow prior to that? I would focus on
potential IRQ conflicts (cat /proc/interrupts) or the kernel probing for
non-existent devices.
Details on exactly where the slowing begins would be a start.
Derrick
Paul Belanger wrote:
>Derrick,
>
>Thanks for the ideas. I have since removed any USB/Firewire/un-needed
>hardware from loading in the MOBO BIOS and recompiled the kernel to boot.
>However I still seem to have the same problem.
>
>Here is some more information.
>
># lsmod
>Module Size Used by Not tainted
>wct4xxp 55040 0 (unused)
>zaptel 179008 0 [wct4xxp]
>
># dmesg
>...
>... SNIP
>...
>Zapata Telephony Interface Registered on major 196
>PCI: Found IRQ 10 for device 00:0f.0
>Found TE410P at base address db001000, remapped to d08d0000
>TE410P version c01a009b, burst ON
>FALC version: 00000005, Board ID: 00
>Reg 0: 0x0f706800
>Reg 1: 0x0f706000
>Reg 2: 0x07fc07fc
>Reg 3: 0x00000000
>Reg 4: 0x00000000
>Reg 5: 0x00000000
>Reg 6: 0xc01a009b
>Reg 7: 0x00001000
>Reg 8: 0x00000000
>Reg 9: 0x00ff0000
>Reg 10: 0x00000000
>TE410P: Launching card: 0
>TE410P: Setting up global serial parameters
>Found a Wildcard: Wildcard TE410P-Xilinx
>Registered tone zone 0 (United States / North America) <- this point only
>happens after 5 - 15 minutes after system has booted.
>TE410P: Span 1 configured for ESF/B8ZS
>SPAN 1: Primary Sync Source
>TE410P: Span 2 configured for ESF/B8ZS
>SPAN 2: Secondary Sync Source
>TE410P: Span 3 configured for ESF/B8ZS
>TE410P: Span 4 configured for ESF/B8ZS
>wct4xxp: Setting yellow alarm on span 1
>Zaptel: Master changed to TE4/0/2
>wct4xxp: Setting yellow alarm on span 2
>Zaptel: Master changed to TE4/0/3
>wct4xxp: Setting yellow alarm on span 3
>Zaptel: Master changed to TE4/0/4
>wct4xxp: Setting yellow alarm on span 4
>wct4xxp: Clearing yellow alarm on span 1
>wct4xxp: Clearing yellow alarm on span 2
>Zaptel: Master changed to TE4/0/1
>TE410P: Span 1 configured for ESF/B8ZS
>SPAN 1: Primary Sync Source
>TE410P: Span 2 configured for ESF/B8ZS
>SPAN 2: Secondary Sync Source
>TE410P: Span 3 configured for ESF/B8ZS
>TE410P: Span 4 configured for ESF/B8ZS
>Registered tone zone 0 (United States / North America)
>wct4xxp: Setting yellow alarm on span 1
>Zaptel: Master changed to TE4/0/2
>wct4xxp: Setting yellow alarm on span 2
>TE410P: Span 1 configured for ESF/B8ZS
>SPAN 1: Primary Sync Source
>TE410P: Span 2 configured for ESF/B8ZS
>SPAN 2: Secondary Sync Source
>TE410P: Span 3 configured for ESF/B8ZS
>TE410P: Span 4 configured for ESF/B8ZS
>Registered tone zone 0 (United States / North America)
>Zaptel: Master changed to TE4/0/1
>wct4xxp: Clearing yellow alarm on span 1
>wct4xxp: Clearing yellow alarm on span 2
>
># cat /var/log/messages
>...
>... SNIP
>...
>Apr 5 13:15:51 gateway kernel: Zapata Telephony Interface Registered on
>major 196
>Apr 5 13:15:51 gateway kernel: PCI: Found IRQ 10 for device 00:0f.0
>Apr 5 13:15:52 gateway logger: /etc/rc.d/rc.hotplug start (exiting script)
>Apr 5 13:15:53 gateway sshd[317]: Server listening on 0.0.0.0 port 22.
>Apr 5 13:19:32 gateway sshd[349]: Accepted password for pabelanger from
>192.168.2.1 port 4191 ssh2
>Apr 5 13:30:13 gateway kernel: Registered tone zone 0 (United States /
>North America)
>
>I would agree that something maybe auto-detecting on startup, but not sure
>what it could be.
>
>PB
>
>===
>
>
>>Are you viewing the output to the console as you are booting the system?
>>I suspect that it has nothing to do with the Digium drivers and more to
>>do with other features of Slackware such as attempting to autodetect USB
>>or 1394 devices. If you don't have any of them you can turn off the
>>probing in your kernel.
>>
>>Derrick
>>
>>
>
>_______________________________________________
>Asterisk-Users mailing list
>Asterisk-Users at lists.digium.com
>http://lists.digium.com/mailman/listinfo/asterisk-users
>To UNSUBSCRIBE or update options visit:
> http://lists.digium.com/mailman/listinfo/asterisk-users
>
>
>
>
>
--
Derrick Knight
derrick at freerangeminds.com
More information about the asterisk-users
mailing list