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 <[email protected]>wrote: > On Tue, Jan 14, 2014 at 12:54 PM, Rodrigo Borges Pereira > <[email protected]> wrote: > > Interestingly, span 2 goes into loop mode, but patlooptest can't access > it: > > > >> patlooptest /dev/dahdi/2 -t 300 -vvvvv > > /dev/dahdi/2: Device or resource busy > > > > And I do not have Asterisk running. > You should be able to use "lsof /dev/dahdi/2" to find out what process > has the file open. > > > So I > > am a bit confused in what's the most correct way of doing this kind of > > tests. patlooptest + physical loopback? patlooptest alone? physical > loopback > > with some other method? > Physical loopback devices are nice because they encompass the cable > into testing. > Digital loopbacks are nice because you don't have to get up from your > desk and plug something in :-) We use them a lot in our automated > testing. > > One other thing to note. Sometimes patlooptest can be starved by the > process scheduler. When this happens, it won't have enough time to > produce or consume all the sequential bytes that it needs to. Then it > will report errors. You can try increasing the scheduler priority > with: > chrt 99 patlooptest <span> ... > > -- > Russ Meyerriecks > Digium, Inc. | Linux Kernel Developer > 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA > direct: +1 256-428-6025 > Check us out at: www.digium.com & www.asterisk.org > > -- > _____________________________________________________________________ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > New to Asterisk? Join us for a live introductory webinar every Thurs: > http://www.asterisk.org/hello > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users >
-- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
