Just had the PRI Charter Communictions turned up two days ago. It seems that during the night dadhi stops and I cannot make incoming and outgoing calls and if do a reload and restart dadhi I can call in and out again.
Any suggestions.
I am using the Digium TE133e card times 2
You might get a clue with
grep wct /var/log/messages*
This is what I get when i issue that command
/var/log/messages:Mar 28 00:16:58 localhost kernel: wcte13xp 0000:0a:00.0: Underrun detected by hardware. Latency at max of 20ms.
/var/log/messages:Mar 28 00:17:03 localhost kernel: wcte13xp 0000:0a:00.0: Underrun detected by hardware. Latency at max of 20ms.
/var/log/messages:Mar 28 00:17:03 localhost kernel: wcte13xp 0000:0d:00.0: Underrun detected by hardware. Latency at max of 20ms.
/var/log/messages:Mar 28 00:17:03 localhost kernel: wcte13xp 0000:0a:00.0: Underrun detected by hardware. Latency at max of 20ms.
/var/log/messages:Mar 28 00:17:03 localhost kernel: wcte13xp 0000:0d:00.0: Underrun detected by hardware. Latency at max of 20ms.
/var/log/messages:Mar 28 00:17:03 localhost kernel: wcte13xp 0000:0a:00.0: Underrun detected by hardware. Latency at max of 20ms.
/var/log/messages:Mar 28 00:17:03 localhost kernel: wcte13xp 0000:0d:00.0: Underrun detected by hardware. Latency at max of 20ms.
/var/log/messages:Mar 28 00:17:03 localhost kernel: wcte13xp 0000:0a:00.0: Underrun detected by hardware. Latency at max of 20ms.
/var/log/messages:Mar 28 00:17:03 localhost kernel: wcte13xp 0000:0d:00.0: Underrun detected by hardware. Latency at max of 20ms.
/var/log/messages:Mar 28 00:17:03 localhost kernel: wcte13xp 0000:0a:00.0: Underrun detected by hardware. Latency at max of 20ms.
/var/log/messages:Mar 28 00:17:03 localhost kernel: wcte13xp 0000:0d:00.0: Underrun detected by hardware. Latency at max of 20ms.
/var/log/messages:Mar 28 00:17:08 localhost kernel: wcte13xp 0000:0d:00.0: Underrun detected by hardware. Latency at max of 20ms.
/var/log/messages:Mar 28 00:17:08 localhost kernel: wcte13xp 0000:0a:00.0: Underrun detected by hardware. Latency at max of 20ms.
/var/log/messages:Mar 28 00:17:08 localhost kernel: wcte13xp 0000:0d:00.0: Underrun detected by hardware. Latency at max of 20ms.
/var/log/messages:Mar 28 00:17:08 localhost kernel: wcte13xp 0000:0a:00.0: Underrun detected by hardware. Latency at max of 20ms.
/var/log/messages:Mar 28 00:17:08 localhost kernel: wcte13xp 0000:0d:00.0: Underrun detected by hardware. Latency at max of 20ms.
/var/log/messages:Mar 28 00:17:08 localhost kernel: wcte13xp 0000:0a:00.0: Underrun detected by hardware. Latency at max of 20ms.
/var/log/messages:Mar 28 00:17:08 localhost kernel: wcte13xp 0000:0d:00.0: Underrun detected by hardware. Latency at max of 20ms.
/var/log/messages:Mar 28 00:17:08 localhost kernel: wcte13xp 0000:0a:00.0: Underrun detected by hardware. Latency at max of 20ms.
/var/log/messages:Mar 28 00:17:08 localhost kernel: wcte13xp 0000:0d:00.0: Underrun detected by hardware. Latency at max of 20ms.
/var/log/messages:Mar 28 00:17:08 localhost kernel: wcte13xp 0000:0a:00.0: Underrun detected by hardware. Latency at max of 20ms.
/var/log/messages:Mar 28 00:17:13 localhost kernel: wcte13xp 0000:0a:00.0: Underrun detected by hardware. Latency at max of 20ms.
/var/log/messages:Mar 28 00:17:13 localhost kernel: wcte13xp 0000:0d:00.0: Underrun detected by hardware. Latency at max of 20ms.
/var/log/messages:Mar 28 00:17:13 localhost kernel: wcte13xp 0000:0a:00.0: Underrun detected by hardware. Latency at max of 20ms.
/var/log/messages:Mar 28 00:17:13 localhost kernel: wcte13xp 0000:0d:00.0: Underrun detected by hardware. Latency at max of 20ms.
/var/log/messages:Mar 28 00:17:13 localhost kernel: wcte13xp 0000:0a:00.0: Underrun detected by hardware. Latency at max of 20ms.
/var/log/messages:Mar 28 00:17:13 localhost kernel: wcte13xp 0000:0d:00.0: Underrun detected by hardware. Latency at max of 20ms.
/var/log/messages:Mar 28 00:17:13 localhost kernel: wcte13xp 0000:0a:00.0: Underrun detected by hardware. Latency at max of 20ms.
/var/log/messages:Mar 28 00:17:13 localhost kernel: wcte13xp 0000:0d:00.0: Underrun detected by hardware. Latency at max of 20ms.
/var/log/messages:Mar 28 00:17:13 localhost kernel: wcte13xp 0000:0a:00.0: Underrun detected by hardware. Latency at max of 20ms.
/var/log/messages:Mar 28 00:17:13 localhost kernel: wcte13xp 0000:0d:00.0: Underrun detected by hardware. Latency at max of 20ms.
/var/log/messages:Mar 28 00:17:18 localhost kernel: wcte13xp 0000:0d:00.0: Underrun detected by hardware. Latency at max of 20ms.
If those errors persist past you log lines timestamp, then that indicates an IRQ problem, make sure you are not “sharing” interrupts, then I suggest you should take that to Digium,
I have then on the phone as week speak
THey told me to do this with not luck
Note
IMPORTANT: In the event that you are still having issues after following the steps above, first make sure that your BIOS is fully up-to-date and secondly, you’ll want to make sure that APIC is disabled in your BIOS.
you can also do that in grub
https://www.centos.org/docs/5/html/5.2/Cluster_Administration/s2-acpi-disable-boot-CA.html
done it all and still same issue. I tried it on my DL380 G5 with a fresh install and no issues only on the DL 380 G6 does the issues arise
Oh well, that’s the younger generation for you 
.
what that suppose to mean. I am still on the phone with digium
Take it up with Dell also, it’s perhaps an incompatible hardware problem.
It is a issue with the DL380 G6 i and narrowed it down to that
Ok so digium support was very helpful. They told to install dahdi 2.10.2… I did and same issus when running dahdi_tool I kept on getting irq misses. So I called back and another tech told me to install 2.11.1. I now no IRQ misses. I also update the te133 firmware from http://downloads.digium.com/pub/telephony/firmware/releases/
This was on a HP DL380 G6 for reference.
────────┤ Wildcard TE131/TE133 Card 0 ├───────────────┐
┌─────│ │ ────┐
│ │ │ │
│ │ Current Alarms: Red Alarm │ │
│ │ Sync Source: Wildcard TE131/TE133 Card 0 │ ↑ │
│ │ IRQ Misses: 0 │ ▒ │
│ │ Bipolar Viol: 0 │ ▒ │
│ │ Tx/Rx Levels: 0/ 0 │ ▒ │
│ │ Total/Conf/Act: 24/ 24/ 0 │ ▒ │
│ │ 111111111122222 ┌──────┐ │ ▒ │
│ │ 123456789012345678901234 │ Back │ │ ▒ │
│ │ TxA ------------------------ └──────┘ │ ▒ │
│ │ TxB ------------------------ │ ▮ │
│ │ TxC ------------------------ │ ↓ │
│ │ TxD ------------------------ │ │
│ │ │ │
│ │ RxA ------------------------ │ │
│ │ RxB ------------------------ │ │
│ │ RxC ------------------------ │ │
│ │ RxD ------------------------ │ │
└─────│ │ ────┘
└──────────────────────────────────────────────────────
For the benefit of your peers, you might post a bug against this.
Already have all the info gathered up and will submit tommorrow.
Thanks for you help.
Bye the way I only come to the forums when I can’t figure it out on my own via google or searching through the forms.
We include DAHDI 2.11.1 already in the 10.13.66 Distro track
As would have all the “do it yourself” recipes on the wiki run after March 1 2016.
I installed freepbx 12 from the website fresh and it had a newer version of dahdi. I can’t Remeber what version off top of my head but I will check tommorrow.