VoIP Mailing List Archives

[rodrigoborgespereira a...]

Hi there,

Running patlooptest following instructions on Digium KB, using dahdi 2.5.1 with a TE205P. I'm getting this kind of output (not full output). Note, I'm using a standard cat5 ethernet cable (30cm), with a Digium T10i crossover.




Error 4985 (loop 19898, offset 425, error 214): Unexpected result, Read: 0xff, Expected 0x00.
Offset 422  { ff ff ff ff ff ff ff }
Error 4986 (loop 19898, offset 426, error 215): Unexpected result, Read: 0xff, Expected 0x00.
Offset 423  { ff ff ff ff ff ff ff }
Error 4987 (loop 19898, offset 427, error 216): Unexpected result, Read: 0xff, Expected 0x00.
Offset 424  { ff ff ff ff ff ff ff }
Error 4988 (loop 19898, offset 428, error 217): Unexpected result, Read: 0xff, Expected 0x00.
Offset 425  { ff ff ff ff ff ff ff }
Error 4989 (loop 19898, offset 429, error 218): Unexpected result, Read: 0xff, Expected 0x00.
Offset 426  { ff ff ff ff ff ff 2e }
Error 4990 (loop 19898, offset 430, error 219): Unexpected result, Read: 0xff, Expected 0x00.
Offset 427  { ff ff ff ff ff 2e 2f }
Error 4991 (loop 19898, offset 431, error 220): Unexpected result, Read: 0xff, Expected 0x00.
Offset 428  { ff ff ff ff 2e 2f 30 }
Error 4992 (loop 19898, offset 432, error 221): Unexpected result, Read: 0x2e, Expected 0x00.
Offset 429  { ff ff ff 2e 2f 30 31 }
Event: 29
Event: 30
Error 4993 (loop 24990, offset 0, error 1): Unexpected result, Read: 0x7e, Expected 0x7a.
Offset 0  { 7e 7f 80 81 }
Error 4994 (loop 24990, offset 428, error 2): Unexpected result, Read: 0xff, Expected 0x2a.
Offset 425  { 27 28 29 ff ff ff ff }
Error 4995 (loop 24990, offset 429, error 3): Unexpected result, Read: 0xff, Expected 0x00.
Offset 426  { 28 29 ff ff ff ff 2a }
Error 4996 (loop 24990, offset 430, error 4): Unexpected result, Read: 0xff, Expected 0x00.
Offset 427  { 29 ff ff ff ff 2a 2b }



Cause for concern? 


I'm testing a card which has been used before without issues. I'm just playing with patlooptest for the first time, and wasn't expecting to see this on a supposedly good card.


appreciate any input, thx.


rgds.

[rmeyerriecks at digium...]

On Tue, Jan 14, 2014 at 11:58 AM, Rodrigo Borges Pereira
<rodrigoborgespereira@gmail.com> wrote:

[rodrigoborgespereira a...]

Thanks.

The cable is straight, and I was using it together with dahdi:maint. Both spans are set to provide (0). I've now tested span 1 again without cable, and still same kind of result:


Timeout achieved Ending Program
Test ran 28309 loops of 2039 bytes/loop with 3692 errors



Interestingly, span 2 goes into loop mode, but patlooptest can't access it:

[rmeyerriecks at digium...]

On Tue, Jan 14, 2014 at 12:54 PM, Rodrigo Borges Pereira
<rodrigoborgespereira@gmail.com> wrote:

[rodrigoborgespereira a...]

Thanks for the tips. I forgot to mention, i did try lsof, and it comes out with no result.

There is one thing I see different between the spans:


shell> head /proc/dahdi/1
Span 1: TE2/0/1 "T2XXP (PCI) Card 0 Span 1" B8ZS/ESF LOOP 


  1 TE2/0/1/1 Clear Master RED 
  2 TE2/0/1/2 Clear RED 
  3 TE2/0/1/3 Clear RED 
  4 TE2/0/1/4 Clear RED 
  5 TE2/0/1/5 Clear RED 
  6 TE2/0/1/6 Clear RED 
  7 TE2/0/1/7 Clear RED 
  8 TE2/0/1/8 Clear RED 
shell> head /proc/dahdi/2
Span 2: TE2/0/2 "T2XXP (PCI) Card 0 Span 2" (MASTER) B8ZS/ESF LOOP 
CRC4 error count: 1
E-bit error count: 1


 25 TE2/0/2/1 Clear Master LOOP 
 26 TE2/0/2/2 Clear LOOP 
 27 TE2/0/2/3 Clear LOOP 
 28 TE2/0/2/4 Clear LOOP 
 29 TE2/0/2/5 Clear LOOP 
 30 TE2/0/2/6 Clear LOOP 
shell> cat /etc/dahdi/system.conf 
loadzone=us
defaultzone=us
span=1,0,0,esf,b8zs
clear=1-24
span=2,0,0,esf,b8zs
clear=25-48


Note the CRC4 and E-bit lines on span 2.


 Right now both ports are in loop mode, no cable attached.


Maybe you guys @ Digium have seen this before as a symptom of card malfunction?



Thanks.



On Tue, Jan 14, 2014 at 9:18 PM, Russ Meyerriecks <rmeyerriecks@digium.com (rmeyerriecks@digium.com)> wrote:

[sruffell at digium.com]

On Tue, Jan 14, 2014 at 05:58:57PM +0000, Rodrigo Borges Pereira wrote:

[rodrigoborgespereira a...]

Ok, I'm a believer now:




shell> chrt -f 99 patlooptest /dev/dahdi/1 -t 300 -vvvvv 
Using Timeout of 300 Seconds
Going for it...
Timeout achieved Ending Program
Test ran 28295 loops of 2039 bytes/loop with 0 errors




Still, any hint about this?


shell> lsof /dev/dahdi/2
shell> 

shell> chrt -f 99 patlooptest /dev/dahdi/2 -t 300 -vvvvv 
/dev/dahdi/2: Device or resource busy



Thanks.





On Wed, Jan 15, 2014 at 12:48 AM, Shaun Ruffell <sruffell@digium.com (sruffell@digium.com)> wrote:

[sruffell at digium.com]

On Wed, Jan 15, 2014 at 04:00:19AM +0000, Rodrigo Borges Pereira wrote:

[rodrigoborgespereira a...]

Still no luck:

shell> pgrep asterisk
shell> ps -ef | grep asterisk
shell> lsof /dev/dahdi/channel
shell> lsof /dev/dahdi/1      
shell> lsof /dev/dahdi/2
shell> chrt -f 99 patlooptest /dev/dahdi/2 -t 300 -vvvvv 
/dev/dahdi/2: Device or resource busy



I can assure no PBX related process is running.





On Wed, Jan 15, 2014 at 4:14 PM, Shaun Ruffell <sruffell@digium.com (sruffell@digium.com)> wrote:

[sruffell at digium.com]

On Wed, Jan 15, 2014 at 04:18:55PM +0000, Rodrigo Borges Pereira wrote:

[amertel at pipeline.com]

I tried it on 123. Those user and PW did not work

Sent from my Verizon Wireless 4G LTE DROID



Shaun Ruffell <sruffell@digium.com> wrote:

On Wed, Jan 15, 2014 at 04:00:19AM +0000, Rodrigo Borges Pereira wrote:

[rodrigoborgespereira a...]

No, I see this:

shell> cat /proc/dahdi/2
Span 2: TE2/0/2 "T2XXP (PCI) Card 0 Span 2" (MASTER) B8ZS/ESF LOOP 
CRC4 error count: 1
E-bit error count: 1


 25 TE2/0/2/1 Clear Master LOOP 
 26 TE2/0/2/2 Clear LOOP 
 27 TE2/0/2/3 Clear LOOP 
 28 TE2/0/2/4 Clear LOOP 
 29 TE2/0/2/5 Clear LOOP 
 30 TE2/0/2/6 Clear LOOP 
 31 TE2/0/2/7 Clear LOOP 
 32 TE2/0/2/8 Clear LOOP 
 33 TE2/0/2/9 Clear LOOP 
 34 TE2/0/2/10 Clear LOOP 
 35 TE2/0/2/11 Clear LOOP 
 36 TE2/0/2/12 Clear LOOP 
 37 TE2/0/2/13 Clear LOOP 
 38 TE2/0/2/14 Clear LOOP 
 39 TE2/0/2/15 Clear LOOP 
 40 TE2/0/2/16 Clear LOOP 
 41 TE2/0/2/17 Clear LOOP 
 42 TE2/0/2/18 Clear LOOP 
 43 TE2/0/2/19 Clear LOOP 
 44 TE2/0/2/20 Clear LOOP 
 45 TE2/0/2/21 Clear LOOP 
 46 TE2/0/2/22 Clear LOOP 
 47 TE2/0/2/23 Clear LOOP 
 48 TE2/0/2/24 Clear LOOP 



shell> cat /proc/dahdi/1
Span 1: TE2/0/1 "T2XXP (PCI) Card 0 Span 1" B8ZS/ESF LOOP 


  1 TE2/0/1/1 Clear Master RED 
  2 TE2/0/1/2 Clear RED 
  3 TE2/0/1/3 Clear RED 
  4 TE2/0/1/4 Clear RED 
  5 TE2/0/1/5 Clear RED 
  6 TE2/0/1/6 Clear RED 
  7 TE2/0/1/7 Clear RED 
  8 TE2/0/1/8 Clear RED 
  9 TE2/0/1/9 Clear RED 
 10 TE2/0/1/10 Clear RED 
 11 TE2/0/1/11 Clear RED 
 12 TE2/0/1/12 Clear RED 
 13 TE2/0/1/13 Clear RED 
 14 TE2/0/1/14 Clear RED 
 15 TE2/0/1/15 Clear RED 
 16 TE2/0/1/16 Clear RED 
 17 TE2/0/1/17 Clear RED 
 18 TE2/0/1/18 Clear RED 
 19 TE2/0/1/19 Clear RED 
 20 TE2/0/1/20 Clear RED 
 21 TE2/0/1/21 Clear RED 
 22 TE2/0/1/22 Clear RED 
 23 TE2/0/1/23 Clear RED 
 24 TE2/0/1/24 Clear RED 




On Wed, Jan 15, 2014 at 4:28 PM, Shaun Ruffell <sruffell@digium.com (sruffell@digium.com)> wrote:

[sruffell at digium.com]

On Wed, Jan 15, 2014 at 05:02:10PM +0000, Rodrigo Borges Pereira wrote:

[rodrigoborgespereira a...]

Shaun, sorry to insist on this, but this kind of diagnostic is new for me and extremely valuable for my support operations.

You say "when configured this way".. do you mean regarding dahdi? Here's my system conf, based on your KB article for loop testing:


shell> cat system.conf 
loadzone=us
defaultzone=us
span=1,0,0,esf,b8zs
clear=1-24
span=2,0,0,esf,b8zs
clear=25-48



How could  I configure now so I can get conclusive readings for span2?


Thanks.







On Wed, Jan 15, 2014 at 5:06 PM, Shaun Ruffell <sruffell@digium.com (sruffell@digium.com)> wrote:

[sruffell at digium.com]

On Wed, Jan 15, 2014 at 05:29:44PM +0000, Rodrigo Borges Pereira wrote: