blob: b4bf308a612260816a748a8fc30789e1d696b1b3 [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 {
Matt Spinleraf036b12020-06-25 10:53:52 -0500138 "Name": "xyz.openbmc_project.Sensor.Device.Error.ReadFailure",
139 "Subsystem": "cec_chip_iface",
140
141 "SRC":
142 {
143 "ReasonCode": "0x1007",
144 "Words6To9":
145 {
146 "6":
147 {
148 "Description": "errno of the failure",
149 "AdditionalDataPropSource": "CALLOUT_ERRNO"
150 }
151 }
152 },
153
154 "Documentation":
155 {
156 "Description": "Sensor device read failure",
157 "Message": "There was a failure when reading a sensor device",
158 "Notes": [
159 "The severity is set by the creator.",
160 "The action flags are set automatically by the code.",
161 "Callouts added based on CALLOUT_DEVICE_PATH."
162 ]
163 }
164 },
165
166 {
167 "Name": "xyz.openbmc_project.Common.Device.Error.ReadFailure",
168 "Subsystem": "cec_chip_iface",
169
170 "SRC":
171 {
172 "ReasonCode": "0x1008",
173 "Words6To9":
174 {
175 "6":
176 {
177 "Description": "errno of the failure",
178 "AdditionalDataPropSource": "CALLOUT_ERRNO"
179 }
180 }
181 },
182
183 "Documentation":
184 {
185 "Description": "Device read failure",
186 "Message": "There was a failure when reading a hardware device",
187 "Notes": [
188 "The severity is set by the creator.",
189 "The action flags are set automatically by the code.",
190 "Callouts added based on CALLOUT_DEVICE_PATH."
191 ]
192 }
193 },
194
195 {
196 "Name": "xyz.openbmc_project.Control.Device.Error.WriteFailure",
197 "Subsystem": "cec_chip_iface",
198
199 "SRC":
200 {
201 "ReasonCode": "0x1009",
202 "Words6To9":
203 {
204 "6":
205 {
206 "Description": "errno of the failure",
207 "AdditionalDataPropSource": "CALLOUT_ERRNO"
208 }
209 }
210 },
211
212 "Documentation":
213 {
214 "Description": "Device write failure",
215 "Message": "There was a failure when writing to a hardware device",
216 "Notes": [
217 "The severity is set by the creator.",
218 "The action flags are set automatically by the code.",
219 "Callouts added based on CALLOUT_DEVICE_PATH"
220 ]
221 }
222 },
223
224 {
225 "Name": "xyz.openbmc_project.Common.Device.Error.WriteFailure",
226 "Subsystem": "cec_chip_iface",
227
228 "SRC":
229 {
230 "ReasonCode": "0x100A",
231 "Words6To9":
232 {
233 "6":
234 {
235 "Description": "errno of the failure",
236 "AdditionalDataPropSource": "CALLOUT_ERRNO"
237 }
238 }
239 },
240
241 "Documentation":
242 {
243 "Description": "Device write failure",
244 "Message": "There was a failure when writing to a hardware device",
245 "Notes": [
246 "The severity is set by the creator.",
247 "The action flags are set automatically by the code.",
248 "Callouts added based on CALLOUT_DEVICE_PATH"
249 ]
250 }
251 },
252 {
Matt Spinler05c2c6c2019-12-18 14:02:09 -0600253 "Name": "org.open_power.Logging.Error.SentBadPELToHost",
254 "Subsystem": "bmc_firmware",
255 "Severity": "non_error",
256
257 "SRC":
258 {
259 "ReasonCode": "0x2001",
260 "Words6To9":
261 {
262 "6":
263 {
264 "Description": "The bad PEL ID",
265 "AdditionalDataPropSource": "BAD_ID"
266 }
267 }
268 },
269
270 "Documentation":
271 {
272 "Description": "The BMC sent the host a malformed PEL",
273 "Message": "The BMC sent the host a malformed PEL",
274 "Notes": [
275 "The host firmware rejected that PEL."
276 ]
277 }
Matt Spinlere95fd012020-01-07 12:53:16 -0600278 },
279
280 {
281 "Name": "org.open_power.Logging.Error.BadHostPEL",
282 "Subsystem": "platform_firmware",
283 "Severity": "unrecoverable",
284
285 "SRC":
286 {
287 "ReasonCode": "0x2002",
288 "Words6To9":
289 {
290 "6":
291 {
292 "Description": "The PLID of the invalid PEL",
293 "AdditionalDataPropSource": "PLID"
294 },
295 "7":
296 {
297 "Description": "The corresponding OpenBMC event log ID",
298 "AdditionalDataPropSource": "OBMC_LOG_ID"
299 },
300 "8":
301 {
302 "Description": "The size of the invalid PEL",
303 "AdditionalDataPropSource": "PEL_SIZE"
304 }
305 }
306 },
307
308 "Documentation":
309 {
310 "Description": "The host sent the BMC an invalid PEL",
311 "Message": "The host sent the BMC an invalid PEL",
312 "Notes": [
313 ]
314 }
Marri Devender Raoead1be22020-03-28 05:50:59 -0500315 },
316
317 {
Matt Spinler3477ce92020-07-08 14:49:25 -0500318 "Name": "org.open_power.Logging.Error.TestError1",
319 "Subsystem": "platform_firmware",
320 "Severity": "unrecoverable",
321
322 "SRC":
323 {
324 "ReasonCode": "0x2003",
325 "Words6To9":
326 {
327 }
328 },
329
330 "Callouts": [
331 {
332 "CalloutList": [
333 {"Priority": "high", "Procedure": "bmc_code"},
334 {"Priority": "medium", "SymbolicFRU": "service_docs"}
335 ]
336 }
337 ],
338
339 "Documentation":
340 {
341 "Description": "An error for testing",
342 "Message": "This is a test error"
343 }
344 },
345
346 {
Marri Devender Raoead1be22020-03-28 05:50:59 -0500347 "Name": "org.open_power.PHAL.Error.Boot",
348 "Subsystem": "cec_hardware",
349 "Severity": "unrecoverable",
350
351 "SRC":
352 {
353 "ReasonCode": "0x3000",
354 "Words6To9":
355 {
356 }
357 },
358
359 "Documentation":
360 {
361 "Description": "Failure occured during boot process",
362 "Message": "Failure occured during boot process",
363 "Notes": [
364 "Debug traces will be captured in AdditionalData section"
365 ]
366 }
Ben Tyner34836322020-04-15 17:01:48 -0500367 },
368
369 {
370 "Name": "org.open_power.Attn.Error.Terminate",
371 "Subsystem": "other_na",
372 "Severity": "critical_system_term",
373
374 "SRC":
375 {
376 "ReasonCode": "0xD138",
377 "Words6To9":
378 {
379 }
380 },
381
382 "Documentation":
383 {
384 "Description": "Status shows TI special attention active",
385 "Message": "TI special attention detected",
386 "Notes": [
387 "This entry is for any TI special attention event ",
388 "reported by the attention handler component"
389 ]
390 }
391 },
392
393 {
394 "Name": "org.open_power.Attn.Error.Fail",
395 "Subsystem": "bmc_firmware",
396 "Severity": "unrecoverable_loss_of_function",
397
398 "SRC":
399 {
400 "ReasonCode": "0xD13E",
401 "Words6To9":
402 {
403 "6":
404 {
405 "Description": "Error code from attention handler",
406 "AdditionalDataPropSource": "ERROR_CODE"
407 }
408 }
409 },
410 "Documentation":
411 {
412 "Description": "The attention handler encountered an error",
413 "MessageArgSources" : ["SRCWord6"],
414 "Message": "Attention handler error %1",
415 "Notes": [
416 "Attention handler will provide error code"
417 ]
418 }
419 },
420
421 {
422 "Name": "org.open_power.Attn.Error.Vital",
423 "Subsystem": "processor_chip",
424 "Severity": "critical",
425
426 "SRC":
427 {
428 "ReasonCode": "0xD16D",
429 "Words6To9":
430 {
431 }
432 },
433
434 "Documentation":
435 {
436 "Description": "Status shows SBE vital attention active",
437 "Message": "SBE vital attention detected",
438 "Notes": [
439 "This entry is for any SBE vital attention event ",
440 "reported by the attention handler component"
441 ]
442 }
443 },
444
445 {
446 "Name": "org.open_power.HwDiags.Error.Checkstop",
447 "Subsystem": "cec_hardware",
448 "Severity": "critical",
449
450 "SRC":
451 {
452 "ReasonCode": "0xE504",
453 "Words6To9":
454 {
455 "6":
456 {
457 "Description": "Chip ID",
458 "AdditionalDataPropSource": "CHIP_ID"
459 },
460 "8":
461 {
462 "Description": "Error Signature",
463 "AdditionalDataPropSource": "SIGNATURE"
464 }
465 }
466 },
467
468 "Documentation":
469 {
470 "Description": "A checkstop condition has been detected",
471 "MessageArgSources" : ["SRCWord6", "SRCWord8"],
472 "Message": "Checkstop: Chip %1, Signature %2",
473 "Notes": [
474 "This entry is for any checkstop event reported by ",
475 "the hardware diagnostics component."
476 ]
477 }
478 },
479
480 {
481 "Name": "org.open_power.HwDiags.Error.Fail",
482 "Subsystem": "bmc_firmware",
483 "Severity": "diagnostic_error",
484
485 "SRC":
486 {
487 "ReasonCode": "0xE580",
488 "Words6To9":
489 {
490 "6":
491 {
492 "Description": "Error code from hardware diagnostics",
493 "AdditionalDataPropSource": "ERROR_CODE"
494 }
495 }
496 },
497 "Documentation":
498 {
499 "Description": "Hardware diagnostics encountered an error",
500 "MessageArgSources" : ["SRCWord6"],
501 "Message": "Hardware diagnostics error %1",
502 "Notes": [
503 "Hardware diagnostics will provide error code"
504 ]
505 }
Shawn McCarney01648f52020-06-25 11:42:02 -0500506 },
507
508 {
509 "Name": "xyz.openbmc_project.Power.Regulators.Error.WriteVerification",
510 "Subsystem": "power",
511 "ComponentID": "0x2700",
512
513 "SRC": {
514 "Type": "11",
515 "ReasonCode": "0x2900",
516 "Words6To9": {}
517 },
518
519 "Documentation": {
520 "Description": "A write verification error occurred on a device",
521 "Message": "A write verification error occurred on a device",
522 "Notes": [
523 "This error occurs when a device register is written, ",
524 "read back, and the two values do not match. This is ",
525 "also called a read-back error. The device should be ",
526 "identified using the CALLOUT_DEVICE_PATH or ",
527 "CALLOUT_IIC_BUS/CALLOUT_IIC_ADDR keywords in the ",
528 "AdditionalData property of the event log. This will ",
529 "cause the device and the hardware in the communication ",
530 "path to be called out."
531 ]
532 }
533 },
534
535 {
536 "Name": "xyz.openbmc_project.Power.Regulators.Error.ConfigFile",
537 "Subsystem": "power",
538 "ComponentID": "0x2700",
539
540 "SRC": {
541 "Type": "11",
542 "ReasonCode": "0xA013",
543 "Words6To9": {}
544 },
545
546 "Callouts": [
547 {
548 "CalloutList": [
549 { "Priority": "high", "Procedure": "bmc_code" }
550 ]
551 }
552 ],
553
554 "Documentation": {
555 "Description": "A regulators configuration file error occurred",
556 "Message": "A regulators configuration file error occurred",
557 "Notes": [
558 "The regulators configuration file could not be found, ",
559 "could not be read, or had invalid contents."
560 ]
561 }
562 },
563
564 {
565 "Name": "xyz.openbmc_project.Power.Error.Internal",
566 "Subsystem": "power",
567 "ComponentID": "0x2700",
568
569 "SRC": {
570 "Type": "11",
571 "ReasonCode": "0xE000",
572 "Words6To9": {}
573 },
574
575 "Callouts": [
576 {
577 "CalloutList": [
578 { "Priority": "high", "Procedure": "bmc_code" }
579 ]
580 }
581 ],
582
583 "Documentation": {
584 "Description": "An internal firmware error occurred",
585 "Message": "An internal firmware error occurred",
586 "Notes": [
587 "The error details must be provided in the AdditionalData ",
588 "property of the event log."
589 ]
590 }
591 },
592
593 {
594 "Name": "xyz.openbmc_project.Power.Error.I2C",
595 "Subsystem": "cec_i2c",
596 "ComponentID": "0x2700",
597
598 "SRC": {
599 "Type": "11",
600 "ReasonCode": "0xE100",
601 "Words6To9": {}
602 },
603
604 "Documentation": {
605 "Description": "An I2C error occurred communicating with a device",
606 "Message": "An I2C error occurred communicating with a device",
607 "Notes": [
608 "The device should be identified using the ",
609 "CALLOUT_DEVICE_PATH or CALLOUT_IIC_BUS/CALLOUT_IIC_ADDR ",
610 "keywords in the AdditionalData property of the event ",
611 "log. This will cause the device and the hardware in the ",
612 "communication path to be called out."
613 ]
614 }
615 },
616
617 {
618 "Name": "xyz.openbmc_project.Power.Error.PMBus",
619 "Subsystem": "power",
620 "ComponentID": "0x2700",
621
622 "SRC": {
623 "Type": "11",
624 "ReasonCode": "0xE200",
625 "Words6To9": {}
626 },
627
628 "Documentation": {
629 "Description": "A PMBus error occurred on a device",
630 "Message": "A PMBus error occurred on a device",
631 "Notes": [
632 "This error occurs when the I2C communication was ",
633 "successful, but the PMBus value read is invalid or ",
634 "unsupported. CALLOUT_INVENTORY_PATH should be specified ",
635 "in the AdditionalData property of the event log so that ",
636 "the device is called out but not the communication path."
637 ]
638 }
639 },
640
641 {
642 "Name": "xyz.openbmc_project.Power.Error.DBus",
643 "Subsystem": "power",
644 "ComponentID": "0x2700",
645
646 "SRC": {
647 "Type": "11",
648 "ReasonCode": "0xE300",
649 "Words6To9": {}
650 },
651
652 "Callouts": [
653 {
654 "CalloutList": [
655 { "Priority": "high", "Procedure": "bmc_code" }
656 ]
657 }
658 ],
659
660 "Documentation": {
661 "Description": "A firmware inter-process communication (D-Bus) error occurred",
662 "Message": "A firmware inter-process communication (D-Bus) error occurred"
663 }
Matt Spinler3fd08d62019-10-22 14:25:33 -0500664 }
Matt Spinler44792fd2019-09-26 15:58:58 -0500665 ]
666}