summaryrefslogtreecommitdiffstats
path: root/src/usr/hwpf/hwp/proc_sbe_errors/sbe_common_halt_codes.xml
blob: f601304d819f9db4c9b5fa6de6f555258fe73385 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
<!-- IBM_PROLOG_BEGIN_TAG                                                   -->
<!-- This is an automatically generated prolog.                             -->
<!--                                                                        -->
<!-- $Source: src/usr/hwpf/hwp/proc_sbe_errors/sbe_common_halt_codes.xml $  -->
<!--                                                                        -->
<!-- IBM CONFIDENTIAL                                                       -->
<!--                                                                        -->
<!-- COPYRIGHT International Business Machines Corp. 2014                   -->
<!--                                                                        -->
<!-- p1                                                                     -->
<!--                                                                        -->
<!-- Object Code Only (OCO) source materials                                -->
<!-- Licensed Internal Code Source Materials                                -->
<!-- IBM HostBoot Licensed Internal Code                                    -->
<!--                                                                        -->
<!-- The source code for this program is not published or otherwise         -->
<!-- divested of its trade secrets, irrespective of what has been           -->
<!-- deposited with the U.S. Copyright Office.                              -->
<!--                                                                        -->
<!-- Origin: 30                                                             -->
<!--                                                                        -->
<!-- IBM_PROLOG_END_TAG                                                     -->
<!-- $Id: sbe_common_halt_codes.xml,v 1.5 2013/06/21 22:57:28 jeshua Exp $ -->
<!-- Halt codes for proc_sbe_* procedures common to P8 and Centaur -->
<hwpErrors>
  <!-- ******************************************************************** -->
  <!-- ** Generic halt codes                                                -->
  <!-- ******************************************************************** -->
  <hwpError>
    <rc>RC_SBE_SUCCESS</rc>
    <description>
      This halt code does not represent an error; This is the code associated
      with the normal successful completion of an IPL by an SBE istep
      procedure.
    </description>
    <!-- JDS TODO - this FFDC should probably only log the target engine -->
    <collectRegisterFfdc>
      <id>REG_FFDC_PROC_STATUS_AND_SBE_VITAL_REGISTERS</id>
      <id>REG_FFDC_PROC_SBE_REGISTERS</id>
      <id>REG_FFDC_PROC_SLW_REGISTERS</id>
      <target>CHIP_IN_ERROR</target>
    </collectRegisterFfdc>
    <sbeError/>
  </hwpError>
  <!-- ******************************************************************** -->
  <hwpError>
    <rc>RC_SBE_SUCCESS_SLAVE_CHIP</rc>
    <description>
      This halt code does not represent an error; This is the code associated
      with the normal successful completion of an IPL by an SBE istep
      procedure on a slave chip.
    </description>
    <!-- JDS TODO - this FFDC should probably only log the target engine -->
    <collectRegisterFfdc>
      <id>REG_FFDC_PROC_STATUS_AND_SBE_VITAL_REGISTERS</id>
      <id>REG_FFDC_PROC_SBE_REGISTERS</id>
      <id>REG_FFDC_PROC_SLW_REGISTERS</id>
      <target>CHIP_IN_ERROR</target>
    </collectRegisterFfdc>
    <sbeError/>
  </hwpError>
  <!-- ******************************************************************** -->
  <hwpError>
    <rc>RC_SBE_PAUSE_WITH_SUCCESS</rc>
    <description>
      This halt code does not represent an error; This is the code associated
      with a procedure initiated halt of the SBE code, with the expectation
      that it will be resumed at a later point in time.
    </description>
    <!-- JDS TODO - this FFDC should probably only log the target engine -->
    <collectRegisterFfdc>
      <id>REG_FFDC_PROC_STATUS_AND_SBE_VITAL_REGISTERS</id>
      <id>REG_FFDC_PROC_SBE_REGISTERS</id>
      <id>REG_FFDC_PROC_SLW_REGISTERS</id>
      <target>CHIP_IN_ERROR</target>
    </collectRegisterFfdc>
    <sbeError/>
  </hwpError>
  <!-- ******************************************************************** -->
  <!-- ** Halt codes from sbe_common.H                                      -->
  <!-- ******************************************************************** -->
  <hwpError>
    <rc>RC_SBE_PROC_ENTRY_HALT</rc>
    <description>
      This halt code does not represent an error; This is the code associated
      with a HALT requested by the user prior to the execution of a procedure
      by setting the PROC_CONTROL_ENTRY_HALT bit in the control word for the
      procedure.
    </description>
    <!-- JDS TODO - this FFDC should probably only log the target engine -->
    <collectRegisterFfdc>
      <id>REG_FFDC_PROC_STATUS_AND_SBE_VITAL_REGISTERS</id>
      <id>REG_FFDC_PROC_SBE_REGISTERS</id>
      <id>REG_FFDC_PROC_SLW_REGISTERS</id>
      <target>CHIP_IN_ERROR</target>
    </collectRegisterFfdc>
    <sbeError/>
  </hwpError>
  <!-- ******************************************************************** -->
  <hwpError>
    <rc>RC_SBE_PROC_EXIT_HALT</rc>
    <description>
      This halt code does not represent an error; This is the code associated
      with a HALT requested by the user after the execution of a procedure
      by setting the PROC_CONTROL_EXIT_HALT bit in the control word for the
      procedure.
    </description>
    <sbeError/>
  </hwpError>
  <!-- ******************************************************************** -->
  <hwpError>
    <rc>RC_SBE_PROC_CHECKSTOP</rc>
    <description>
      This halt code indicates that a checkstop was detected after executing a
      procedure.  Use the fields of the SBEVITAL register to identify the
      procedure that failed.
    </description>
    <!-- JDS TODO - this FFDC should probably only log the target engine
      and to log the FIR regs? -->
    <collectRegisterFfdc>
      <id>REG_FFDC_PROC_STATUS_AND_SBE_VITAL_REGISTERS</id>
      <id>REG_FFDC_PROC_SBE_REGISTERS</id>
      <id>REG_FFDC_PROC_SLW_REGISTERS</id>
      <target>CHIP_IN_ERROR</target>
    </collectRegisterFfdc>
    <sbeError/>
  </hwpError>
  <!-- ******************************************************************** -->
  <hwpError>
    <rc>RC_SBE_PROC_RECOVERABLE</rc>
    <description>
      This halt code indicates that a recoverable error was detected after
      executing a procedure.  Use the fields of the SBEVITAL register to
      identify the procedure that failed.
    </description>
    <!-- JDS TODO - this FFDC should probably only log the target engine
      and to log the FIR regs? -->
    <collectRegisterFfdc>
      <id>REG_FFDC_PROC_STATUS_AND_SBE_VITAL_REGISTERS</id>
      <id>REG_FFDC_PROC_SBE_REGISTERS</id>
      <id>REG_FFDC_PROC_SLW_REGISTERS</id>
      <target>CHIP_IN_ERROR</target>
    </collectRegisterFfdc>
    <sbeError/>
  </hwpError>
  <!-- ******************************************************************** -->
  <hwpError>
    <rc>RC_SBE_PROC_SPATTN</rc>
    <description>
      This halt code indicates that a Special Attention was detected after
      executing a procedure.  Use the fields of the SBEVITAL register to
      identify the procedure that failed.
    </description>
    <!-- JDS TODO - this FFDC should probably only log the target engine
      and to log the FIR regs? -->
    <collectRegisterFfdc>
      <id>REG_FFDC_PROC_STATUS_AND_SBE_VITAL_REGISTERS</id>
      <id>REG_FFDC_PROC_SBE_REGISTERS</id>
      <id>REG_FFDC_PROC_SLW_REGISTERS</id>
      <target>CHIP_IN_ERROR</target>
    </collectRegisterFfdc>
    <sbeError/>
  </hwpError>
  <!-- ******************************************************************** -->
  <!-- ** Halt codes from proc_sbe_pore_errors.S                            -->
  <!-- ******************************************************************** -->
  <hwpError>
    <rc>RC_SBE_PORE_ERROR0</rc>
    <description>
      This halt code indicates that an execution-phase PIB/PCB access
      returned a non-0 response.  The PORE PIBMS_DBG registers 0 and 1
      (plus the remainder of the PORE state) contain the information required
      for an initial debug of the problem.
    </description>
    <!-- JDS TODO - this FFDC should probably only log the target engine -->
    <collectRegisterFfdc>
      <id>REG_FFDC_PROC_STATUS_AND_SBE_VITAL_REGISTERS</id>
      <id>REG_FFDC_PROC_SBE_REGISTERS</id>
      <id>REG_FFDC_PROC_SLW_REGISTERS</id>
      <target>CHIP_IN_ERROR</target>
    </collectRegisterFfdc>
    <sbeError/>
  </hwpError>
  <!-- ******************************************************************** -->
  <hwpError>
    <rc>RC_SBE_PORE_ERROR1</rc>
    <description>
      This halt code indicates that an execution-phase OCI accesss had an
      error.  The PORE PIBMS_DBG registers 0 and 1 (plus the remainder of the
      PORE state) contain the information required for an initial debug of the
      problem.

      This error should never occur during an SBE IPL since the SBE does not
      include an OCI interface.
    </description>
    <!-- JDS TODO - this FFDC should probably only log the target engine -->
    <collectRegisterFfdc>
      <id>REG_FFDC_PROC_STATUS_AND_SBE_VITAL_REGISTERS</id>
      <id>REG_FFDC_PROC_SBE_REGISTERS</id>
      <id>REG_FFDC_PROC_SLW_REGISTERS</id>
      <target>CHIP_IN_ERROR</target>
    </collectRegisterFfdc>
    <sbeError/>
  </hwpError>
  <!-- ******************************************************************** -->
  <hwpError>
    <rc>RC_SBE_PORE_ERROR2</rc>
    <description>
      This halt code indicates an instruction fetch or decode error. The PORE
      specification lists several causes of this error code.  The most likely
      causes in a production system are:
      o An I2C hang when fetching code from SEEPROM;
      o A bad branch that starts executing garbage or data;
      o Memory corruption
    </description>
    <!-- JDS TODO - this FFDC should probably only log the target engine -->
    <collectRegisterFfdc>
      <id>REG_FFDC_PROC_STATUS_AND_SBE_VITAL_REGISTERS</id>
      <id>REG_FFDC_PROC_SBE_REGISTERS</id>
      <id>REG_FFDC_PROC_SLW_REGISTERS</id>
      <target>CHIP_IN_ERROR</target>
    </collectRegisterFfdc>
    <sbeError/>
  </hwpError>
  <!-- ******************************************************************** -->
  <hwpError>
    <rc>RC_SBE_PORE_ERROR3</rc>
    <description>
      This halt code indicates an internal data error during consistency
      checking, e.g., a bad scan-data CRC.

      This error should never occur during an SBE IPL since the SBE IPL does
      not use the PORE SCAND instruction.
    </description>
    <!-- JDS TODO - this FFDC should probably only log the target engine -->
    <collectRegisterFfdc>
      <id>REG_FFDC_PROC_STATUS_AND_SBE_VITAL_REGISTERS</id>
      <id>REG_FFDC_PROC_SBE_REGISTERS</id>
      <id>REG_FFDC_PROC_SLW_REGISTERS</id>
      <target>CHIP_IN_ERROR</target>
    </collectRegisterFfdc>
    <sbeError/>
  </hwpError>
  <!-- ******************************************************************** -->
  <hwpError>
    <rc>RC_SBE_PORE_ERROR4</rc>
    <description>
      This halt code indicates that a second error occurred during processing
      of an initial error.

      It is extremely unlikely that this error would ever occur during an SBE
      IPL since the PORE error handlers are nothing more than a single HALT
      statement.
    </description>
    <!-- JDS TODO - this FFDC should probably only log the target engine -->
    <collectRegisterFfdc>
      <id>REG_FFDC_PROC_STATUS_AND_SBE_VITAL_REGISTERS</id>
      <id>REG_FFDC_PROC_SBE_REGISTERS</id>
      <id>REG_FFDC_PROC_SLW_REGISTERS</id>
      <target>CHIP_IN_ERROR</target>
    </collectRegisterFfdc>
    <sbeError/>
  </hwpError>
  <!-- ******************************************************************** -->
  <!-- ** Halt codes from scan0 subroutine                                  -->
  <!-- ******************************************************************** -->
  <hwpError>
    <rc>RC_SBE_SCAN0_DONE_POLL_THRESHOLD</rc>
    <description>
      This error is signalled by the scan0 subroutine, indicating that the
      scan0 DONE polling reached the specified threshold value. The scan0
      subroutine could have been called by various procedures.
    </description>
    <!-- JDS TODO - this FFDC should probably only log the target engine
         and should log something about the target chiplet -->
    <collectRegisterFfdc>
      <id>REG_FFDC_PROC_STATUS_AND_SBE_VITAL_REGISTERS</id>
      <id>REG_FFDC_PROC_SBE_REGISTERS</id>
      <id>REG_FFDC_PROC_SLW_REGISTERS</id>
      <target>CHIP_IN_ERROR</target>
    </collectRegisterFfdc>
    <sbeError/>
  </hwpError>
  <!-- ******************************************************************** -->
  <!-- ** Halt codes from arrayinit subroutine                              -->
  <!-- ******************************************************************** -->
  <hwpError>
    <rc>RC_SBE_ARRAYINIT_POLL_THRESHOLD</rc>
    <description>
      This error is signalled by the arrayinit subroutine, indicating that the
      arrayinit DONE polling reached the specified threshold value. The arrayinit
      subroutine could have been called by various procedures.
    </description>
    <!-- JDS TODO - this FFDC should probably only log the target engine
         and should log something about the target chiplet -->
    <collectRegisterFfdc>
      <id>REG_FFDC_PROC_STATUS_AND_SBE_VITAL_REGISTERS</id>
      <id>REG_FFDC_PROC_SBE_REGISTERS</id>
      <id>REG_FFDC_PROC_SLW_REGISTERS</id>
      <target>CHIP_IN_ERROR</target>
    </collectRegisterFfdc>
    <sbeError/>
  </hwpError>
</hwpErrors>
OpenPOWER on IntegriCloud