Re: [Asterisk-Users] TDM04B lock up
I have a strange situation. Once in a while (non-deterministic) the 2 TDM04B cards lock up at the same time and stop processing incoming and outgoing calls even though * shows that it is trying to communicate to ZAP channels (at least on the outgoing). The only cure is to reboot the system when it happens. It makes me very apprehensive of the system Has anyone seen this problem. Could this be something to do with the IRQ sharing. Here is the output of lspci -v. I see that one of the cards shares IRQ # with VGA controller and the other one with ICH4 IDE. Any help would be appreciated. The TDM04b card is known to do that and its been reported to digium by several users. Seems to lock up about once every week or two, and varies from one system to another. The digium folks aren't saying anything as yet about what needs to be fixed. But, best open a trouble ticket with them for the records. There is a very high probability it is a hardware design issue. I've added a capacitor to my card under the assumption that noisy on-card logic is distrubing the chipsets. So far I'm not had a lockup, but it's a little to early to say that actually fixed it. irq sharing has been known to be an issue in some cases, however its generally over-blown on this list. If you want to eliminate that as an issue, either move you cards around to different slots or take a look in your bios config to disable those irq's on in use (or both). I'd guess the probability of an irq issue causing your problems is in the neighborhood of about a 20% chance. ___ Asterisk-Users mailing list Asterisk-Users@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
[Asterisk-Users] TDM04B lock up
Hi I have a strange situation. Once in a while (non-deterministic) the 2 TDM04B cards lock up at the same time and stop processing incoming and outgoing calls even though * shows that it is trying to communicate to ZAP channels (at least on the outgoing). The only cure is to reboot the system when it happens. It makes me very apprehensive of the system Has anyone seen this problem. Could this be something to do with the IRQ sharing. Here is the output of lspci -v. I see that one of the cards shares IRQ # with VGA controller and the other one with ICH4 IDE. Any help would be appreciated. 00:00.0 Host bridge: Intel Corp. 82845G/GL [Brookdale-G] Chipset Host Bridge (rev 01) Subsystem: Dell Computer Corporation: Unknown device 0160 Flags: bus master, fast devsel, latency 0 Memory at f000 (32-bit, prefetchable) [size=128M] Capabilities: [e4] #09 [1105] 00:02.0 VGA compatible controller: Intel Corp. 82845G/GL [Brookdale-G] Chipset Integrated Graphics Device (rev 01) (prog-if 00 [VGA]) Subsystem: Dell Computer Corporation: Unknown device 0160 Flags: fast devsel, IRQ 11 Memory at e800 (32-bit, prefetchable) [size=128M] Memory at feb8 (32-bit, non-prefetchable) [size=512K] Capabilities: [d0] Power Management version 1 00:1e.0 PCI bridge: Intel Corp. 82801BA/CA/DB PCI Bridge (rev 81) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=01, subordinate=01, sec-latency=32 I/O behind bridge: d000-dfff Memory behind bridge: fe90-feaf 00:1f.0 ISA bridge: Intel Corp. 82801DB ISA Bridge (LPC) (rev 01) Flags: bus master, medium devsel, latency 0 00:1f.1 IDE interface: Intel Corp. 82801DB ICH4 IDE (rev 01) (prog-if 8a [Master SecP PriP]) Subsystem: Dell Computer Corporation: Unknown device 0160 Flags: bus master, medium devsel, latency 0, IRQ 9 I/O ports at ignored I/O ports at ignored I/O ports at ignored I/O ports at ignored I/O ports at ffa0 [size=16] Memory at feb7fc00 (32-bit, non-prefetchable) [size=1K] 00:1f.3 SMBus: Intel Corp. 82801DB SMBus (rev 01) Subsystem: Dell Computer Corporation: Unknown device 0160 Flags: medium devsel, IRQ 3 I/O ports at efe0 [size=32] 01:04.0 Communication controller: Tiger Jet Network Inc. Intel 537 Subsystem: Unknown device b100:0003 Flags: bus master, medium devsel, latency 64, IRQ 11 I/O ports at dc00 [size=256] Memory at fe9fc000 (32-bit, non-prefetchable) [size=4K] Capabilities: [40] Power Management version 2 01:05.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) Subsystem: Realtek Semiconductor Co., Ltd. RT8139 Flags: bus master, medium devsel, latency 64, IRQ 3 I/O ports at dd00 [size=256] Memory at fe9fbf00 (32-bit, non-prefetchable) [size=256] Capabilities: [50] Power Management version 2 01:06.0 Communication controller: Tiger Jet Network Inc. Intel 537 Subsystem: Unknown device b100:0003 Flags: bus master, medium devsel, latency 64, IRQ 9 I/O ports at de00 [size=256] Memory at fe9fd000 (32-bit, non-prefetchable) [size=4K] Capabilities: [40] Power Management version 2 Regards Goutam Shaw ___ Asterisk-Users mailing list Asterisk-Users@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
Re: [Asterisk-Users] TDM04B lock up
I had an issue with the same setup except only channel 1 on each card would work for incoming. All would work for outgoing, but asterisk never saw the other channels ringing. Restarting asterisk didn't help either. I panicked and just rebooted and the problem went away. I wish I had taken the time to have tried unloading and reloading the drivers. The system had been up for 22 days when this happened so I now just restart every sunday morning to be safe. On Fri, 2005-03-11 at 09:36, Goutam Shaw wrote: Hi I have a strange situation. Once in a while (non-deterministic) the 2 TDM04B cards lock up at the same time and stop processing incoming and outgoing calls even though * shows that it is trying to communicate to ZAP channels (at least on the outgoing). The only cure is to reboot the system when it happens. It makes me very apprehensive of the system Has anyone seen this problem. Could this be something to do with the IRQ sharing. Here is the output of lspci -v. I see that one of the cards shares IRQ # with VGA controller and the other one with ICH4 IDE. Any help would be appreciated. 00:00.0 Host bridge: Intel Corp. 82845G/GL [Brookdale-G] Chipset Host Bridge (rev 01) Subsystem: Dell Computer Corporation: Unknown device 0160 Flags: bus master, fast devsel, latency 0 Memory at f000 (32-bit, prefetchable) [size=128M] Capabilities: [e4] #09 [1105] 00:02.0 VGA compatible controller: Intel Corp. 82845G/GL [Brookdale-G] Chipset Integrated Graphics Device (rev 01) (prog-if 00 [VGA]) Subsystem: Dell Computer Corporation: Unknown device 0160 Flags: fast devsel, IRQ 11 Memory at e800 (32-bit, prefetchable) [size=128M] Memory at feb8 (32-bit, non-prefetchable) [size=512K] Capabilities: [d0] Power Management version 1 00:1e.0 PCI bridge: Intel Corp. 82801BA/CA/DB PCI Bridge (rev 81) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=01, subordinate=01, sec-latency=32 I/O behind bridge: d000-dfff Memory behind bridge: fe90-feaf 00:1f.0 ISA bridge: Intel Corp. 82801DB ISA Bridge (LPC) (rev 01) Flags: bus master, medium devsel, latency 0 00:1f.1 IDE interface: Intel Corp. 82801DB ICH4 IDE (rev 01) (prog-if 8a [Master SecP PriP]) Subsystem: Dell Computer Corporation: Unknown device 0160 Flags: bus master, medium devsel, latency 0, IRQ 9 I/O ports at ignored I/O ports at ignored I/O ports at ignored I/O ports at ignored I/O ports at ffa0 [size=16] Memory at feb7fc00 (32-bit, non-prefetchable) [size=1K] 00:1f.3 SMBus: Intel Corp. 82801DB SMBus (rev 01) Subsystem: Dell Computer Corporation: Unknown device 0160 Flags: medium devsel, IRQ 3 I/O ports at efe0 [size=32] 01:04.0 Communication controller: Tiger Jet Network Inc. Intel 537 Subsystem: Unknown device b100:0003 Flags: bus master, medium devsel, latency 64, IRQ 11 I/O ports at dc00 [size=256] Memory at fe9fc000 (32-bit, non-prefetchable) [size=4K] Capabilities: [40] Power Management version 2 01:05.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) Subsystem: Realtek Semiconductor Co., Ltd. RT8139 Flags: bus master, medium devsel, latency 64, IRQ 3 I/O ports at dd00 [size=256] Memory at fe9fbf00 (32-bit, non-prefetchable) [size=256] Capabilities: [50] Power Management version 2 01:06.0 Communication controller: Tiger Jet Network Inc. Intel 537 Subsystem: Unknown device b100:0003 Flags: bus master, medium devsel, latency 64, IRQ 9 I/O ports at de00 [size=256] Memory at fe9fd000 (32-bit, non-prefetchable) [size=4K] Capabilities: [40] Power Management version 2 Regards Goutam Shaw ___ Asterisk-Users mailing list Asterisk-Users@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 ___ Asterisk-Users mailing list Asterisk-Users@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
Re: [Asterisk-Users] TDM04B lock up
Goutam Shaw wrote: Hi I have a strange situation. Once in a while (non-deterministic) the 2 TDM04B cards lock up at the same time and stop processing incoming and outgoing calls even though * shows that it is trying to communicate to ZAP channels (at least on the outgoing). The only cure is to reboot the system when it happens. It makes me very apprehensive of the system Has anyone seen this problem. Could this be something to do with the IRQ sharing. Here is the output of lspci -v. Get the cards on their own interrupts - use the BIOS, turn off unneeded onboard devices etc. If you still have problems and the FXO modules are marked Rev C on the non pin side, talk to Digium support. I had ongoing problems with FXO modules stopping responding and requiring reboots to restore. Regdumps of the offending module show ff loaded in almost all registers. After contacting Digium, I was told this was a hardware issue and after having them replaced with modules marked X100B RevB, I have so far had no problems. Regards, Richard ___ Asterisk-Users mailing list Asterisk-Users@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
Re: [Asterisk-Users] TDM04B lock up
Should ACPI be turned off in the kernel? In the bios I can only set cards to the 1-15 interrupt range, but linux and acpi it seems moves these to the 20's. I looked last night on the lists and found no true answer to this question. I have 4 TDM's so interrupts below 15 are few and far between, but I do have enough. On Fri, 2005-03-11 at 13:50, Richard Scobie wrote: Goutam Shaw wrote: Hi I have a strange situation. Once in a while (non-deterministic) the 2 TDM04B cards lock up at the same time and stop processing incoming and outgoing calls even though * shows that it is trying to communicate to ZAP channels (at least on the outgoing). The only cure is to reboot the system when it happens. It makes me very apprehensive of the system Has anyone seen this problem. Could this be something to do with the IRQ sharing. Here is the output of lspci -v. Get the cards on their own interrupts - use the BIOS, turn off unneeded onboard devices etc. If you still have problems and the FXO modules are marked Rev C on the non pin side, talk to Digium support. I had ongoing problems with FXO modules stopping responding and requiring reboots to restore. Regdumps of the offending module show ff loaded in almost all registers. After contacting Digium, I was told this was a hardware issue and after having them replaced with modules marked X100B RevB, I have so far had no problems. Regards, Richard ___ Asterisk-Users mailing list Asterisk-Users@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 ___ Asterisk-Users mailing list Asterisk-Users@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
RE: [Asterisk-Users] TDM04B lock up
As far as I can tell, the main kernel configuration issue is to make sure APIC and IO-APIC support is turned on, if your system supports it. (All SMP motherboards do, and many single-processor ones do as well.) This seems to give access to 32 interrupts instead of 16, minimizing interrupt sharing. -Original Message-From: Dennis Webb [mailto:[EMAIL PROTECTED]Sent: Friday, March 11, 2005 2:51 PMTo: Asterisk Users Mailing List - Non-Commercial DiscussionSubject: Re: [Asterisk-Users] TDM04B lock up Should ACPI be turned off in the kernel? In the bios I can only set cards to the 1-15 interrupt range, but linux and acpi it seems moves these to the 20's. I looked last night on the lists and found no true answer to this question. I have 4 TDM's so interrupts below 15 are few and far between, but I do have enough. ___ Asterisk-Users mailing list Asterisk-Users@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
Re: [Asterisk-Users] TDM04B lock up
David Brodbeck wrote: As far as I can tell, the main kernel configuration issue is to make sure APIC and IO-APIC support is turned on, if your system supports it. (All SMP motherboards do, and many single-processor ones do as well.) This seems to give access to 32 interrupts instead of 16, minimizing interrupt sharing. http://lists.digium.com/pipermail/asterisk-users/2004-December/076983.html -- Kristian Kielhofner ___ Asterisk-Users mailing list Asterisk-Users@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
