| SRDB ID | Synopsis | Date | ||
| 48195 | Sun Fire[TM] 12K/15K: Dstop: Control parity error from SDC | 31 Oct 2002 |
| Status | Issued |
| Description |
- Problem Statement:
Dstop: Control parity error from SDC
- Symptoms:
'wfail' output reports something similar to the following:
01 redxl> dumpf load dsmd.dstop.020423.1029.47
02 Created Tue Apr 23 10:29:48 2002
03 By hpost v. 1.2 Generic 112488-03 Feb 15 2002 13:40:50 executing as pid=8599
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]: 10108
08 Slot0[17:0]: 10108
09 Slot1[17:0]: 10108
00 -D option, -d
11 "DSMD DomainStop Dump"
12 0 errors occurred while creating this dump.
13 redxl> wfail
14 SDI EX03/S0: All SDI is DStopped and RStopped, requested by DARB.
15 SDI EX08/S0 Master_Stop_Status0[31:0] = 8004004F
16 MStop0[3:0]: All SDI logic is DStopped + Recordstopped.
17 SDI EX08/S0 Dstop0[31:0] = 10019000
18 Dstop0[16]: D DARB texp requests all Dstop (M)
19 Dstop0[28]: D 1E Slot0 asserted Error, enabled to cause Dstop (M)
10 EPLD SB08 Err1_Dom0: Mask= 00 Err= 0C 1stErr= 0C
21 Err1[2]: 1E+ Error reported by DX0
22 Err1[3]: 1E+ Error reported by DX1
23 DX SB08/DX0 Gen_Err[31:0] = 00018001
24 GErr[ 0,16]: 1E+ Control parity error from SDC
25 FAIL Slot SB8: Dstop detected by DX SB8/DX0.
26 Primary service FRU is Slot SB8.
27 DX SB08/DX1 Gen_Err[31:0] = 00018001
28 GErr[ 0,16]: 1E+ Control parity error from SDC
29 FAIL Slot SB8: Dstop detected by DX SB8/DX1.
30 Primary service FRU is Slot SB8.
31 SDI EX16/S0: All SDI is DStopped and RStopped, requested by DARB.
32 DARB C0: enabled ports (expanders) [17:0]: 14108
33 DARB C0: other darb req Dstop+Rstop for exps[17:0]: 00100
34 DARB C1: enabled ports (expanders) [17:0]: 14108
35 DARB C1: other darb req Dstop+Rstop for exps[17:0]: 00100
SOLUTION SUMMARY:
- 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 dump file name -
dsmd.dstop files are created by dsmd as part of an ASR. Walking the
error chain:
- The SDI on EX8 calls for Dstop as directed by its Slot 0 board, SB8 (line 19)
- The EPLD on SB8 indicates the DX0 and DX1 asserted error (line 21,22)
- DX0 and DX1 both report a parity error from the SDC (lines 23,24,27,28)
- SB8 is FAILed out and named the FRU (lines 25,29,30)
The SDC sends control data to the DXs for data routing. In this case, DX0 and
DX1 in SB8 detected a parity error on those signals from the SDC. The
pathway for these signals is entirely contained within the system board.
- Resolution:
Repair/replace SB8.
For the general case, replace the Slot 0/1 board whose DXs report this error.
- Summary of part number and patch ID's
http://infoserver.central.sun.com/data/syshbk/Devices/System_Board/SYSBD_SunFire_USIIICu.html
http://infoserver.central.sun.com/data/syshbk/Devices/I_O/IO_SunFire_15K_hsPCI_IO_Board.html
- References and bug IDs
SunSolve Article 48122
- Additional background information
- Meta-Data/Problem categorization:
Product/Platform: SF12K/SF15K
Category:
- Keywords
15K, 12K, SF15K, SF12K, starcat, dstop, Control parity error from SDC INTERNAL SUMMARY:
SUBMITTER: Scott Davenport APPLIES TO: Hardware/Sun Fire /15000, Hardware/Sun Fire /12000 ATTACHMENTS: