[asterisk-users] Dahdi interface flapping

[Shaun Ruffell]

On Fri, Aug 02, 2013 at 10:12:54AM -0400, Andre Goree wrote:
> 
> Ran through a loopback test with Digium which seemingly proved that
> there was no issue with their card.  I've contacted my telco for
> assistance but so far have been unable to come up with
> anything...though there may be a timing slip issue.  In any case, the
> D-channel will indeed come up, but then after a while (at non-regular
> intervals), the D-channel goes down after this message in the logs:
> [2013-08-02 09:56:23] NOTICE[8688] chan_dahdi.c: PRI got event: HDLC Bad FCS (8) on D-channel of span 1
> [2013-08-02 09:56:23] NOTICE[8688] chan_dahdi.c: PRI got event: HDLC Bad FCS (8) on D-channel of span 1
> ...
> [2013-08-02 09:56:26] VERBOSE[8688] chan_dahdi.c: PRI Span: 1 TEI=0 MDL-ERROR (F): SABME in state 7(Multi-frame established)
> [2013-08-02 09:56:26] VERBOSE[8688] chan_dahdi.c: PRI Span: 1 TEI=0 MDL-ERROR (F): SABME in state 7(Multi-frame established)
> [2013-08-02 09:56:40] VERBOSE[8688] chan_dahdi.c: PRI Span: 1 TEI=0 MDL-ERROR (I): T200 expired N200 times sending RR/RNR in state 8(Timer recovery)
> [2013-08-02 09:56:40] VERBOSE[8688] chan_dahdi.c: PRI Span: 1 TEI=0 MDL-ERROR (I): T200 expired N200 times sending RR/RNR in state 8(Timer recovery)
> 
> In the meantime I've been trying to adjust smp_affinity for the te133
> IRQ (just for the hell of it and the fact that I'm running out of
> things to try)  but it apparently it's being reset automatically by
> something.  I.e., I'll run this:
> [root at asterisk-master ~]# echo 8 > /proc/irq/31/smp_affinity
> [root at asterisk-master ~]# cat /proc/irq/31/smp_affinity
> 08
> 
> but then, 5-10 secs later:
> [root at asterisk-master ~]# cat /proc/irq/31/smp_affinity
> 01
> 
> Have you ever seen something like that?

irqbalance will adjust the smp_affinity of interrupts. If you shut
it down you should be able to run your test.

> I'm using brand-newish hardware w/both the server and the card, so
> I wouldn't be surprised if I've run into some sort of new issue.
> I'm about to shut the server down now and give the BIOS settings a
> once-over just to make sure I'm not actually running into
> something weird hardware-wise.

Although, patlooptest ran clean. It's most likely either a)
misconfiguration between the card settings and the provider b)
cabling between the card and the smart jack or c) Just something bad
on the provider's end. The probability of it being system / hardware
related is low IMO.

I take it though your old install still works fine? What was the
reason you're replacing the old install anyway?

-- 
Shaun Ruffell
Digium, Inc. | Linux Kernel Developer
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us out at: www.digium.com & www.asterisk.org