Service manual

Power-Up 2-35
The SCM formats and prints SROM and XSROM errors found during power-up
or when executing the diagnostics in user mode. Example 2–3 shows examples
of two formats for SROM/XSROM failures.
The error format is identified:
1 = expected/received
2 = parameters
3 = unexpected exception
Severity: possible results are: hard, soft, machine check, fault, or
unexpected interrupt
QBB in which the error occurred
CPU that was executing code at the time the error occurred
Type of Error = SROM or XSROM
Test # = hex number of the test running at the time of the error
Error # = the specific error identifying the diagnostic subtest (see Appendix
C)
Possible FRU(s) and the possible component on that FRU ordered from
most likely to least likely
Values of specific parameters the diagnostic test uses (see Appendix C for
definitions of parameters related to the specific test and sub-test)
Example 1 shows a QSD CPUx_SCRATCH CSR Read/Write Test failure. A
bit in the data path is not correct. The parameters in this format are: expected
data, received data, and the address where the error occurred. In this case the
error points to the QSD3 ASIC on QBB0. Diagnostic error FRU1 callouts are
the ones used by the SCM to determine what resource to drop from the system
as it is powering up. In this case QBB0 would be dropped from the system.
Example 2 shows a local memory BIST check test failure on MEM0. Appendix
C shows error number 100f of test 25 to be a multi-bit error on MEM0. The
callout of DIMMs is J2, J3, and J4. The parameters are also defined in
Appendix C. Diagnostic error FRU1 callouts are the ones used by the SCM to
determine what resource to drop from the system as it is powering up. In this
case the memory array with the failing DIMM would be mapped out of the
system.