[asterisk-bugs] [JIRA] (DAHLIN-336) Dell R720 keeps rebooting on DAHDI red alarm.

Russ Meyerriecks (JIRA) noreply at issues.asterisk.org
Mon Mar 24 13:33:19 CDT 2014


    [ https://issues.asterisk.org/jira/browse/DAHLIN-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=216776#comment-216776 ] 

Russ Meyerriecks commented on DAHLIN-336:
-----------------------------------------

Antonio,
  I'm just trying to help you get the quickest support possible. If your system is giving you "fatal bus errors" and rebooting, your problem is highly likely to be hardware related. In the less likely scenario that your card's driver is the problem, we still couldn't help you because Sangoma provides their own drivers for their own hardware. On the even more unlikely scenario that openr2 has a bug, we still couldn't provide support here, because openr2 is not maintained here either.

  So your best bet is to contact Sangoma's tech support for this one. If you're able to show that this is a bug in the core of dahdi, I would be happy to re-open the case and investigate further.

> Dell R720 keeps rebooting on DAHDI red alarm.
> ---------------------------------------------
>
>                 Key: DAHLIN-336
>                 URL: https://issues.asterisk.org/jira/browse/DAHLIN-336
>             Project: DAHDI-Linux
>          Issue Type: Bug
>      Security Level: None
>          Components: dahdi (the module)
>         Environment: ----------------------------------------------------------------------------------------------
> Hardware
> Chassis Model              : PowerEdge R720
> Processor Brand            : Intel(R) Xeon(R) CPU E5-2620 0 @ 2.00GHz
> Memory Total Installed Capacity   : 16384  MB
> ----------------------------------------------------------------------------------------------
> [ 07:04.0 Network controller: Sangoma Technologies Corp. A200/Remora FXO/FXS Analog AFT card ]
> Slot PCI7
> Adapter                    : A200/Remora FXO/FXS Analog AFT card
> Type                       : PCI E Gen 3 X16
> Data Bus Width             : 8x or x8
> Speed                      : [Not Obtained, see card documentation]
> Slot Length                : Long
> Voltage Supply             : 3.3 Volts
> -------------------------------
> | Wanpipe Hardware Probe Info |
> -------------------------------
> 1 . AFT-A101-SH : SLOT=4 : BUS=5 : IRQ=15 : CPU=A : PORT=1 : HWEC=32 : V=39
> ----------------------------------------------------------------------------------------------
> Software
> Debian 6 (Squeeze)
> Asterisk 1.8.23.1
> OpenR2 version: 1.3.3, revision: (release)
> WANPIPE Release: 7.0.5
> DAHDI Version: 2.7.0.1 Echo Canceller: HWEC
> ----------------------------------------------------------------------------------------------
>            Reporter: Antonio Castaneda
>            Assignee: Russ Meyerriecks
>            Severity: Critical
>              Labels: asterisk, crash
>
> Hello everyone.
> I am running Asterisk on the hardware / software platforms described above in 3 different branches of the company I work for. One server per office, all of them pretty much alike regarding hardware and software configuration.
> This started a few months ago, every server keeps alarming and showing this log message:
> Severity      : Critical
> Date and Time : Mon Mar 24 09:02:21 2014
> Description   : A bus fatal error was detected on a component at slot 5.
> This is referring to the slot where Sangoma Card is installed. It gets worse when one of the server keeps rebooting almost 2 times per day due to this, which is dangerous and worktime loss.
> I also provide here my MFC/R2 and DADHDI configuration and below the logs regarding the errors just before the server rebooted.
> I look forward to your helpful comments or further questions.
> Thank you in advance
> Best regards.
> CONFIGURATION FILES:
> --- /etc/dahdi/system.conf
> loadzone=us
> defaultzone=us
> span=1,1,0,cas,hdb3
> cas=1-15:1101
> dchan=16
> cas=17-31:1101
> echocanceller=mg2,1-15,17-31
> --- /etc/asterisk/chan_dahdi.conf
> [channels]
> context=default
> usecallerid=yes
> hidecallerid=no
> callwaiting=yes
> usecallingpres=yes
> callwaitingcallerid=yes
> threewaycalling=yes
> transfer=yes
> canpark=yes
> cancallforward=yes
> callreturn=yes
> echocancel=yes
> echocancelwhenbridged=yes
> relaxdtmf=yes
> rxgain=0.0
> txgain=0.0
> group=1
> callgroup=1
> pickupgroup=1
> immediate=no
> callerid=asreceived
> cidsignalling=dtmf
> cidstart=ring
> switchtype=national
> context=incalls
> group=0
> echocancel=yes
> signalling=mfcr2
> mfcr2_variant=mx
> mfcr2_get_ani_first=no
> mfcr2_max_ani=10
> mfcr2_max_dnis=4
> mfcr2_category=national_subscriber
> mfcr2_mfback_timeout=-1
> mfcr2_metering_pulse_timeout=-1
> mfcr2_call_files=yes
> mfcr2_logdir=log
> mfcr2_logging=all
> channel => 1-10



--
This message was sent by Atlassian JIRA
(v6.2#6252)



More information about the asterisk-bugs mailing list