blob: 6cadf5acc5c54c29e818ed68102976a5bc65d88c [file] [log] [blame]
Matt Spinler44792fd2019-09-26 15:58:58 -05001{
2 "PELs":
3 [
Matt Spinler3fd08d62019-10-22 14:25:33 -05004 {
5 "Name": "xyz.openbmc_project.Common.Error.Timeout",
6 "Subsystem": "bmc_firmware",
Matt Spinler44792fd2019-09-26 15:58:58 -05007
Matt Spinler3fd08d62019-10-22 14:25:33 -05008 "SRC":
9 {
10 "ReasonCode": "0x1001",
11 "Words6To9":
12 {
13 "6":
14 {
15 "Description": "Timeout in ms",
16 "AdditionalDataPropSource": "TIMEOUT_IN_MSEC"
17 }
18 }
19 },
20
21 "Documentation":
22 {
23 "Description": "This is a generic timeout error",
24 "Message": "An operation timed out",
25 "Notes": [
26 "The journal should contain more information"
27 ]
28 }
29 },
30
31 {
32 "Name": "xyz.openbmc_project.Common.Error.InternalFailure",
33 "Subsystem": "bmc_firmware",
34
35 "SRC":
36 {
37 "ReasonCode": "0x1002",
38 "Words6To9":
39 {
40 }
41 },
42
43 "Documentation":
44 {
45 "Description": "BMC code had a generic internal failure",
46 "Message": "An application had an internal failure",
47 "Notes": [
48 "The journal should contain more information"
49 ]
50 }
51 },
52
53 {
54 "Name": "xyz.openbmc_project.Common.Error.InvalidArgument",
55 "Subsystem": "user_error",
56
57 "SRC":
58 {
59 "ReasonCode": "0x1003",
60 "Words6To9":
61 {
62 }
63 },
64
65 "Documentation":
66 {
67 "Description": "BMC code was given an invalid argument",
68 "Message": "Code was given an invalid argument",
69 "Notes": [
70 "The journal should contain more information"
71 ]
72 }
73 },
74 {
75 "Name": "xyz.openbmc_project.Common.Error.InsufficientPermission",
76 "Subsystem": "user_error",
77
78 "SRC":
79 {
80 "ReasonCode": "0x1004",
81 "Words6To9":
82 {
83 }
84 },
85
86 "Documentation":
87 {
88 "Description": "An operation failed due to insufficient permission",
89 "Message": "An operation failed due to unsufficient permission",
90 "Notes": [
91 "The journal should contain more information"
92 ]
93 }
94 },
95
96 {
97 "Name": "xyz.openbmc_project.Common.Error.NotAllowed",
98 "Subsystem": "user_error",
99
100 "SRC":
101 {
102 "ReasonCode": "0x1005",
103 "Words6To9":
104 {
105 }
106 },
107
108 "Documentation":
109 {
110 "Description": "An operation failed because it isn't allowed",
111 "Message": "An operation failed becuase it isn't allowed",
112 "Notes": [
113 "The journal should contain more information"
114 ]
115 }
116 },
117
118 {
119 "Name": "xyz.openbmc_project.Common.Error.NoCACertificate",
120 "Subsystem": "user_error",
121
122 "SRC":
123 {
124 "ReasonCode": "0x1006",
125 "Words6To9":
126 {
127 }
128 },
129
130 "Documentation":
131 {
132 "Description": "The server's CA certificate has not been provided",
133 "Message": "The server's CA certificate has not been provided"
134 }
Matt Spinler05c2c6c2019-12-18 14:02:09 -0600135 },
136
137 {
138 "Name": "org.open_power.Logging.Error.SentBadPELToHost",
139 "Subsystem": "bmc_firmware",
140 "Severity": "non_error",
141
142 "SRC":
143 {
144 "ReasonCode": "0x2001",
145 "Words6To9":
146 {
147 "6":
148 {
149 "Description": "The bad PEL ID",
150 "AdditionalDataPropSource": "BAD_ID"
151 }
152 }
153 },
154
155 "Documentation":
156 {
157 "Description": "The BMC sent the host a malformed PEL",
158 "Message": "The BMC sent the host a malformed PEL",
159 "Notes": [
160 "The host firmware rejected that PEL."
161 ]
162 }
Matt Spinlere95fd012020-01-07 12:53:16 -0600163 },
164
165 {
166 "Name": "org.open_power.Logging.Error.BadHostPEL",
167 "Subsystem": "platform_firmware",
168 "Severity": "unrecoverable",
169
170 "SRC":
171 {
172 "ReasonCode": "0x2002",
173 "Words6To9":
174 {
175 "6":
176 {
177 "Description": "The PLID of the invalid PEL",
178 "AdditionalDataPropSource": "PLID"
179 },
180 "7":
181 {
182 "Description": "The corresponding OpenBMC event log ID",
183 "AdditionalDataPropSource": "OBMC_LOG_ID"
184 },
185 "8":
186 {
187 "Description": "The size of the invalid PEL",
188 "AdditionalDataPropSource": "PEL_SIZE"
189 }
190 }
191 },
192
193 "Documentation":
194 {
195 "Description": "The host sent the BMC an invalid PEL",
196 "Message": "The host sent the BMC an invalid PEL",
197 "Notes": [
198 ]
199 }
Marri Devender Raoead1be22020-03-28 05:50:59 -0500200 },
201
202 {
203 "Name": "org.open_power.PHAL.Error.Boot",
204 "Subsystem": "cec_hardware",
205 "Severity": "unrecoverable",
206
207 "SRC":
208 {
209 "ReasonCode": "0x3000",
210 "Words6To9":
211 {
212 }
213 },
214
215 "Documentation":
216 {
217 "Description": "Failure occured during boot process",
218 "Message": "Failure occured during boot process",
219 "Notes": [
220 "Debug traces will be captured in AdditionalData section"
221 ]
222 }
Ben Tyner34836322020-04-15 17:01:48 -0500223 },
224
225 {
226 "Name": "org.open_power.Attn.Error.Terminate",
227 "Subsystem": "other_na",
228 "Severity": "critical_system_term",
229
230 "SRC":
231 {
232 "ReasonCode": "0xD138",
233 "Words6To9":
234 {
235 }
236 },
237
238 "Documentation":
239 {
240 "Description": "Status shows TI special attention active",
241 "Message": "TI special attention detected",
242 "Notes": [
243 "This entry is for any TI special attention event ",
244 "reported by the attention handler component"
245 ]
246 }
247 },
248
249 {
250 "Name": "org.open_power.Attn.Error.Fail",
251 "Subsystem": "bmc_firmware",
252 "Severity": "unrecoverable_loss_of_function",
253
254 "SRC":
255 {
256 "ReasonCode": "0xD13E",
257 "Words6To9":
258 {
259 "6":
260 {
261 "Description": "Error code from attention handler",
262 "AdditionalDataPropSource": "ERROR_CODE"
263 }
264 }
265 },
266 "Documentation":
267 {
268 "Description": "The attention handler encountered an error",
269 "MessageArgSources" : ["SRCWord6"],
270 "Message": "Attention handler error %1",
271 "Notes": [
272 "Attention handler will provide error code"
273 ]
274 }
275 },
276
277 {
278 "Name": "org.open_power.Attn.Error.Vital",
279 "Subsystem": "processor_chip",
280 "Severity": "critical",
281
282 "SRC":
283 {
284 "ReasonCode": "0xD16D",
285 "Words6To9":
286 {
287 }
288 },
289
290 "Documentation":
291 {
292 "Description": "Status shows SBE vital attention active",
293 "Message": "SBE vital attention detected",
294 "Notes": [
295 "This entry is for any SBE vital attention event ",
296 "reported by the attention handler component"
297 ]
298 }
299 },
300
301 {
302 "Name": "org.open_power.HwDiags.Error.Checkstop",
303 "Subsystem": "cec_hardware",
304 "Severity": "critical",
305
306 "SRC":
307 {
308 "ReasonCode": "0xE504",
309 "Words6To9":
310 {
311 "6":
312 {
313 "Description": "Chip ID",
314 "AdditionalDataPropSource": "CHIP_ID"
315 },
316 "8":
317 {
318 "Description": "Error Signature",
319 "AdditionalDataPropSource": "SIGNATURE"
320 }
321 }
322 },
323
324 "Documentation":
325 {
326 "Description": "A checkstop condition has been detected",
327 "MessageArgSources" : ["SRCWord6", "SRCWord8"],
328 "Message": "Checkstop: Chip %1, Signature %2",
329 "Notes": [
330 "This entry is for any checkstop event reported by ",
331 "the hardware diagnostics component."
332 ]
333 }
334 },
335
336 {
337 "Name": "org.open_power.HwDiags.Error.Fail",
338 "Subsystem": "bmc_firmware",
339 "Severity": "diagnostic_error",
340
341 "SRC":
342 {
343 "ReasonCode": "0xE580",
344 "Words6To9":
345 {
346 "6":
347 {
348 "Description": "Error code from hardware diagnostics",
349 "AdditionalDataPropSource": "ERROR_CODE"
350 }
351 }
352 },
353 "Documentation":
354 {
355 "Description": "Hardware diagnostics encountered an error",
356 "MessageArgSources" : ["SRCWord6"],
357 "Message": "Hardware diagnostics error %1",
358 "Notes": [
359 "Hardware diagnostics will provide error code"
360 ]
361 }
Shawn McCarney01648f52020-06-25 11:42:02 -0500362 },
363
364 {
365 "Name": "xyz.openbmc_project.Power.Regulators.Error.WriteVerification",
366 "Subsystem": "power",
367 "ComponentID": "0x2700",
368
369 "SRC": {
370 "Type": "11",
371 "ReasonCode": "0x2900",
372 "Words6To9": {}
373 },
374
375 "Documentation": {
376 "Description": "A write verification error occurred on a device",
377 "Message": "A write verification error occurred on a device",
378 "Notes": [
379 "This error occurs when a device register is written, ",
380 "read back, and the two values do not match. This is ",
381 "also called a read-back error. The device should be ",
382 "identified using the CALLOUT_DEVICE_PATH or ",
383 "CALLOUT_IIC_BUS/CALLOUT_IIC_ADDR keywords in the ",
384 "AdditionalData property of the event log. This will ",
385 "cause the device and the hardware in the communication ",
386 "path to be called out."
387 ]
388 }
389 },
390
391 {
392 "Name": "xyz.openbmc_project.Power.Regulators.Error.ConfigFile",
393 "Subsystem": "power",
394 "ComponentID": "0x2700",
395
396 "SRC": {
397 "Type": "11",
398 "ReasonCode": "0xA013",
399 "Words6To9": {}
400 },
401
402 "Callouts": [
403 {
404 "CalloutList": [
405 { "Priority": "high", "Procedure": "bmc_code" }
406 ]
407 }
408 ],
409
410 "Documentation": {
411 "Description": "A regulators configuration file error occurred",
412 "Message": "A regulators configuration file error occurred",
413 "Notes": [
414 "The regulators configuration file could not be found, ",
415 "could not be read, or had invalid contents."
416 ]
417 }
418 },
419
420 {
421 "Name": "xyz.openbmc_project.Power.Error.Internal",
422 "Subsystem": "power",
423 "ComponentID": "0x2700",
424
425 "SRC": {
426 "Type": "11",
427 "ReasonCode": "0xE000",
428 "Words6To9": {}
429 },
430
431 "Callouts": [
432 {
433 "CalloutList": [
434 { "Priority": "high", "Procedure": "bmc_code" }
435 ]
436 }
437 ],
438
439 "Documentation": {
440 "Description": "An internal firmware error occurred",
441 "Message": "An internal firmware error occurred",
442 "Notes": [
443 "The error details must be provided in the AdditionalData ",
444 "property of the event log."
445 ]
446 }
447 },
448
449 {
450 "Name": "xyz.openbmc_project.Power.Error.I2C",
451 "Subsystem": "cec_i2c",
452 "ComponentID": "0x2700",
453
454 "SRC": {
455 "Type": "11",
456 "ReasonCode": "0xE100",
457 "Words6To9": {}
458 },
459
460 "Documentation": {
461 "Description": "An I2C error occurred communicating with a device",
462 "Message": "An I2C error occurred communicating with a device",
463 "Notes": [
464 "The device should be identified using the ",
465 "CALLOUT_DEVICE_PATH or CALLOUT_IIC_BUS/CALLOUT_IIC_ADDR ",
466 "keywords in the AdditionalData property of the event ",
467 "log. This will cause the device and the hardware in the ",
468 "communication path to be called out."
469 ]
470 }
471 },
472
473 {
474 "Name": "xyz.openbmc_project.Power.Error.PMBus",
475 "Subsystem": "power",
476 "ComponentID": "0x2700",
477
478 "SRC": {
479 "Type": "11",
480 "ReasonCode": "0xE200",
481 "Words6To9": {}
482 },
483
484 "Documentation": {
485 "Description": "A PMBus error occurred on a device",
486 "Message": "A PMBus error occurred on a device",
487 "Notes": [
488 "This error occurs when the I2C communication was ",
489 "successful, but the PMBus value read is invalid or ",
490 "unsupported. CALLOUT_INVENTORY_PATH should be specified ",
491 "in the AdditionalData property of the event log so that ",
492 "the device is called out but not the communication path."
493 ]
494 }
495 },
496
497 {
498 "Name": "xyz.openbmc_project.Power.Error.DBus",
499 "Subsystem": "power",
500 "ComponentID": "0x2700",
501
502 "SRC": {
503 "Type": "11",
504 "ReasonCode": "0xE300",
505 "Words6To9": {}
506 },
507
508 "Callouts": [
509 {
510 "CalloutList": [
511 { "Priority": "high", "Procedure": "bmc_code" }
512 ]
513 }
514 ],
515
516 "Documentation": {
517 "Description": "A firmware inter-process communication (D-Bus) error occurred",
518 "Message": "A firmware inter-process communication (D-Bus) error occurred"
519 }
Matt Spinler3fd08d62019-10-22 14:25:33 -0500520 }
Matt Spinler44792fd2019-09-26 15:58:58 -0500521 ]
522}