blob: 655d153cdb6652fafbbf32e3f9aa31d972f48e3d [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",
Matt Spinler26958762020-08-27 13:21:23 -0500111 "Message": "An operation failed because it isn't allowed",
Matt Spinler3fd08d62019-10-22 14:25:33 -0500112 "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 {
Matt Spinler30ddc9f2020-07-16 15:39:59 -0500347 "Name": "xyz.openbmc_project.Logging.Error.Default",
348 "Subsystem": "other_na",
349
350 "SRC":
351 {
352 "ReasonCode": "0x2004",
353 "Words6To9":
354 {
355 }
356 },
357
358 "Documentation":
359 {
360 "Description": "This entry is used when no other matching entry is found",
361 "Message": "Unknown (Original event not in message registry)",
362 "Notes": [
363 "This is used when the actual error name isn't found in ",
364 "the registry. The original error name will be stored ",
365 "in the UserData section that contains the AdditionalData ",
366 "properties using the key ERROR_NAME.",
367 "This error may contain callouts if the creator passed ",
368 "them in.",
369 "The severity is set by the creator.",
370 "If this error is seen, then a code change needs to be ",
371 "made to add the missing error entry to this registry."
372 ]
373 }
374 },
375
376 {
Marri Devender Raoead1be22020-03-28 05:50:59 -0500377 "Name": "org.open_power.PHAL.Error.Boot",
378 "Subsystem": "cec_hardware",
379 "Severity": "unrecoverable",
380
381 "SRC":
382 {
383 "ReasonCode": "0x3000",
384 "Words6To9":
385 {
386 }
387 },
388
389 "Documentation":
390 {
391 "Description": "Failure occured during boot process",
392 "Message": "Failure occured during boot process",
393 "Notes": [
394 "Debug traces will be captured in AdditionalData section"
395 ]
396 }
Ben Tyner34836322020-04-15 17:01:48 -0500397 },
398
399 {
400 "Name": "org.open_power.Attn.Error.Terminate",
401 "Subsystem": "other_na",
402 "Severity": "critical_system_term",
403
404 "SRC":
405 {
406 "ReasonCode": "0xD138",
407 "Words6To9":
408 {
409 }
410 },
411
412 "Documentation":
413 {
414 "Description": "Status shows TI special attention active",
415 "Message": "TI special attention detected",
416 "Notes": [
417 "This entry is for any TI special attention event ",
418 "reported by the attention handler component"
419 ]
420 }
421 },
422
423 {
424 "Name": "org.open_power.Attn.Error.Fail",
425 "Subsystem": "bmc_firmware",
426 "Severity": "unrecoverable_loss_of_function",
427
428 "SRC":
429 {
430 "ReasonCode": "0xD13E",
431 "Words6To9":
432 {
433 "6":
434 {
435 "Description": "Error code from attention handler",
436 "AdditionalDataPropSource": "ERROR_CODE"
437 }
438 }
439 },
440 "Documentation":
441 {
442 "Description": "The attention handler encountered an error",
443 "MessageArgSources" : ["SRCWord6"],
444 "Message": "Attention handler error %1",
445 "Notes": [
446 "Attention handler will provide error code"
447 ]
448 }
449 },
450
451 {
452 "Name": "org.open_power.Attn.Error.Vital",
453 "Subsystem": "processor_chip",
454 "Severity": "critical",
455
456 "SRC":
457 {
458 "ReasonCode": "0xD16D",
459 "Words6To9":
460 {
461 }
462 },
463
464 "Documentation":
465 {
466 "Description": "Status shows SBE vital attention active",
467 "Message": "SBE vital attention detected",
468 "Notes": [
469 "This entry is for any SBE vital attention event ",
470 "reported by the attention handler component"
471 ]
472 }
473 },
474
475 {
476 "Name": "org.open_power.HwDiags.Error.Checkstop",
477 "Subsystem": "cec_hardware",
478 "Severity": "critical",
479
480 "SRC":
481 {
482 "ReasonCode": "0xE504",
483 "Words6To9":
484 {
485 "6":
486 {
487 "Description": "Chip ID",
488 "AdditionalDataPropSource": "CHIP_ID"
489 },
490 "8":
491 {
492 "Description": "Error Signature",
493 "AdditionalDataPropSource": "SIGNATURE"
494 }
495 }
496 },
497
498 "Documentation":
499 {
500 "Description": "A checkstop condition has been detected",
501 "MessageArgSources" : ["SRCWord6", "SRCWord8"],
502 "Message": "Checkstop: Chip %1, Signature %2",
503 "Notes": [
504 "This entry is for any checkstop event reported by ",
505 "the hardware diagnostics component."
506 ]
507 }
508 },
509
510 {
511 "Name": "org.open_power.HwDiags.Error.Fail",
512 "Subsystem": "bmc_firmware",
513 "Severity": "diagnostic_error",
514
515 "SRC":
516 {
517 "ReasonCode": "0xE580",
518 "Words6To9":
519 {
520 "6":
521 {
522 "Description": "Error code from hardware diagnostics",
523 "AdditionalDataPropSource": "ERROR_CODE"
524 }
525 }
526 },
527 "Documentation":
528 {
529 "Description": "Hardware diagnostics encountered an error",
530 "MessageArgSources" : ["SRCWord6"],
531 "Message": "Hardware diagnostics error %1",
532 "Notes": [
533 "Hardware diagnostics will provide error code"
534 ]
535 }
Shawn McCarney01648f52020-06-25 11:42:02 -0500536 },
537
538 {
Brandon Wyman38caaf02020-09-01 16:07:42 -0500539 "Name": "xyz.openbmc_project.Power.PowerSupply.Error.InputFault",
540 "Subsystem": "power_supply",
541 "Severity": "unrecoverable_redundancy_loss",
542 "ActionFlags": ["service_action", "report"],
543 "ComponentID": "0x2700",
544
545 "SRC": {
546 "Type": "11",
547 "ReasonCode": "0x15F0",
548 "Words6To9": {}
549 },
550
551 "Callouts": [
552 {
553 "CalloutList": [
554 { "Priority": "high", "SymbolicFRU": "pwrsply" }
555 ]
556 }
557 ],
558
559 "Documentation": {
560 "Description": "Power Supply input power fault",
561 "Message": "A power supply has indicated an input or under voltage condition.",
562 "Notes": [
563 "Check the power supply cabling and/or input power ",
564 "source. The PWRSPLY procedure is used rather than ",
565 "calling out a location code, as typically these faults ",
566 "are related to the supplied power, the cable, or the ",
567 "cable connectors. If the input fault resolves down to an ",
568 "issue with the power supply itself, the power supply ",
569 "indicating this input fault should be called out. Add the ",
570 "CALLOUT_INVENTORY_PATH to the additional data, and set the",
571 "CALLOUT_PRIORITY to something other than high."
572 ]
573 }
574 },
575
576 {
577 "Name": "xyz.openbmc_project.Power.PowerSupply.Error.Fault",
578 "Subsystem": "power_supply",
579 "Severity": "unrecoverable_redundancy_loss",
580 "ActionFlags": ["service_action", "report", "call_home"],
581 "ComponentID": "0x2700",
582
583 "SRC": {
584 "Type": "11",
585 "ReasonCode": "0x15F1",
586 "Words6To9": {}
587 },
588
589 "Documentation": {
590 "Description": "Power Supply power fault",
591 "Message": "The power supply detected a fault condition, see AdditionalData for further details.",
592 "Notes": [
593 "The power supply reporting the fault should be called ",
594 "out using the CALLOUT_INVENTORY_PATH keyword. Include ",
595 "specific fault, STATUS_* details, and code level in the ",
596 "AdditionalData section."
597 ]
598 }
599 },
600
601 {
602 "Name": "xyz.openbmc_project.Power.PowerSupply.Error.CommFault",
603 "Subsystem": "power_supply",
604 "Severity": "unrecoverable_redundancy_loss",
605 "ActionFlags": ["service_action", "report", "call_home"],
606 "ComponentID": "0x2700",
607
608 "SRC": {
609 "Type": "11",
610 "ReasonCode": "0x15F2",
611 "Words6To9": {}
612 },
613
614 "Documentation": {
615 "Description": "Power Supply non-power fault",
616 "Message": "A communication failure occurred talking to the power supply",
617 "Notes": [
618 "Communication problems with the power supply could be ",
619 "the power supply, or any hardware between it and the ",
620 "BMC. Reporting the error should be passing in a call ",
621 "out using CALLOUT_DEVICE_PATH."
622 ]
623 }
624 },
625
626 {
627 "Name": "xyz.openbmc_project.Power.PowerSupply.Error.Missing",
628 "Subsystem": "power_supply",
629 "Severity": "unrecoverable",
630 "ActionFlags": ["service_action", "report", "call_home"],
631 "ComponentID": "0x2700",
632
633 "SRC": {
634 "Type": "11",
635 "ReasonCode": "0x15F6",
636 "Words6To9": {}
637 },
638
639 "Callouts": [
640 {
641 "CalloutList": [
642 { "Priority": "high", "SymbolicFRU": "pwrsply" }
643 ]
644 }
645 ],
646
647 "Documentation": {
648 "Description": "Power Supply is missing",
649 "Message": "A power supply that should be present is missing",
650 "Notes": [
651 "The CalloutList should use the PWRSPLY symbolic FRU ",
652 "with the trusted location code property. This is not ",
653 "currently possible. An issue has been opened to allow ",
654 "for that combination. Until then, PWRSPLY will have a ",
655 "priority of high, and the caller should provide the ",
656 "CALLOUT_INVENTORY_PATH with CALLOUT_PRIORITY also set to ",
657 "high."
658 ]
659 }
660 },
661
662 {
Shawn McCarney01648f52020-06-25 11:42:02 -0500663 "Name": "xyz.openbmc_project.Power.Regulators.Error.WriteVerification",
664 "Subsystem": "power",
665 "ComponentID": "0x2700",
666
667 "SRC": {
668 "Type": "11",
669 "ReasonCode": "0x2900",
670 "Words6To9": {}
671 },
672
673 "Documentation": {
674 "Description": "A write verification error occurred on a device",
675 "Message": "A write verification error occurred on a device",
676 "Notes": [
677 "This error occurs when a device register is written, ",
678 "read back, and the two values do not match. This is ",
679 "also called a read-back error. The device should be ",
680 "identified using the CALLOUT_DEVICE_PATH or ",
681 "CALLOUT_IIC_BUS/CALLOUT_IIC_ADDR keywords in the ",
682 "AdditionalData property of the event log. This will ",
683 "cause the device and the hardware in the communication ",
684 "path to be called out."
685 ]
686 }
687 },
688
689 {
690 "Name": "xyz.openbmc_project.Power.Regulators.Error.ConfigFile",
691 "Subsystem": "power",
692 "ComponentID": "0x2700",
693
694 "SRC": {
695 "Type": "11",
696 "ReasonCode": "0xA013",
697 "Words6To9": {}
698 },
699
700 "Callouts": [
701 {
702 "CalloutList": [
703 { "Priority": "high", "Procedure": "bmc_code" }
704 ]
705 }
706 ],
707
708 "Documentation": {
709 "Description": "A regulators configuration file error occurred",
710 "Message": "A regulators configuration file error occurred",
711 "Notes": [
712 "The regulators configuration file could not be found, ",
713 "could not be read, or had invalid contents."
714 ]
715 }
716 },
717
718 {
719 "Name": "xyz.openbmc_project.Power.Error.Internal",
720 "Subsystem": "power",
721 "ComponentID": "0x2700",
722
723 "SRC": {
724 "Type": "11",
725 "ReasonCode": "0xE000",
726 "Words6To9": {}
727 },
728
729 "Callouts": [
730 {
731 "CalloutList": [
732 { "Priority": "high", "Procedure": "bmc_code" }
733 ]
734 }
735 ],
736
737 "Documentation": {
738 "Description": "An internal firmware error occurred",
739 "Message": "An internal firmware error occurred",
740 "Notes": [
741 "The error details must be provided in the AdditionalData ",
742 "property of the event log."
743 ]
744 }
745 },
746
747 {
748 "Name": "xyz.openbmc_project.Power.Error.I2C",
749 "Subsystem": "cec_i2c",
750 "ComponentID": "0x2700",
751
752 "SRC": {
753 "Type": "11",
754 "ReasonCode": "0xE100",
755 "Words6To9": {}
756 },
757
758 "Documentation": {
759 "Description": "An I2C error occurred communicating with a device",
760 "Message": "An I2C error occurred communicating with a device",
761 "Notes": [
762 "The device should be identified using the ",
763 "CALLOUT_DEVICE_PATH or CALLOUT_IIC_BUS/CALLOUT_IIC_ADDR ",
764 "keywords in the AdditionalData property of the event ",
765 "log. This will cause the device and the hardware in the ",
766 "communication path to be called out."
767 ]
768 }
769 },
770
771 {
772 "Name": "xyz.openbmc_project.Power.Error.PMBus",
773 "Subsystem": "power",
774 "ComponentID": "0x2700",
775
776 "SRC": {
777 "Type": "11",
778 "ReasonCode": "0xE200",
779 "Words6To9": {}
780 },
781
782 "Documentation": {
783 "Description": "A PMBus error occurred on a device",
784 "Message": "A PMBus error occurred on a device",
785 "Notes": [
786 "This error occurs when the I2C communication was ",
787 "successful, but the PMBus value read is invalid or ",
788 "unsupported. CALLOUT_INVENTORY_PATH should be specified ",
789 "in the AdditionalData property of the event log so that ",
790 "the device is called out but not the communication path."
791 ]
792 }
793 },
794
795 {
796 "Name": "xyz.openbmc_project.Power.Error.DBus",
797 "Subsystem": "power",
798 "ComponentID": "0x2700",
799
800 "SRC": {
801 "Type": "11",
802 "ReasonCode": "0xE300",
803 "Words6To9": {}
804 },
805
806 "Callouts": [
807 {
808 "CalloutList": [
809 { "Priority": "high", "Procedure": "bmc_code" }
810 ]
811 }
812 ],
813
814 "Documentation": {
815 "Description": "A firmware inter-process communication (D-Bus) error occurred",
816 "Message": "A firmware inter-process communication (D-Bus) error occurred"
817 }
Matt Spinler60d1c392020-09-23 15:23:24 -0500818 },
819
820 {
Matt Spinler7c9c07e2020-10-22 10:16:37 -0500821 "Name": "xyz.openbmc_project.Fan.Error.Fault",
822 "Subsystem": "power_fans",
823 "ComponentID": "0x2800",
824
825 "SRC": {
826 "Type": "11",
827 "ReasonCode": "0x76F0",
828 "Words6To9": {}
829 },
830
831 "Documentation": {
832 "Description": "Fan rotor fault",
833 "Message": "Fan rotor fault",
834 "Notes": [
835 "This error occurs when a fan rotor has been faulted for a ",
836 "certain amount of time. The callout is the fan which is ",
837 "passed in with CALLOUT_INVENTORY_PATH. The severity is ",
838 "passed in during creation and will be either informational ",
839 "or unrecoverable. The action flags use the defaults and ",
840 "vary based on the severity."
841 ]
842 }
843 },
844
845 {
Matt Spinler60d1c392020-09-23 15:23:24 -0500846 "Name": "xyz.openbmc_project.Fan.Error.Missing",
847 "Subsystem": "power_fans",
848 "ComponentID": "0x2800",
849 "Severity": "unrecoverable_redundancy_loss",
850 "ActionFlags": ["service_action", "report", "call_home"],
851
852 "SRC": {
853 "Type": "11",
854 "ReasonCode": "0x76F1",
855 "Words6To9": {}
856 },
857
858 "Callouts": [
859 {
860 "CalloutList": [
861 { "Priority": "high", "SymbolicFRU": "air_mover"},
862 { "Priority": "low", "LocCode": "P0" }
863 ]
864 }
865 ],
866
867 "Documentation": {
868 "Description": "A fan is missing",
869 "Message": "A fan is missing",
870 "Notes": [
871 "This error occurs when a fan has been missing for a ",
872 "certain amount of time. The callouts are made by ",
873 "passing in CALLOUT_INVENTORY_PATH which will be ",
874 "combined with the symbolic FRU (not possible yet) ",
875 "along with the FRU(s) where the controllers are."
876 ]
877 }
Matt Spinler3fd08d62019-10-22 14:25:33 -0500878 }
Matt Spinler44792fd2019-09-26 15:58:58 -0500879 ]
880}