•  
Home » Developer Group » Dialogic SS7 and SIGTRAN Signalling » error ss7MD Resetting board: board 0 not reset correctly
..

error ss7MD Resetting board: board 0 not reset correctly

..

Developer Group

Developer Group
Connect with thousands of other developers to brainstorm ideas, share best practices and tips - or just chat about the latest emerging technologies making noise in the field. And of course, get the most up-to-date service and support news from Dialogic.
Options
Details
  • 13 replies
  • 1 subscriber
  • Postedover 4 years ago
Dialogic SS7 and SIGTRAN Signalling

error ss7MD Resetting board: board 0 not reset correctly

  • g_sezhian@thuraya.com
    Posted by
    on 20 Aug 2015 12:56 PM

    Hi

      Im getting the below error while starting the Dialogic Board, Please Guide

    S7L:I0000 M t0008 i0000 f20 ddf sd6
    Resetting board: board 0 not reset correctly
    S7MGT: FAILED
    S7L:I0000 M t06a0 i0000 f20 def s62 p001000d6

    Can you guide in solving this.

    ********************************************************************************
    *
    * Example System Configuration File (example_system.txt) for use with
    * the DSI Development Package.
    *
    * Edit this file to reflect your configuration.
    *
    ********************************************************************************
    *
    * Essential modules running on host:
    *
    LOCAL 0x20 * ssds/ssdh/ssdm - Board interface task
    LOCAL 0x00 * tim - Timer task
    *
    * Optional modules running on the host:
    *
    LOCAL 0xcf * s7_mgt - Management/config task
    LOCAL 0xef * s7_log - Display and logging utility
    *LOCAL 0x2d * upe - Example user part task
    LOCAL 0x1d * userapp
    LOCAL 0x3d * s7_play


    *
    * Modules that optionally run on the host:
    *
    LOCAL 0x22 * MTP3 module (and SS7LD 'mtp' and 'isup' run-mode)
    LOCAL 0x23 * ISUP module (and SS7LD 'isup' run-mode)
    * LOCAL 0x4a * TUP module
    * LOCAL 0x33 * SCCP module
    * LOCAL 0x14 * TCAP module
    * LOCAL 0x15 * MAP module
    * LOCAL 0x25 * IS41 module
    * LOCAL 0x35 * INAP module
    *
    * Essential modules running on the board (all redirected via ssd):
    *
    REDIRECT 0x71 0x20 * MTP2 module (except SS7HD boards)
    * REDIRECT 0x81 0x20 * MTP2 module_id for SP 0 (SS7HD boards only)
    * REDIRECT 0x91 0x20 * MTP2 module_id for SP 1 (SS7HD boards only)
    * REDIRECT 0xe1 0x20 * MTP2 module_id for SP 2 (SS7HD boards only)
    * REDIRECT 0xf1 0x20 * MTP2 module_id for SP 3 (SS7HD boards only)
    REDIRECT 0x10 0x20 * CT bus/Clocking control module
    REDIRECT 0x8e 0x20 * On-board management module
    *
    * Modules that optionally run on the board (all redirected via ssd):
    *
    * REDIRECT 0x22 0x20 * MTP3 module (except for SS7LD 'mtp' and 'isup' run modes)
    * REDIRECT 0x23 0x20 * ISUP module (except for SS7LD 'mtp' and 'isup' run modes)
    * REDIRECT 0x4a 0x20 * TUP module
    * REDIRECT 0x33 0x20 * SCCP module
    * REDIRECT 0x14 0x20 * TCAP module
    * REDIRECT 0x15 0x20 * MAP module
    * REDIRECT 0x25 0x20 * IS41 module
    * REDIRECT 0x35 0x20 * INAP module
    *
    *
    * SS7MD boards only:
    * REDIRECT 0x31 0x20 * ATM Module
    * REDIRECT 0x41 0x20 * Q.SAAL Module
    * REDIRECT 0x61 0x20 * Signalling Driver Module

    *
    *
    * INAP parameters:
    *
    * Configure INAP
    * INAP_CONFIG <options>
    * INAP_CONFIG 2
    *
    * Configure INAP Functional Entities
    * INAP_FE <fe_ref> <options> <sccp_address>
    * INAP_FE 0x00000007 0x0000000f 0x00000000
    *
    * Configure INAP Application Context
    * INAP_AC <ac_ref> <ac>
    * INAP_AC 0x00 0xa109060704000101010000
    *
    * Configure INAP Trace
    * INAP_TRACE <op_evt_mask> <ip_evt_mask> <non_prim_mask>
    * INAP_TRACE 0xf 0xf 0x7f
    *
    *
    * IS41 parameters:
    *
    * Configure IS41 TRACE
    * IS41_TRACE <op_evt_mask> <ip_evt_mask> <non_prim_mask>
    * IS41_TRACE 0xf 0xf 0xff
    *
    ********************************************************************************
    MTP_TRACE 0x20 2 0

    ISUP_TRACE 1 1 4
  • g_sezhian@thuraya.com
    Posted by
    on 21 Aug 2015 2:27 PM

    Hi Guys Please guide me in Fixing this.
  • franck@modulo
    Posted by
    on 21 Aug 2015 2:42 PM

    1/ did you build an install the driver for it?

    2/ share gctload -d output if answer to 1/ is yes
  • g_sezhian@thuraya.com
    Posted by
    on 23 Aug 2015 7:38 AM

    Hi

    Below is the output from gctload and dmesg.

    ---------------gctload------------------------------------------------------

    [root@callproxy1 DSI]# ./gctload -d

    Reading from system configuration file: 'system.txt'

    Created LOCAL module Id 0x20

    Created LOCAL module Id 0x0

    Created LOCAL module Id 0xcf

    Created LOCAL module Id 0xef

    Created LOCAL module Id 0x1d

    Created LOCAL module Id 0x3d

    Created LOCAL module Id 0x22

    Created LOCAL module Id 0x23

    Redirect module Id 0x71 to module Id 0x20

    Redirect module Id 0x10 to module Id 0x20

    Redirect module Id 0x8e to module Id 0x20

    Redirect module Id 0xdf to module Id 0xef

    (15707)gctload: Verification started.

    (15707)gctload: Verification complete.

    (15707)gctload: Process (15708)'./ssdm' - forked by gctload

    (15707)gctload: Process (15709)'./tim' - forked by gctload

    (15707)gctload: Process (15710)'./tick' - forked by gctload

    (15707)gctload: Process (15711)'./s7_mgt' - forked by gctload

    (15707)gctload: Process (15712)'./HSTBIN/mtp3' - forked by gctload

    (15707)gctload: Process (15713)'./HSTBIN/isup' - forked by gctload

    (15707)gctload: Process (15714)'./s7_log' - forked by gctload

    (15707)gctload: Initialisation complete.

    SS7 MTP3 started in trial mode.

    This binary will terminate after 1 hour.

    SS7 ISUP started in trial mode.

    This binary will terminate after 1 hour.

    S7_log : mod ID=0xef, options=0xaf0d, max_param_len=320

    S7_log : Writing log file /appl/deploy/logs/log_ss7.txt

    S7_MGT Tx: M-I0000-t7680-i0000-fcf-d20-s00-r8000-p200000cf70637337332e6463310000000000000000000008

    SS7 ssdm started in trial mode.

    This binary will terminate after one hour.

    S7_MGT Rx: M-I0000-t3680-i0000-f20-dcf-s00-r0000-p200000cf70637337332e6463310000000000000000000008

    S7_MGT Tx: M-I0000-t7681-i0000-fcf-d20-s00-r8000-p0010000000002e2f44432f7373372e6463360000000000000022

    S7_MGT Rx: M-I0000-t3681-i0000-f20-dcf-s00-r0000-p0010000000002e2f44432f7373372e6463360000000000000022

    S7_MGT Rx: M-I0000-t06a0-i0000-f20-dcf-s62-r0000-p001000d6

    S7L:I0000 M t0008 i0000 f20 ddf sd6

    S7_MGT Tx: M-I0000-t06a0-i0000-f20-def-s62-r0000-p001000d6

    SSD - board[0] - SSDSI_FAILURE

    S7MGT: FAILED

    S7L:I0000 M t06a0 i0000 f20 def s62 p001000d6

    S7L:I0000 Environment: Congestion (0)

    -----------------------------------------dmesg---------------------------------------------------------

    [root@callproxy1 DSI]# dmesg | tail -30

    ->[iph_detach_device] detaching device ss7md0 - detach 6

    ->ss7md [iph_detach_device]: disable interrupt

    DSI SS7MD Release 6.6.16 (Build 1221)

    Part of the Dialogic(R) DSI Development Package for Linux

    Copyright (C) Dialogic Corporation 2008-2014. All Rights Reserved.

    Interphase iphwae 0000:0b:00.0: setting latency timer to 64

    DSI SS7MD Release 6.6.16 (Build 1221)

    Part of the Dialogic(R) DSI Development Package for Linux

    Copyright (C) Dialogic Corporation 2008-2014. All Rights Reserved.

    ->[iph_attach] device 0 ended reset (0)

    ->[iph_attach] device 0: BER=0x80040035

    ss7md : found card 0 - type 0x90e5 - SN PX801188

            type 0x90e5 => 5639L quad T1/E1/J1

    ResetBoard for dev 0

    ->Restoring the PCI configuration register for dev 0  ...

    ->ss7md : adapter 0 successfully loaded

    ss7md: !!! WATCHDOG on device 0 => the card needs to be reset

    ss7md: WatchdogTimeout 0

    ss7md: HostToCardSigCount 3 - HostToCardEchoCount -1

    ss7md[iMonitor] CodeReady device 0 - Value=52445921

    ssdm[15685]: segfault at 8750664 ip 000000000804b1c5 sp 00000000f7588290 error 4 in ssdm[8048000+e8000]

    ResetBoard for dev 0

    ->Restoring the PCI configuration register for dev 0  ...

    ->ss7md : adapter 0 successfully loaded

    ss7md: !!! WATCHDOG on device 0 => the card needs to be reset

    ss7md: WatchdogTimeout 0

    ss7md: HostToCardSigCount 3 - HostToCardEchoCount -1

    ss7md[iMonitor] CodeReady device 0 - Value=52445921

    ssdm[15717]: segfault at 8750664 ip 000000000804b1c5 sp 00000000f760b290 error 4 in ssdm[8048000+e8000]
  • g_sezhian@thuraya.com
    Posted by
    on 23 Aug 2015 7:56 AM

    Addition info

    Hardware: HP DL380 Gen9

    OS: Centos 6.5/6.6 x86_64 bit
  • g_sezhian@thuraya.com
    Posted by
    on 23 Aug 2015 8:40 AM

    Below is from /var/logs/messages/

    Aug 23 03:33:01 call1 rsyslogd: [origin software="rsyslogd" swVersion="5.8.10" x-pid="1564" x-info="http://www.rsyslog.com"] rsyslogd was HUPed
    Aug 23 10:25:24 call1 kernel: ->iph_detach for dev 73e05000 - index 0 - Dev=73e05000 - iDev=73e04000
    Aug 23 10:25:24 call1 kernel: ->[iph_detach_device] detaching device ss7md0 - detach 6
    Aug 23 10:25:24 call1 kernel: ->[iph_detach_device] detach delayed
    Aug 23 10:25:24 call1 kernel: ->iph_detach for dev 73e04000 - index 0 - Dev=73e05000 - iDev=73e04000
    Aug 23 10:25:24 call1 kernel: ->[iph_detach_device] detaching device ss7md0 - detach 6
    Aug 23 10:25:24 call1 kernel: ->ss7md [iph_detach_device]: disable interrupt
    Aug 23 10:25:24 call1 kernel:
    Aug 23 10:33:00 call1 kernel: DSI SS7MD Release 6.6.16 (Build 1221)
    Aug 23 10:33:00 call1 kernel: Part of the Dialogic(R) DSI Development Package for Linux
    Aug 23 10:33:00 call1 kernel: Copyright (C) Dialogic Corporation 2008-2014. All Rights Reserved.
    Aug 23 10:33:00 call1 kernel: DSI SS7MD Release 6.6.16 (Build 1221)
    Aug 23 10:33:00 call1 kernel: Part of the Dialogic(R) DSI Development Package for Linux
    Aug 23 10:33:00 call1 kernel: Copyright (C) Dialogic Corporation 2008-2014. All Rights Reserved.
    Aug 23 10:33:00 call1 kernel: ->[iph_attach] device 0 ended reset (0)
    Aug 23 10:33:01 call1 kernel: ->[iph_attach] device 0: BER=0x80040035
    Aug 23 10:33:01 call1 kernel: ss7md : found card 0 - type 0x90e5 - SN PX801188
    Aug 23 10:33:01 call1 kernel: type 0x90e5 => 5639L quad T1/E1/J1
    Aug 23 10:33:40 call1 kernel: ResetBoard for dev 0
    Aug 23 10:33:44 call1 kernel: ->Restoring the PCI configuration register for dev 0 ...
    Aug 23 10:34:20 call1 kernel: ->ss7md : adapter 0 successfully loaded
    Aug 23 10:34:22 call1 kernel: ss7md: !!! WATCHDOG on device 0 => the card needs to be reset
    Aug 23 10:34:22 call1 kernel: ss7md: WatchdogTimeout 0
    Aug 23 10:34:22 call1 kernel: ss7md: HostToCardSigCount 3 - HostToCardEchoCount -1
    Aug 23 10:34:22 call1 kernel: ss7md[iMonitor] CodeReady device 0 - Value=52445921
    Aug 23 10:34:22 call1 kernel: ssdm[15685]: segfault at 8750664 ip 000000000804b1c5 sp 00000000f7588290 error 4 in ssdm[8048000+e8000]
    Aug 23 10:39:40 call1 kernel: ResetBoard for dev 0
    Aug 23 10:39:43 call1 kernel: ->Restoring the PCI configuration register for dev 0 ...
    Aug 23 10:40:20 call1 kernel: ->ss7md : adapter 0 successfully loaded
    Aug 23 10:40:21 call1 kernel: ss7md: !!! WATCHDOG on device 0 => the card needs to be reset
    Aug 23 10:40:21 call1 kernel: ss7md: WatchdogTimeout 0
    Aug 23 10:40:21 call1 kernel: ss7md: HostToCardSigCount 3 - HostToCardEchoCount -1
    Aug 23 10:40:21 call1 kernel: ss7md[iMonitor] CodeReady device 0 - Value=52445921
    Aug 23 10:40:22 call1 kernel: ssdm[15717]: segfault at 8750664 ip 000000000804b1c5 sp 00000000f760b290 error 4 in ssdm[8048000+e8000]
    Aug 23 11:42:45 call1 kernel: ResetBoard for dev 0
    Aug 23 11:42:49 call1 kernel: ->Restoring the PCI configuration register for dev 0 ...
    Aug 23 11:43:26 call1 kernel: ->ss7md : adapter 0 successfully loaded
    Aug 23 11:43:27 call1 kernel: ss7md: !!! WATCHDOG on device 0 => the card needs to be reset
    Aug 23 11:43:27 call1 kernel: ss7md: WatchdogTimeout 0
    Aug 23 11:43:27 call1 kernel: ss7md: HostToCardSigCount 3 - HostToCardEchoCount -1
    Aug 23 11:43:27 call1 kernel: ss7md[iMonitor] CodeReady device 0 - Value=52445921
    Aug 23 11:43:28 call1 kernel: ssdm[15765]: segfault at 8750664 ip 000000000804b1c5 sp 00000000f7614290 error 4 in ssdm[8048000+e8000]
  • g_sezhian@thuraya.com
    Posted by
    on 23 Aug 2015 9:21 AM

    Yes we have built and installed it using ss7MDDriver directory contents.
  • franck@modulo
    Posted by
    on 24 Aug 2015 5:51 AM

    well

    S7_MGT Tx: M-I0000-t06a0-i0000-f20-def-s62-r0000-p001000d6

    reports a board failure

    so, one of the two:

    1/ the board is defective, check it on another machine.

    2/ the driver is not build correctly or is not compatible with your OS.

    what OS are you deploying?
  • g_sezhian@thuraya.com
    Posted by
    on 24 Aug 2015 6:24 AM

    Thanks . I have checked the Board in another machine . It appears fine.

    Hardware: HP DL380 Gen9

    OS: Centos 6.5/6.6 x86_64 bit

    We followed the procedure to build the driver. But I have a doubt that we may have missed?
  • franck@modulo
    Posted by
    on 24 Aug 2015 6:26 AM

    i guess you need then to go through it with the support team.
  • g_sezhian@thuraya.com
    Posted by
    on 24 Aug 2015 6:33 AM

    Yes . Thanks . Another way to hack this?.I tried to copy the driver file from other machine to this ..till facing the same issue.
  • franck@modulo
    Posted by
    on 24 Aug 2015 6:36 AM

    the other machine is the same hw/same sw?
  • g_sezhian@thuraya.com
    Posted by
    on 24 Aug 2015 6:38 AM

    No it has different Hardware and Software Versions. The one failing is a New server from HP. We checked with dialogic before purchase, they replied PCIx must be enough.
  • harish
    Posted by
    on 24 Aug 2015 9:13 AM

    Hi G_S,

    Hope after the patch, issue is solved.

    Regards