SRDB ID |
|
Synopsis |
|
Date |
48488 |
|
Sun Fire[TM] 12K/15K: Dstop: Data parity error detected by SDC on Slot0 |
|
1 Nov 2002 |
- Problem Statement:
Dstop: Data parity error detected by SDC on Slot0
- Symptoms:
'wfail' output reports something similar to the following:
01 redxl> dumpf load dsmd.dstop.020510.2017.20
02 Created Fri May 10 20:17:22 2002
03 By hpost v. 1.2 Generic 112488-04 Mar 18 2002 14:43:00 executing as pid=7416
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] = 600400CF
15 MStop0[3:0]: All SDI logic is DStopped + Recordstopped.
16 SDI EX08/S0 Dstop0[31:0] = 34018400
17 Dstop0[16]: D DARB texp requests all Dstop (M)
18 Dstop0[26]: D 1E AXQ requests Slot0 Dstop (M)
19 Dstop0[28]: D Slot0 asserted Error, enabled to cause Dstop (M)
20 Dstop0[29]: D Slot1 asserted Error, enabled to cause Dstop (M)
21 AXQ EX08 ( 8) Error_Flag_00[31:0] = 00808080 Mask = 0000FFFF
22 Err0[23]: D 1E AXQ Data parity error detected by SDC on Slot0
23 FAIL Slot SB8: Dstop/Rstop detected by AXQ.
24 Primary service FRU is Slot SB8.
25 Secondary service FRU is EXB EX8.
26 SDI EX13/S0: All SDI is DStopped and RStopped, requested by DARB.
27 SDI EX16/S0: All SDI is DStopped and RStopped, requested by DARB.
28 DARB C0: enabled ports (expanders) [17:0]: 16100
29 DARB C0: other darb req Dstop+Rstop for exps[17:0]: 00100
30 DARB C1: enabled ports (expanders) [17:0]: 16100
31 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 AXQ8 (line 18)
- AXQ8 reports the SDC detected a parity error on SB8 (line 22)
- SB8 is FAILed out of the configuration (line 23)
- SB8 and EX8 are named as the primary and secondary FRUs (line 24,25)
The SDC and AXQ communicate via bidirectional signals to exchange
TTransID and TargID information. Even parity is generated by the SDC
two cycles after data arrives at the SDC. This parity bit is sent to
the AXQ once generated. In this example, the SDC indicated a parity
error occurred on data sent by the AXQ (line 22).
The pathway between the AXQ and the SDC encountered a parity error. The
pathway crosses the interconnect between the system board and the expander,
so an individual FRU cannot be uniquely identified. Either the SB or
the EX may be at fault.
- Resolution:
Replace SB8. If errors persist, replace EX8.
- 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
http://infoserver.central.sun.com/data/syshbk/Systems/SunFire15K/component.centerplane.html
- References and bug IDs
SunSolve Article 48122
- Additional background information:
None
- Meta-Data/Problem categorization:
Product/Platform: SF12K/SF15K
Category:
- Keywords
15K, 12K, SF15K, SF12K, Sun Fire 15K, Enterprise, Server, Sun Fire 12K,
starcat, dstop, Data parity error detected by SDC on Slot0
INTERNAL SUMMARY:
SUBMITTER: Scott Davenport
APPLIES TO: Hardware/Sun Fire /15000, Hardware/Sun Fire /12000
ATTACHMENTS:
Copyright (c) 1997-2003 Sun Microsystems, Inc.