- Problem Statement:

    Dstop: Communication port A parity error

- Symptoms:

    'wfail' output reports something similar to the following:

       01  redxl> dumpf load dsmd.dstop.020508.1901.51
       02  Created Wed May  8 19:01:53 2002
       03  By hpost v. 1.2 Generic 112488-04 Mar 18 2002 14:43:00  executing as pid=12154
       04  On ssc name =  rasputin-sc0.SD_RASCAL.West.Sun.COM
       05  Domain =  0=A    Platform = rasputin
       06  Boards in dump: master SC    CPs/CSBs[1:0]: 3
       07            EXB[17:0]: 12100
       08          Slot0[17:0]: 12100
       09          Slot1[17:0]: 12100
       10  -D option, -d
       11  "DSMD DomainStop Dump"
       12  0 errors occurred while creating this dump.
       13  redxl> wfail
       14  SDI EX08/S0  Master_Stop_Status0[31:0] = D004000F
       15          MStop0[3:0]: All SDI logic is DStopped + Recordstopped.
       16  SDI EX08/S0  Dstop0[31:0] = 00118010
       17          Dstop0[16]: D    DARB texp requests all Dstop (M)
       18          Dstop0[20]: D 1E SDI internal sysreg port requested Dstop
       19  SDI EX08/S0  Sysreg_Error[31:0] = 00108010  Mask = 780377FF
       20          SRErr[20]: D 1E Communication port A parity error
       21              {coma_rdy,comap,coma[3:0]} = 10
       22  FAIL EXB EX8:  Dstop/Rstop detected by SDI EX8/S0.
       23  Primary service FRU is EXB EX8.
       24  SDI EX13/S0: All SDI is DStopped and RStopped,         requested by DARB.
       25  SDI EX16/S0: All SDI is DStopped and RStopped,         requested by DARB.
       26  DARB C0: enabled ports (expanders)          [17:0]: 16100
       27  DARB C0: other darb req Dstop+Rstop for exps[17:0]: 00100
       28  DARB C1: enabled ports (expanders)          [17:0]: 16100
       29  DARB C1: other darb req Dstop+Rstop for exps[17:0]: 00100


      

- Troubleshooting:

    The dump header tells us that this Dstop was generated by dsmd (lines 10,11) 
    while a domain was active. This is also evident by the dumpf file name - 
    dsmd.dstop files are created by dsmd as part of an ASR. Walking the
    error chain:

     - Master SDI on EX8 calls for Dstop as directed by itself (line 18)
     - Master SDI on EX8 reports a parity error in the SRErr0 register (lines 20)
     - EX8 is FAILed from the configuration and named as a primary FRU (lines 22,23)

    The SRErr register records errors dealing with AXQ System Register reads. At
    a certain point in the transaction, the master SDI feeds data to the slaves 
    using communication ports (A and B), which is a parity protected pathway.  The 
    pathway used between the Master SDI and slaves is completely contained within 
    the expander.    

- Resolution:

    Repair/replace EX8.
        

- Summary of part number and patch ID's 

    http://infoserver.central.sun.com/data/syshbk/Systems/SunFire15K/component.centerplane.html      
        
- References and bug IDs

    Knowledge Article 48122 
    SDI ASIC Specification     

- Additional background information:

        
        
- Meta-Data/Problem categorization:

Product/Platform: SF12K/SF15K
Category:

- Keywords

15K, 12K, SF15K, SF12K, Sun Fire 15K, Enterprise, Server, Sun Fire 12K,
starcat, dstop, Communication port A parity error