Hi
Related to this message:
http://lists.digium.com/pipermail/asterisk-users/2005-February/090205.html
After having a lot of trouble with abort and breakdown of the PRI connection I
finally figured out what was wrong:
The kernel was compiled for generic ide chipsets which doesn't support DMA.
W
tim panton wrote:
[..]
Good luck with it.
I think I am lucky! ;-)
We resolved the problem changing the Mother board to one with an Intel chipset.
The first one had Via chipset.
1) At first, we changed the mother board by another with Intel chipset. This one
can set udma2 (or udma3) from BIOS. It is
>
> 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 = 2344930
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 N
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 HdSw>15uSec Fixed D
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
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/lis
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 t
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?
Alex G Robertson wrote:
Some news.
It is not caused by transmission lines, conectors or a
This is happens because of imperfect HDLC code. I am having the same in
my logs, but quite rare
and on spans which is idle. Therefore this is not an issue with PRIs itself.
I may be wrong, but telco technician checked my PRIs as well, and didn't
find any flaws.
I can tell you more. IT happens wh
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 erro
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 NOT
12 matches
Mail list logo
