Re: [asterisk-users] PRI got event: HDLC Abort (6) on Primary D-channel of span 1 (fwd)
i had the same Problem, but i don't know why, i spitted the second card in a second Asterisk Box, and its wokring, with 2 TE405P in one Server its not working. If you solved the Problem, please let me know. Thanks Nico On Thu, 20 Jul 2006, asterisk wrote: Hi all, We have two server with *. With 2-2 PRI card (sangoma , digium TE110P, digium TE100P).server 1: - asterisk: SVN-branch-1.2-r36998M - span 1 Digium Wildcard TE110P T1/E1 - span 2 Digium Wildcard TE110P T1/E1 zap show status Description Alarms IRQbpviol CRC4 Digium Wildcard TE110P T1/E1 Card 0 OK 0 0 0 Digium Wildcard TE110P T1/E1 Card 1 OK 0 0 0 server 2: - asterisk: SVN-branch-1.2-r37402M - span 0 Digium Wildcard E100P E1/PRA - span 1 wanpipe1 (Sangoma) zap show status Description Alarms IRQbpviol CRC4 Digium Wildcard E100P E1/PRA Card 0 OK 0 0 0 wanpipe1 card 0 OK 0 0 0 server 1 connecting to server 2 with two E1 cross cable. server 1 drops the next messages: Jul 20 10:23:24 NOTICE[11074]: chan_zap.c:8207 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Jul 20 10:23:27 NOTICE[11074]: chan_zap.c:8207 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Jul 20 10:23:27 NOTICE[11074]: chan_zap.c:8207 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Jul 20 10:23:28 NOTICE[11074]: chan_zap.c:8207 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Jul 20 10:24:29 NOTICE[11074]: chan_zap.c:8207 pri_dchannel: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 Jul 20 10:24:29 NOTICE[11074]: chan_zap.c:8207 pri_dchannel: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 Jul 20 10:24:29 NOTICE[11074]: chan_zap.c:8207 pri_dchannel: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 Jul 20 10:25:04 NOTICE[11074]: chan_zap.c:8207 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Jul 20 10:25:04 NOTICE[11074]: chan_zap.c:8207 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Jul 20 10:25:04 NOTICE[11074]: chan_zap.c:8207 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Jul 20 10:26:26 NOTICE[11074]: chan_zap.c:8207 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Jul 20 10:26:26 NOTICE[11074]: chan_zap.c:8207 pri_dchannel: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 Jul 20 10:26:28 NOTICE[11074]: chan_zap.c:8207 pri_dchannel: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 Jul 20 10:26:29 NOTICE[11074]: chan_zap.c:8207 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Jul 20 10:26:29 NOTICE[11074]: chan_zap.c:8207 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Jul 20 10:26:59 NOTICE[11074]: chan_zap.c:8207 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Jul 20 10:27:00 NOTICE[11074]: chan_zap.c:8207 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Jul 20 10:27:19 NOTICE[11074]: chan_zap.c:8207 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Jul 20 10:27:19 NOTICE[11074]: chan_zap.c:8207 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Jul 20 10:27:26 NOTICE[11074]: chan_zap.c:8207 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Jul 20 10:27:26 NOTICE[11074]: chan_zap.c:8207 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 server 2 dont drop nothing zaptel.conf on server 1: loadzone=hu defaultzone=hu # TE110P PRI interface [wcte11xp kernel module] span=1,1,0,ccs,hdb3,crc4 bchan=1-15 dchan=16 bchan=17-31 span=2,2,0,ccs,hdb3,crc4 bchan=32-46 dchan=47 bchan=48-62 zaptel.conf on server 2: loadzone=hu defaultzone=hu # E100P PRI interface [wct1xxp kernel module] span=1,1,0,ccs,hdb3,crc4 bchan=1-15 dchan=16 bchan=17-31 # Sangoma A101u PRI span=2,0,0,ccs,hdb3,crc4 bchan=32-46 dchan=47 bchan=48-62 can you give me some help? How can i fix this problem? Thx Kind regards, Szolke ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[asterisk-users] PRI got event: HDLC Abort (6) on Primary D-channel of span 1
Hi all, We have two server with *. With 2-2 PRI card (sangoma , digium TE110P, digium TE100P). server 1: - asterisk: SVN-branch-1.2-r36998M - span 1 Digium Wildcard TE110P T1/E1 - span 2 Digium Wildcard TE110P T1/E1 zap show status Description Alarms IRQ bpviol CRC4 Digium Wildcard TE110P T1/E1 Card 0 OK 0 0 0 Digium Wildcard TE110P T1/E1 Card 1 OK 0 0 0 server 2: - asterisk: SVN-branch-1.2-r37402M - span 0 Digium Wildcard E100P E1/PRA - span 1 wanpipe1 (Sangoma) zap show status Description Alarms IRQ bpviol CRC4 Digium Wildcard E100P E1/PRA Card 0 OK 0 0 0 wanpipe1 card 0 OK 0 0 0 server 1 connecting to server 2 with two E1 cross cable. server 1 drops the next messages: Jul 20 10:23:24 NOTICE[11074]: chan_zap.c:8207 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Jul 20 10:23:27 NOTICE[11074]: chan_zap.c:8207 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Jul 20 10:23:27 NOTICE[11074]: chan_zap.c:8207 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Jul 20 10:23:28 NOTICE[11074]: chan_zap.c:8207 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Jul 20 10:24:29 NOTICE[11074]: chan_zap.c:8207 pri_dchannel: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 Jul 20 10:24:29 NOTICE[11074]: chan_zap.c:8207 pri_dchannel: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 Jul 20 10:24:29 NOTICE[11074]: chan_zap.c:8207 pri_dchannel: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 Jul 20 10:25:04 NOTICE[11074]: chan_zap.c:8207 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Jul 20 10:25:04 NOTICE[11074]: chan_zap.c:8207 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Jul 20 10:25:04 NOTICE[11074]: chan_zap.c:8207 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Jul 20 10:26:26 NOTICE[11074]: chan_zap.c:8207 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Jul 20 10:26:26 NOTICE[11074]: chan_zap.c:8207 pri_dchannel: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 Jul 20 10:26:28 NOTICE[11074]: chan_zap.c:8207 pri_dchannel: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 Jul 20 10:26:29 NOTICE[11074]: chan_zap.c:8207 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Jul 20 10:26:29 NOTICE[11074]: chan_zap.c:8207 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Jul 20 10:26:59 NOTICE[11074]: chan_zap.c:8207 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Jul 20 10:27:00 NOTICE[11074]: chan_zap.c:8207 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Jul 20 10:27:19 NOTICE[11074]: chan_zap.c:8207 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Jul 20 10:27:19 NOTICE[11074]: chan_zap.c:8207 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Jul 20 10:27:26 NOTICE[11074]: chan_zap.c:8207 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Jul 20 10:27:26 NOTICE[11074]: chan_zap.c:8207 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 server 2 dont drop nothing zaptel.conf on server 1: loadzone=hu defaultzone=hu # TE110P PRI interface [wcte11xp kernel module] span=1,1,0,ccs,hdb3,crc4 bchan=1-15 dchan=16 bchan=17-31 span=2,2,0,ccs,hdb3,crc4 bchan=32-46 dchan=47 bchan=48-62 zaptel.conf on server 2: loadzone=hu defaultzone=hu # E100P PRI interface [wct1xxp kernel module] span=1,1,0,ccs,hdb3,crc4 bchan=1-15 dchan=16 bchan=17-31 # Sangoma A101u PRI span=2,0,0,ccs,hdb3,crc4 bchan=32-46 dchan=47 bchan=48-62 can you give me some help? How can i fix this problem? Thx Kind regards, Szolke ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] PRI got event: HDLC Abort (6) on Primary D-channel of span 1
See inline comments: Peter Svensson wrote: What span is your clock source? A TE405P card can only operate in one clock domain at a time. I.e. the same clock will be used on all of them. Not correct, I actual have span 1 connected to my telco and span 2 connected to a Norstar PBX. See diagram. Telco - Asterisk - Norstar PBX If both providers are connected to the same TE405P card you will most likely have a problem with one of them unless they in turn have their clocks locked to a common source. For this, span 1 is CPE and span 2 is network. Two differently clocked sources wil manifest themselves as the occasional bit slip. I am not sure if a bit slip can cause the problems on the D channel you are seeing. Before I when into production, I created a stress test using the TE405P and a Dialogic D/MV960A 4T1. Between both cards, I had different clocking sources on each port; not a problem. I was able to generate millions of calls between the two with out any problems, Peter Anyways, the source of my problem was infact the telco, and 6 hours after asterisk reported my PRI's down, the telco brought the D-channel back in service, and asterisk went back to work. Did not even reboot the machine. PB ___ 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
[Asterisk-Users] PRI got event: HDLC Abort (6) on Primary D-channel of span 1
Evening all, Just got my first PRI got event: HDLC Abort (6) on Primary D-channel of span 1 error message. Our production box has been up for ~2 month. We are Asterisk 1.0.9 with Slackware 10.1. Now I have search the lists from this message and hear all the problem. Everything from asterisk and IRQ's to telco issue. I hear to night, to say.. I'm pretty sure mine is a telco issue. Reason I think this, check out how soon after my HDLC Abort (6) error I get Red Alarms. Right away. Most of the other issue, HDLC Abort (6) repeats many times. Jul 20 18:27:50 NOTICE[2650]: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Jul 20 18:27:50 WARNING[2652]: Detected alarm on channel 1: Red Alarm Jul 20 18:27:50 WARNING[2652]: Unable to disable echo cancellation on channel 1 Jul 20 18:27:50 WARNING[2652]: Detected alarm on channel 2: Red Alarm Jul 20 18:27:50 WARNING[2652]: Unable to disable echo cancellation on channel 2 Jul 20 18:27:50 WARNING[2652]: Detected alarm on channel 3: Red Alarm Jul 20 18:27:50 WARNING[2652]: Unable to disable echo cancellation on channel 3 Jul 20 18:27:50 WARNING[2652]: Detected alarm on channel 4: Red Alarm Jul 20 18:27:50 WARNING[2652]: Unable to disable echo cancellation on channel 4 Jul 20 18:27:50 WARNING[2652]: Detected alarm on channel 5: Red Alarm Jul 20 18:27:50 WARNING[2652]: Unable to disable echo cancellation on channel 5 Jul 20 18:27:50 WARNING[2652]: Detected alarm on channel 6: Red Alarm Jul 20 18:27:50 WARNING[2652]: Unable to disable echo cancellation on channel 6 Jul 20 18:27:50 WARNING[2652]: Detected alarm on channel 7: Red Alarm Jul 20 18:27:50 WARNING[2652]: Unable to disable echo cancellation on channel 7 Jul 20 18:27:50 WARNING[2652]: Detected alarm on channel 8: Red Alarm Jul 20 18:27:50 WARNING[2652]: Unable to disable echo cancellation on channel 8 Jul 20 18:27:50 WARNING[2652]: Detected alarm on channel 9: Red Alarm Jul 20 18:27:50 WARNING[2652]: Unable to disable echo cancellation on channel 9 Jul 20 18:27:50 WARNING[2652]: Detected alarm on channel 10: Red Alarm Jul 20 18:27:50 WARNING[2652]: Unable to disable echo cancellation on channel 10 Jul 20 18:27:50 WARNING[2652]: Detected alarm on channel 11: Red Alarm Jul 20 18:27:50 WARNING[2652]: Unable to disable echo cancellation on channel 11 Jul 20 18:27:50 WARNING[2652]: Detected alarm on channel 12: Red Alarm Jul 20 18:27:50 WARNING[2652]: Unable to disable echo cancellation on channel 12 Jul 20 18:27:50 WARNING[2652]: Detected alarm on channel 13: Red Alarm Jul 20 18:27:50 WARNING[2652]: Unable to disable echo cancellation on channel 13 Jul 20 18:27:50 WARNING[2652]: Detected alarm on channel 14: Red Alarm Jul 20 18:27:50 WARNING[2652]: Unable to disable echo cancellation on channel 14 Jul 20 18:27:50 WARNING[2652]: Detected alarm on channel 15: Red Alarm Jul 20 18:27:50 WARNING[2652]: Unable to disable echo cancellation on channel 15 Jul 20 18:27:50 WARNING[2652]: Detected alarm on channel 16: Red Alarm Jul 20 18:27:50 WARNING[2652]: Unable to disable echo cancellation on channel 16 Jul 20 18:27:50 WARNING[2652]: Detected alarm on channel 17: Red Alarm Jul 20 18:27:50 WARNING[2652]: Unable to disable echo cancellation on channel 17 Jul 20 18:27:50 WARNING[2652]: Detected alarm on channel 18: Red Alarm Jul 20 18:27:50 WARNING[2652]: Unable to disable echo cancellation on channel 18 Jul 20 18:27:50 WARNING[2652]: Detected alarm on channel 19: Red Alarm Jul 20 18:27:50 WARNING[2652]: Unable to disable echo cancellation on channel 19 Jul 20 18:27:50 WARNING[2652]: Detected alarm on channel 20: Red Alarm Jul 20 18:27:50 WARNING[2652]: Unable to disable echo cancellation on channel 20 Jul 20 18:27:50 WARNING[2652]: Detected alarm on channel 21: Red Alarm Jul 20 18:27:50 WARNING[2652]: Unable to disable echo cancellation on channel 21 Jul 20 18:27:50 WARNING[2652]: Detected alarm on channel 22: Red Alarm Jul 20 18:27:50 WARNING[2652]: Unable to disable echo cancellation on channel 22 Jul 20 18:27:50 WARNING[2652]: Detected alarm on channel 23: Red Alarm Jul 20 18:27:50 WARNING[2652]: Unable to disable echo cancellation on channel 23 Jul 20 18:27:50 NOTICE[2650]: PRI got event: Alarm (4) on Primary D-channel of span 1 Jul 20 18:27:50 WARNING[2650]: No D-channels available! Using Primary on channel anyway 24! Jul 20 18:27:59 WARNING[2650]: No D-channels available! Using Primary on channel anyway 24! But just to me safe, please check out my /procs and let me know if you see anything. Once again, I strongly believe this is a telco issue not Asterisk. [EMAIL PROTECTED]/0] # cat /proc/interrupts CPU0 0:90839XT-PIC timer 1:2XT-PIC keyboard 2:0XT-PIC cascade 10: 898130 XT-PIC t4xxp 12: 879XT-PIC eth0 14: 2155 XT-PIC ide0 NMI:0 ERR:0 Any to back my clams that asterisk is fine, I'm using the TE405P, with a different telco in my second span and it operates
Re: [Asterisk-Users] PRI got event: HDLC Abort (6) on Primary, D-channel of span 1
2 - Check your span line in your zaptel.conf. You should be receiving timing, not giving it, when using a PRI (generally). Change the second number from 1 to 0. Save and restart asterisk. (span=1,0,0,esf,b8zs) I think you've got this cocked-up. A 0 in the second position tells zaptel to internally-clock the circuit, and ingnore the clocking information from the provider. Why would you want to do that? ___ 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: [Asterisk-Users] PRI got event: HDLC Abort (6) on Primary D-channel of span 1
On Wed, 20 Jul 2005, Paul Belanger wrote: Any to back my clams that asterisk is fine, I'm using the TE405P, with a different telco in my second span and it operates fine!! What span is your clock source? A TE405P card can only operate in one clock domain at a time. I.e. the same clock will be used on all of them. If both providers are connected to the same TE405P card you will most likely have a problem with one of them unless they in turn have their clocks locked to a common source. Two differently clocked sources wil manifest themselves as the occasional bit slip. I am not sure if a bit slip can cause the problems on the D channel you are seeing. Peter ___ 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
[Asterisk-Users] PRI got event: HDLC Abort (6) on Primary, D-channel of span 1
I also experienced this problem and the first thing that really helped out was changing the timing in the span line of the zaptel.conf. Change it to look like this (see below) and see if it helps out. I got the error much less after doing this and eventually got rid of the error completely by removing my raid drives, installing an IDE drive, enabling DMA mode on the Hard Drive, enabling APCI in my kernel (also enabling my motherboard chipset in the kernel). After doing this I got 20x the Hard Drive write speed, no interrupts are shared, and the error is gone. span=1,0,0,esf,b8zs Message: 1 Date: Wed, 29 Jun 2005 07:13:29 -0600 From: Michael Blood [EMAIL PROTECTED] Subject: [Asterisk-Users] PRI got event: HDLC Abort (6) on Primary D-channel of span 1 To: asterisk-users@lists.digium.com Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=us-ascii I receive this error on the asterisk console and it is pretty much ALWAYS coming up. Sometimes there will be a break where it does not display. We had our PRI provider test the lines and they claim that there is no signalling problem. It doesn't matter if there are no calls or if there are 10 calls in progress the error is still displayed. I also get an annoying popping or clicking sound but that doesn't always correspond with this error coming up so it is likely a separate issue. I have loaded all modules by hand like below as someone suggested in a search for HDLC errors on the list. insmod zaptel insmod wct1xxp Unfortunately it did not help Has anyone run into this in the past? Michael ;zapata.conf switchtype=national context=incoming_eli_pri_1 signalling=pri_cpe group=1 channel = 1-11 bchan=1-11 dchan=24 ;zaptel.conf span=1,1,0,esf,b8zs bchan=1-11 dchan=24 Jun 29 07:09:07 NOTICE[3094]: chan_zap.c:7394 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Jun 29 07:09:07 NOTICE[3094]: chan_zap.c:7394 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Jun 29 07:09:07 NOTICE[3094]: chan_zap.c:7394 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 ___ 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
[Asterisk-Users] PRI got event: HDLC Abort (6) on Primary, D-channel of span 1
Hey Kevin,
I managed to resolve this error after a week of pulling out my hair.
Here is what I did to resolve the error and a link below for further assistance.
1 - If you are not using 2.6 kernel, upgrade.
2 - Check your span line in your zaptel.conf. You should be receiving timing,
not giving it, when using a PRI (generally). Change the second number from 1
to 0. Save and restart asterisk. (span=1,0,0,esf,b8zs)
3 - I had a SATA RAID ARRAY setup (RAID 5) because I thought, hey, I can have redundency so that I don't loose voicemail if a drive crashes. Sadly if you run anything other than an IDE Drive you cannot use DMA and the Digium cards rely heavily on DMA. So I was forced to take out my RAID Controller and SATA drives and install a nice high end 120 Gig IDE Drive.
4 - In you BIOS disable any on board devices that you can (i.e. scsi
controllers, usb controllers, serial controllers, etc...). If your BIOS
supports/has an APIC(Advanced Processor Interrupt Controller) (which most
modern motherboards do) go into your IRQ settings and set them all to the
default AUTO type option. (you'll see why further below).
5 - In your 2.6 kernel enable these options:
PROCESSOR TYPE AND FEATURES ---
[*] Local APIC support on uniprocessors
[*] IO-APIC support on uniprocessors
DEVICE DRIVERS ---
ATA/ATAPI/MFM/RLL support ---
[*] Generic PCI bus-master DMA support
[*] Use PCI DMA by default when available
* VIA82CXXX chipset support
- I CHOSE THE VIA82CXXX CHIPSET SUPPORT FOR MY MOTHERBOARD, CHOSE THE
APPROPRIATE ONE FOR YOUR MOTHERBOARD, THIS IS IMPORTANT IN USING DMA. THE APIC
IS GOING TO ASSIGN IRQS AND PREVENT SHARING, ALSO FREES UP MORE THAN 16 IRQ
LIMIT. SAVE THE CHANGES AND RECOMPILE YOUR KERNEL.
6 - run these commands to enable dma if it is not already on and enable irq
unmask
linux# hdparm -d1 /dev/hda
/dev/hda:
setting using_dma to 1 (on)
using_dma= 1 (on)
linux# hdparm -u1 /dev/hda
/dev/hda:
setting unmaskirq to 1 (on)
unmaskirq= 1 (on)
linux# hdparm /dev/hda shows info.
/dev/hda:
multcount= 16 (on)
IO_support = 1 (32-bit)
unmaskirq= 1 (on)
using_dma= 1 (on)
keepsettings = 0 (off)
readonly = 0 (off)
readahead= 256 (on)
geometry = 65535/16/63, sectors = 80026361856, start = 0
linux# hdparm -i /dev/hda shows more info.
/dev/hda:
Model=WDC WD800JB-00FMA0, FwRev=13.03G13, SerialNo=WD-WMAJ97238449
Config={ HardSect NotMFM HdSw15uSec SpinMotCtl Fixed DTR5Mbs FmtGapReq }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=58
BuffType=unknown, BuffSize=8192kB, MaxMultSect=16, MultSect=16
CurCHS=4047/16/255, CurSects=16511760, LBA=yes, LBAsects=156301488
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5
AdvancedPM=no WriteCache=enabled
Drive conforms to: device does not report version:
* signifies the current active mode
YOU CAN SEE ABOVE THAT UDMA5 MODE IS ACTIVE BY THE * NEXT TO IT.
7 - you can run hdparm -tT /dev/hda to get some benchmarks on your drive, mine
is running at:
/dev/hda:
Timing cached reads: 956 MB in 2.00 seconds = 477.59 MB/sec
Timing buffered disk reads: 126 MB in 3.03 seconds = 41.62 MB/sec
Which is literally 20 times faster than before I ran through these steps.
8 - Make absolutly positive that you are using the current most stable version
of asterisk.
9 - Lastly, if you are running any services that you can put on another machine
(i.e. TFTP, NTP) do so. Move them to another machine and try not to run any
services but what is absolutely necessary and asterisk.
This should take care of you but if you need more try the link below. When all
else fails, go to the digium supported hardware and change out your motherboard.
Fixing interrputs:
http://www.asteriskguru.com/tutorials/pci_irq_apic_tdm_ticks_te410p_te405p_noise.html
Message: 6
Date: Fri, 15 Jul 2005 20:13:48 -0400
From: Kevin [EMAIL PROTECTED]
Subject: [Asterisk-Users] PRI got event: HDLC Abort (6) on Primary
D-channel of span 1
To: 'Asterisk Users Mailing List - Non-Commercial Discussion'
asterisk-users@lists.digium.com
Message-ID: [EMAIL PROTECTED]
Content-Type: text/plain; charset=us-ascii
I am getting an error in the log on the PRI span. The error is :
PRI got event: HDLC Abort (6) on Primary D-channel of span 1
I thought the problem was an interrupt conflict with the T110P card, so
I changed out the server to one that will dedicate the interrupt to the
T110P card. I still have the problem.
It's a dell 800 server with an SATA drive.
Can anyone offer
[Asterisk-Users] PRI got event: HDLC Abort (6) on Primary D-channel of span 1
I am getting an error in the log on the PRI span. The error is : PRI got event: HDLC Abort (6) on Primary D-channel of span 1 I thought the problem was an interrupt conflict with the T110P card, so I changed out the server to one that will dedicate the interrupt to the T110P card. I still have the problem. It's a dell 800 server with an SATA drive. Can anyone offer and suggestions as any probable cause? Thanks ___ 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: [Asterisk-Users] PRI got event: HDLC Abort (6) on Primary D-channel of span 1
try removing asterisk modules you are not using, and non-asterisk services running on the machine, especially ones with high disk or network usage. Kevin wrote: I am getting an error in the log on the PRI span. The error is : PRI got event: HDLC Abort (6) on Primary D-channel of span 1 I thought the problem was an interrupt conflict with the T110P card, so I changed out the server to one that will dedicate the interrupt to the T110P card. I still have the problem. It's a dell 800 server with an SATA drive. Can anyone offer and suggestions as any probable cause? Thanks ___ 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 ___ 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: [Asterisk-Users] PRI got event: HDLC Abort (6) on Primary D-channel of span 1
Michael Blood wrote: I receive this error on the asterisk console and it is pretty much ALWAYS coming up. Sometimes there will be a break where it does not display. This happens when Asterisk receives corrupt data from the card. The most common cause of this is some device or driver locking interrupts for long enough to lose data coming in from the card. Common causes of this are graphics, raid, etc. If the problem only happens when accessing the disk, then you may have to tune your IDE settings using haparm (see google). Some IDE chipsets simply don't work with Digium cards because they lock interrupts for too long. We had this problem with a ServerWorks chipset. The only solution was to replace the motherboard with one from a different company. -- Eric Wieling * BTEL Consulting * 504-210-3699 x2120 ___ 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
[Asterisk-Users] PRI got event: HDLC Abort (6) on Primary D-channel of span 1
event: HDLC Abort (6) on Primary D-channel of span 1Jun 29 07:09:08 NOTICE[3094]: chan_zap.c:7394 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1Jun 29 07:09:08 NOTICE[3094]: chan_zap.c:7394 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1Jun 29 07:09:08 NOTICE[3094]: chan_zap.c:7394 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1Jun 29 07:09:08 NOTICE[3094]: chan_zap.c:7394 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1Jun 29 07:09:08 NOTICE[3094]: chan_zap.c:7394 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1Jun 29 07:09:08 NOTICE[3094]: chan_zap.c:7394 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1Jun 29 07:09:08 NOTICE[3094]: chan_zap.c:7394 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1Jun 29 07:09:08 NOTICE[3094]: chan_zap.c:7394 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1Jun 29 07:09:08 NOTICE[3094]: chan_zap.c:7394 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1Jun 29 07:09:08 NOTICE[3094]: chan_zap.c:7394 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1Jun 29 07:09:08 NOTICE[3094]: chan_zap.c:7394 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1Jun 29 07:09:08 NOTICE[3094]: chan_zap.c:7394 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 ___ 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: [Asterisk-Users] PRI got event: HDLC Abort (6) on Primary D-channel of span 1
pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Jun 29 07:09:08 NOTICE[3094]: chan_zap.c:7394 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Jun 29 07:09:08 NOTICE[3094]: chan_zap.c:7394 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Jun 29 07:09:08 NOTICE[3094]: chan_zap.c:7394 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Jun 29 07:09:08 NOTICE[3094]: chan_zap.c:7394 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Jun 29 07:09:08 NOTICE[3094]: chan_zap.c:7394 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Jun 29 07:09:08 NOTICE[3094]: chan_zap.c:7394 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Jun 29 07:09:08 NOTICE[3094]: chan_zap.c:7394 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Jun 29 07:09:08 NOTICE[3094]: chan_zap.c:7394 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Jun 29 07:09:08 NOTICE[3094]: chan_zap.c:7394 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Jun 29 07:09:08 NOTICE[3094]: chan_zap.c:7394 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Jun 29 07:09:08 NOTICE[3094]: chan_zap.c:7394 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Jun 29 07:09:08 NOTICE[3094]: chan_zap.c:7394 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Jun 29 07:09:08 NOTICE[3094]: chan_zap.c:7394 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Jun 29 07:09:08 NOTICE[3094]: chan_zap.c:7394 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 ___ 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 -- Tom ___ 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
