[Asterisk-Users] tdm400p and dell 2600 poweredge

[Jeb Campbell]

Dennis Webb wrote:
> I'm using tdm400's here and was curious about the irq misses.  My zttool 
> won't compile for some reason and I haven't researched it enough to be 
> worried about it yet.  Is zttool the way to diagnose the irq issue and 
> does zttool work with the tdm400 boards.  I don't have a shared irq 
> issue but here's the output of /proc/interrupts.  is there anything else 
> to check?
> 
> cat /proc/interrupts
>            CPU0       CPU1
>   0:  172897707          0    IO-APIC-edge  timer
>   1:         11          0    IO-APIC-edge  i8042
>   2:          0          0          XT-PIC  cascade
>   8:          2          0    IO-APIC-edge  rtc
>   9:          0          0   IO-APIC-level  acpi
> 11:          0          0   IO-APIC-level  ohci_hcd
> 12:         50          0    IO-APIC-edge  i8042
> 14:         76          1    IO-APIC-edge  ide0
> 18:  172811936          0   IO-APIC-level  wctdm
> 20:  172802850          0   IO-APIC-level  wctdm
> 22:  172807318          0   IO-APIC-level  wctdm
> 24:  172791427          0   IO-APIC-level  wctdm
> 26:     361826          0   IO-APIC-level  cciss0
> 28:   11479585          0   IO-APIC-level  eth0
> 31:     293841          0   IO-APIC-level  aic7xxx, aic7xxx
> NMI:       5767          0
> LOC:  172894484  172894411
> ERR:          0
> MIS:          0

You appear to be fine as far as sharing irq's goes-- I must have had a 
2650 as I used the megaraid driver (Perc).  Sorry, to the list -- it was 
a while ago.

The quickest way (I know) to check for irq misses is to simply
"cat /proc/zaptel/1" and do that for each number [1,2,etc] that is in 
there (you get a number for each card).  If it doesn't say "irq misses = 
  number" then you don't have a problem.

Also I would not be worried (especially on non t1) to have a few misses 
since you loaded the modules (that's when it starts the count).  When I 
was having problems, I was getting hundreds of irq misses a minute.

For zttool to compile you must have newt installed (or libnewt & 
libnewt-devel for rpm distros -- something like that anyway).  Hope that 
helps.

Jeb Campbell
jebc at c4solutions.net