Yo Mark, On Tue, Jun 17, 2003 at 06:58:28 -0500, Mark Spencer wrote:
> > As far as SMP and single T400P - we'll try and report the results > > but the idea was to go with as high density as possible ... > > Right, I'm just trying to narrow down the problem. I'm theorizing that > the problem is some sort of spinlock deadlock. Does it only occur if > there is activity or even if the lines are up but no calls taking place? I've had it happen while shutting down an idle Asterisk yesterday. Prior to shutting it down, there had been some activity on multiple channels of the E100P in that box, though, and this was the first time it happened on an idle box. It usually happens on call-setup or disconnect. I've never had it happen during established calls, unless some other Zap-channels connect / disconnect during those calls. BTW: As I reported in my previous mail to the list, I've now installed kernel 2.4.21-rc2 with ACPI-patch on the box with the E100P. I've been trying very hard to reproduce a freeze with this kernel, but haven't succeeded yet. Maybe others with the same problem could try this as well. I'm using Redhat 8 on that particular box, but doubt the distribution has anything to do with it. All Asterisk and Zaptel related stuff is latest CVS. The hardware is a Supermicro 8060 (http://www.supermicro.com/PRODUCT/SUPERServer/SuperServer8060.htm) with 4 700MHz PIII Xeons and 2GB of RAM. Besides the E100P, it also has an TDM400P and an Eicon Diva Server 4BRI. According to "/proc/interrupts", all devices have a unique IRQ. Grtz, Oliver _______________________________________________ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users
