asterisk users - Apr 2008 - Digium T1 Card Crashing Server (Dell 2950)

I installed the Digium T1 card on Dell Poweredge 2950 and the system crashed
several times, we got a Kernel Panic and first though it was the OS so I
switched from Fedora 7 to Centos 5.1.
Our server was alarming in our monitoring system, when our Infrastructure
department investigated the issue they found that the server was locked up
at the console. They had to do a hard reboot of the server to bring it back.
The following information was pulled from the logs:

BUG: soft lockup detected on CPU#1!
 [<c044b2a4>] softlockup_tick+0x96/0xa4
 [<c042e214>] update_process_times+0x39/0x5c
 [<c04196ff>] smp_apic_timer_interrupt+0x5b/0x6c
 [<c04059bf>] apic_timer_interrupt+0x1f/0x24
.............................

Apr 10 11:07:39 Newark1 php:
/var/lib/asterisk/agi-bin/libs_a2billing/Class.A2Billing.php[259]: Error
parsing /etc/asterisk//a2billing.conf on line 48
Apr 10 11:07:39 Newark1 php:
/var/lib/asterisk/agi-bin/libs_a2billing/Class.A2Billing.php[588]: Undefined
index:  asterisk_version
Apr 10 11:07:39 Newark1 php: /var/lib/asterisk/agi-bin/a2billing.php[150]:
Undefined index:  intro_prompt
Apr 10 11:39:59 Newark1 syslogd 1.4.1: restart.
Apr 10 11:39:59 Newark1 kernel: klogd 1.4.1, log source = /proc/kmsg
started.
I believe the issue may be related to a driver for Our Digium Interface.
Here is the versions we are running
Asterisk 1.4.19
libpri-1.4.3
zaptel-1.4.10
Digium's TE220 PCI Express card with echo cancellation.

Thanks.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20080410/a11d6876/attachment.htm

Any time you have this kind of hard lockup with a Digium card you should 
run, not walk to the nearest phone and call them.

broadband Voice wrote:
> I installed the Digium T1 card on Dell Poweredge 2950 and the system
crashed
> several times, we got a Kernel Panic and first though it was the OS so I
> switched from Fedora 7 to Centos 5.1.
> Our server was alarming in our monitoring system, when our Infrastructure
> department investigated the issue they found that the server was locked up
> at the console. They had to do a hard reboot of the server to bring it
back.
-- 
Consulting for Asterisk, Polycom, Sangoma, Digium, Cisco, LAN, WAN, QoS, 
T-1, PRI, Frame Relay, Linux, and network design.  Based near 
Birmingham, AL.  Now accepting clients worldwide.

> BUG: soft lockup detected on CPU#1!
>?[<c044b2a4>] softlockup_tick+0x96/0xa4
>?[<c042e214>] update_process_times+0x39/0x5c
>?[<c04196ff>] smp_apic_timer_interrupt+0x5b/0x6c
>?[<c04059bf>] apic_timer_interrupt+0x1f/0x24
> .............................
You don't happen to be running a XEN Kernel are you?  I saw this problem
while running CentOS 5.1 XEN kernel and if you search their bug tracking
system you will see some reports about this bug.  A search on google
revealed some possible solutions.

This was the first thought that came to my mind when I saw this.

Regards,

Michael L. Young
(elguero)