Re: [ nocadm ] Re: [Asterisk-Users] HDLC Bad FCS / HDLC Abort

2005-02-22 Thread Alex G Robertson
Did you confirm you are not running graphics?  (X, frame buffer, etc). 
 Did you confirm you have unmasked IDE interrupts (-u1 to haparm)?
Yes and Yes. ;-)
# hdparm -i /dev/hd[ac]
/dev/hda:
 Model=SAMSUNG SP1203N, FwRev=TL100-24, SerialNo=0836J1FX419316
 Config={ HardSect NotMFM HdSw15uSec Fixed DTR10Mbs }
 RawCHS=16383/16/63, TrkSize=34902, SectSize=554, ECCbytes=4
 BuffType=DualPortCache, BuffSize=2048kB, MaxMultSect=16, MultSect=16
 CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=234493056
 IORDY=on/off, tPIO={min:240,w/IORDY:120}, tDMA={min:120,rec:120}
 PIO modes:  pio0 pio1 pio2 pio3 pio4
 DMA modes:  mdma0 mdma1 mdma2
 UDMA modes: udma0 udma1 udma2 *udma3 udma4 udma5
 AdvancedPM=no WriteCache=enabled
 Drive conforms to: (null):
 * signifies the current active mode
/dev/hdc:
 Model=SAMSUNG SP1203N, FwRev=TL100-24, SerialNo=0836J1FX419368
 Config={ HardSect NotMFM HdSw15uSec Fixed DTR10Mbs }
 RawCHS=16383/16/63, TrkSize=34902, SectSize=554, ECCbytes=4
 BuffType=DualPortCache, BuffSize=2048kB, MaxMultSect=16, MultSect=16
 CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=234493056
 IORDY=on/off, tPIO={min:240,w/IORDY:120}, tDMA={min:120,rec:120}
 PIO modes:  pio0 pio1 pio2 pio3 pio4
 DMA modes:  mdma0 mdma1 mdma2
 UDMA modes: udma0 udma1 udma2 *udma3 udma4 udma5
 AdvancedPM=no WriteCache=enabled
 Drive conforms to: (null):
 * signifies the current active mode
--
Alex G Robertson
NOC - Microlink
___
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
  http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [ nocadm ] Re: [Asterisk-Users] HDLC Bad FCS / HDLC Abort

2005-02-22 Thread Eric Wieling
Alex G Robertson wrote:
Did you confirm you are not running graphics?  (X, frame buffer, etc). 
 Did you confirm you have unmasked IDE interrupts (-u1 to haparm)?

Yes and Yes. ;-)
# hdparm -i /dev/hd[ac]
/dev/hda:
 Model=SAMSUNG SP1203N, FwRev=TL100-24, SerialNo=0836J1FX419316
 Config={ HardSect NotMFM HdSw15uSec Fixed DTR10Mbs }
 RawCHS=16383/16/63, TrkSize=34902, SectSize=554, ECCbytes=4
 BuffType=DualPortCache, BuffSize=2048kB, MaxMultSect=16, MultSect=16
 CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=234493056
 IORDY=on/off, tPIO={min:240,w/IORDY:120}, tDMA={min:120,rec:120}
 PIO modes:  pio0 pio1 pio2 pio3 pio4
 DMA modes:  mdma0 mdma1 mdma2
 UDMA modes: udma0 udma1 udma2 *udma3 udma4 udma5
 AdvancedPM=no WriteCache=enabled
 Drive conforms to: (null):
Try hdparm -v /dev/hda
___
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
  http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [ nocadm ] Re: [Asterisk-Users] HDLC Bad FCS / HDLC Abort

2005-02-22 Thread Alex G Robertson

 Try hdparm -v /dev/hda

Here it is
# hdparm -v /dev/hd[ac]
/dev/hda:
 multcount= 16 (on)
 IO_support   =  1 (32-bit)
 unmaskirq=  1 (on)
 using_dma=  1 (on)
 keepsettings =  0 (off)
 readonly =  0 (off)
 readahead=  8 (on)
 geometry = 14596/255/63, sectors = 234493056, start = 0
/dev/hdc:
 multcount= 16 (on)
 IO_support   =  1 (32-bit)
 unmaskirq=  1 (on)
 using_dma=  1 (on)
 keepsettings =  0 (off)
 readonly =  0 (off)
 readahead=  8 (on)
 geometry = 14596/255/63, sectors = 234493056, start = 0

[]s
--
Alex G Robertson
NOC - Microlink
___
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
  http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [ nocadm ] Re: [Asterisk-Users] HDLC Bad FCS / HDLC Abort

2005-02-21 Thread Alex G Robertson
Eric Wieling wrote:
 Yes.  There are lots of messages in the mailing list archives regarding
 this problem, some of them even include things to try.  You didn't see
 these messages when you searched the mailing list archives?

Yes, I've read then.
They say it can be caused by interruptions.
I tried asterisk on kernels 2.4.29 and on 2.6.10 and I got the same errors.
At this moment, I am running the latest version available on cvs on kernel 
2.6.10 and I took off all other cards (4 FXO - Intel Ambient 3200) and  still 
get the errors.

The TE405P card is not loosing interruptions any more...
Have a see...
# cat /proc/interrupts
   CPU0
  0:4454368  XT-PIC  timer
  1:589  XT-PIC  i8042
  2:  0  XT-PIC  cascade
  8:  2  XT-PIC  rtc
 10:4421380  XT-PIC  t4xxp
 11:  10671  XT-PIC  eth0
 14:   3163  XT-PIC  ide0
 15:   3125  XT-PIC  ide1
NMI:  0
ERR:  0
# cat /proc/zaptel/1
Span 1: TE4/0/1 TE410P (PCI) Card 0 Span 1 B8ZS/ESF
   1 TE4/0/1/1 FXOKS (In use)
   2 TE4/0/1/2 FXOKS (In use)
   3 TE4/0/1/3 FXOKS (In use)
   4 TE4/0/1/4 FXOKS (In use)
[...]
# cat /proc/zaptel/4
Span 4: TE4/0/4 TE410P (PCI) Card 0 Span 4 HDB3/CCS
  73 TE4/0/4/1 Clear (In use)
  74 TE4/0/4/2 Clear (In use)
[...]
I contacted Digium Instalation Support and I am waiting for their response.
[]s
Alex Robertson
Alex G Robertson wrote:
Some news.
It is not caused by transmission lines, conectors or anything like that.
The telco tecnician just came here and analyzed the circuit and he got 
no erros!

He sugested me to loop my PRI port in the balum attached in my 
asterisk box. And Surprise...

I got the same errors!
The error is on my hardware/software.
[]s
Alex Robertson
Alex G Robertson wrote:
Hi everybody,
I just installed asterisk, but this NOTICE dont stop appearing on my 
log file;;

Feb 17 18:30:11 NOTICE[1336]: PRI got event: HDLC Bad FCS (8) on 
Primary D-channel of span 4
Feb 17 18:29:42 NOTICE[1336]: PRI got event: HDLC Abort (6) on 
Primary D-channel of span 4
Feb 17 18:29:41 NOTICE[1336]: PRI got event: HDLC Abort (6) on 
Primary D-channel of span 4
Feb 17 18:29:41 NOTICE[1336]: PRI got event: HDLC Bad FCS (8) on 
Primary D-channel of span 4
Feb 17 18:27:11 NOTICE[1336]: PRI got event: HDLC Abort (6) on 
Primary D-channel of span 4
Feb 17 18:26:51 NOTICE[1336]: PRI got event: HDLC Bad FCS (8) on 
Primary D-channel of span 4
Feb 17 18:25:11 NOTICE[1336]: PRI got event: HDLC Bad FCS (8) on 
Primary D-channel of span 4
Feb 17 18:24:41 NOTICE[1336]: PRI got event: HDLC Abort (6) on 
Primary D-channel of span 4
Feb 17 18:22:21 NOTICE[1336]: PRI got event: HDLC Abort (6) on 
Primary D-channel of span 4
Feb 17 18:21:16 NOTICE[1336]: PRI got event: HDLC Bad FCS (8) on 
Primary D-channel of span 4
Feb 17 18:21:15 NOTICE[1336]: PRI got event: HDLC Bad FCS (8) on 
Primary D-channel of span 4
Feb 17 18:21:15 NOTICE[1336]: PRI got event: HDLC Bad FCS (8) on 
Primary D-channel of span 4
Feb 17 18:21:15 NOTICE[1336]: PRI got event: HDLC Bad FCS (8) on 
Primary D-channel of span 4
Feb 17 18:21:15 NOTICE[1336]: PRI got event: HDLC Abort (6) on 
Primary D-channel of span 4
Feb 17 18:21:15 NOTICE[1336]: PRI got event: HDLC Bad FCS (8) on 
Primary D-channel of span 4
Feb 17 18:21:14 NOTICE[1336]: PRI got event: HDLC Bad FCS (8) on 
Primary D-channel of span 4
Feb 17 18:21:14 NOTICE[1336]: PRI got event: HDLC Bad FCS (8) on 
Primary D-channel of span 4
Feb 17 18:21:14 NOTICE[1336]: PRI got event: HDLC Bad FCS (8) on 
Primary D-channel of span 4
Feb 17 18:21:13 NOTICE[1336]: PRI got event: HDLC Abort (6) on 
Primary D-channel of span 4
Feb 17 18:21:12 NOTICE[1336]: PRI got event: HDLC Bad FCS (8) on 
Primary D-channel of span 4
Feb 17 18:21:11 NOTICE[1336]: PRI got event: HDLC Bad FCS (8) on 
Primary D-channel of span 4
Feb 17 18:21:01 NOTICE[1336]: PRI got event: HDLC Bad FCS (8) on 
Primary D-channel of span 4

And from time to time this is happening
-- B-channel 0/1 successfully restarted on span 4
-- B-channel 0/2 successfully restarted on span 4
-- B-channel 0/3 successfully restarted on span 4
-- B-channel 0/4 successfully restarted on span 4
[...]
-- B-channel 0/29 successfully restarted on span 4
-- B-channel 0/30 successfully restarted on span 4
-- B-channel 0/31 successfully restarted on span 4
And the conversation stops.
Telco, with a traffic analyzer, says that the clock is sliding.
Does anybody knows what can it be? Hardware, software, transmission 
(conectors) etc ?

Thanks in advance.
--
Alex G Robertson
NOC - Microlink
___
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
  http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [ nocadm ] Re: [Asterisk-Users] HDLC Bad FCS / HDLC Abort

2005-02-21 Thread Alex G Robertson
Sergey Kuznetsov wrote:
This is happens because of imperfect HDLC code. 
Do you mean the software? The source code?
[]s
--
Alex G Robertson
NOC - Microlink
___
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
  http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [ nocadm ] Re: [Asterisk-Users] HDLC Bad FCS / HDLC Abort

2005-02-21 Thread Eric Wieling
Alex G Robertson wrote:
Eric Wieling wrote:
  Yes.  There are lots of messages in the mailing list archives regarding
  this problem, some of them even include things to try.  You didn't see
  these messages when you searched the mailing list archives?
 
Yes, I've read then.
They say it can be caused by interruptions.
Did you confirm you are not running graphics?  (X, frame buffer, etc). 
 Did you confirm you have unmasked IDE interrupts (-u1 to haparm)?

--Eric
___
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
  http://lists.digium.com/mailman/listinfo/asterisk-users