| /openbmc/openbmc/meta-ibm/recipes-phosphor/leds/witherspoon-led-manager-config/ |
| H A D | led.yaml | 18 front-fault:
23 rear-fault:
45 front-fault:
50 rear-fault:
77 front-fault:
82 rear-fault:
109 front-fault:
114 rear-fault:
141 front-fault:
146 rear-fault:
[all …]
|
| /openbmc/openbmc/meta-ibm/meta-romulus/recipes-phosphor/leds/romulus-led-manager-config/ |
| H A D | led.yaml | 16 fault:
30 # Both the 'fault' and 'identify' gpios are wired to the same LED.
34 fault:
45 fault:
51 fault:
57 fault:
63 fault:
69 fault:
75 fault:
81 fault:
[all …]
|
| /openbmc/linux/drivers/gpu/drm/nouveau/nvkm/subdev/fault/ |
| D | base.c | |
| D | gv100.c | |
| /openbmc/phosphor-power/ |
| H A D | elog-errors.hpp | 12 namespace sdbusplus::error::org::open_power::witherspoon::fault namespace
15 } // namespace sdbusplus::error::org::open_power::witherspoon::fault
16 namespace sdbusplus::error::org::open_power::witherspoon::fault namespace
19 } // namespace sdbusplus::error::org::open_power::witherspoon::fault
20 namespace sdbusplus::error::org::open_power::witherspoon::fault namespace
23 } // namespace sdbusplus::error::org::open_power::witherspoon::fault
24 namespace sdbusplus::error::org::open_power::witherspoon::fault namespace
27 } // namespace sdbusplus::error::org::open_power::witherspoon::fault
28 namespace sdbusplus::error::org::open_power::witherspoon::fault namespace
31 } // namespace sdbusplus::error::org::open_power::witherspoon::fault
[all …]
|
| /openbmc/openbmc/meta-amd/meta-ethanolx/recipes-phosphor/leds/ethanolx-led-manager-config/ |
| H A D | led.yaml | 4 fault:
18 fault:
29 fault:
35 fault:
41 fault:
47 fault:
53 fault:
59 fault:
65 fault:
71 fault:
[all …]
|
| /openbmc/openbmc/meta-amd/meta-daytonax/recipes-phosphor/leds/daytonax-led-manager-config/ |
| H A D | led.yaml | 4 led-fault:
18 led-fault:
29 led-fault:
35 led-fault:
41 led-fault:
47 led-fault:
53 led-fault:
59 led-fault:
65 led-fault:
71 led-fault:
[all …]
|
| /openbmc/docs/designs/ |
| H A D | hw-fault-monitor.md | 1 # Hardware Fault Monitor
14 The goal is to create a new hardware fault monitor which will provide a
15 framework for collecting various fault and sensor information and making it
19 information through BMC interfaces, the hardware fault monitor will also receive
24 Future expansion of the hardware fault monitor would include adding the means to
25 locally analyze fault and sensor information and then based on specified
27 hardware fault monitor could receive repair action requests via Redfish from
54 - FRU fault manager controls the blinking of LEDs when faults occur:
55 <https://github.com/openbmc/phosphor-led-manager/blob/master/fault-monitor/fru-fault-monitor.hpp>
62 There is an OpenCompute Fault Management Infrastructure proposal that also
[all …]
|
| /openbmc/openbmc/meta-facebook/meta-minerva/recipes-phosphor/gpio/phosphor-gpio-monitor/ |
| H A D | minerva-phosphor-multi-gpio-monitor.json | 753 "RISING": ["vr-fault-deassert-log@cmm_p12v-ina230-alert.service"],
754 "FALLING": ["vr-fault-assert-log@cmm_p12v-ina230-alert.service"]
763 "RISING": ["vr-fault-deassert-log@cmm_p24v-ina230-alert.service"],
764 "FALLING": ["vr-fault-assert-log@cmm_p24v-ina230-alert.service"]
773 "RISING": ["vr-fault-deassert-log@cmm_p48v-hsc-alert.service"],
774 "FALLING": ["vr-fault-assert-log@cmm_p48v-hsc-alert.service"]
783 "RISING": ["vr-fault-assert-log@cmm_p1v05.service"],
784 "FALLING": ["vr-fault-deassert-log@cmm_p1v05.service"]
793 "RISING": ["vr-fault-assert-log@cmm_p1v5.service"],
794 "FALLING": ["vr-fault-deassert-log@cmm_p1v5.service"]
[all …]
|
| /openbmc/witherspoon-pfault-analysis/ |
| H A D | elog-errors.hpp | 13 namespace sdbusplus::error::org::open_power::witherspoon::fault namespace
16 } // namespace sdbusplus::error::org::open_power::witherspoon::fault
17 namespace sdbusplus::error::org::open_power::witherspoon::fault namespace
20 } // namespace sdbusplus::error::org::open_power::witherspoon::fault
21 namespace sdbusplus::error::org::open_power::witherspoon::fault namespace
24 } // namespace sdbusplus::error::org::open_power::witherspoon::fault
25 namespace sdbusplus::error::org::open_power::witherspoon::fault namespace
28 } // namespace sdbusplus::error::org::open_power::witherspoon::fault
29 namespace sdbusplus::error::org::open_power::witherspoon::fault namespace
32 } // namespace sdbusplus::error::org::open_power::witherspoon::fault
[all …]
|
| /openbmc/linux/arch/powerpc/platforms/powernv/ |
| D | vas-fault.c | |
| /openbmc/openbmc/meta-facebook/meta-yosemite4/recipes-phosphor/gpio/ |
| H A D | phosphor-gpio-monitor_%.bbappend | 19 file://slot-hsc-fault \
20 file://slot-hsc-fault@.service \
21 file://fan-board-efuse-fault \
22 file://fan-board-efuse-fault@.service \
27 file://nic-power-fault \
28 file://nic-power-fault@.service \
37 file://medusa-hsc-fault@.service \
38 file://medusa-hsc-fault \
39 file://medusa-power-module-fault.service \
40 file://medusa-power-module-fault \
[all …]
|
| /openbmc/openbmc/meta-ibm/meta-system1/recipes-phosphor/leds/system1-led-manager-config/ |
| H A D | led.yaml | 44 led-fan0-fault:
51 led-fan0-fault:
58 led-fan0-fault:
65 led-fan0-fault:
72 led-fan0-fault:
79 led-fan0-fault:
86 led-fan0-fault:
121 led-nvmed0-fault:
128 led-nvmed01-fault:
135 led-nvmed2-fault:
[all …]
|
| /openbmc/linux/arch/arm/mm/ |
| D | fsr-3level.c | |
| D | fsr-2level.c | |
| /openbmc/witherspoon-pfault-analysis/org/open_power/Witherspoon/ |
| H A D | Fault.errors.yaml | 10 description: The power supply detected an output overcurrent fault condition.
13 description: The power supply detected an output overvoltage fault condition.
22 description: A power off was issued because a power fault was detected
28 description: The power sequencer chip detected a voltage fault
31 description: The power sequencer chip detected a PGOOD fault
34 description: The power sequencer chip detected a fault
37 description: A GPU suffered a power fault
40 description: A GPU suffered an over-temperature fault
43 description: A memory device suffered a power fault
|
| /openbmc/linux/arch/microblaze/mm/ |
| D | fault.c | |
| /openbmc/phosphor-power/phosphor-power-sequencer/docs/ |
| H A D | pgood_faults.md | 9 (pgood) fault has occurred.
11 ## Pgood fault while powering on the system
21 ## Pgood fault after the system was powered on
23 A pgood fault can occur after a system has been powered on. The system may have
35 ## Pgood fault handling
37 `phosphor-power-sequencer` detects a pgood fault by monitoring the chassis pgood
43 When a pgood fault is detected, `phosphor-power-sequencer` will perform the
47 fault.
48 - Log an error with information about the fault.
53 were powered on are also experiencing a pgood fault. If so, check if any
[all …]
|
| /openbmc/openbmc/meta-ampere/meta-jade/recipes-phosphor/leds/phosphor-led-manager/ |
| H A D | com.ampere.Hardware.Chassis.Model.MtJade.json | 17 "Name": "fault",
53 "Name": "fault",
65 "Name": "fault",
77 "Name": "fault",
89 "Name": "fault",
101 "Name": "fault",
113 "Name": "fault",
125 "Name": "fault",
137 "Name": "fault",
149 "Name": "fault",
|
| /openbmc/linux/arch/alpha/mm/ |
| D | fault.c | |
| /openbmc/linux/arch/parisc/mm/ |
| D | fault.c | |
| /openbmc/linux/arch/x86/kvm/svm/ |
| D | svm_ops.h | |
| /openbmc/phosphor-power/phosphor-regulators/docs/config_file/ |
| H A D | phase_fault_detection.md | 11 will continue to provide the desired output voltage. However, a phase fault
14 The technique used to detect a phase fault varies depending on the regulator
18 Phase fault detection is performed every 15 seconds. A phase fault must be
24 - Use the [if](if.md) action to implement the high level behavior "if a fault is
26 - Detecting the fault
28 the fault. For example, you may need to check a bit in a status register.
31 additional data about the fault if necessary.
32 - Use the [log_phase_fault](log_phase_fault.md) action to log a phase fault
50 … of strings | One or more comment lines describing the phase fault detection. …
63 "comments": ["Detect phase fault using I/O expander"],
[all …]
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/State/ |
| H A D | Power.events.yaml | 15 description: A fault has been detected on a power rail.
16 message: A fault has been detected on power rail '{PowerRail}'.
30 description: A fault has been detected from a voltage regulator.
32 A fault has been detected on voltage regulator
44 description: A fault detected on a power rail has cleared.
45 message: A fault has cleared on power rail '{PowerRail}'.
54 description: A fault detected on a voltage regulator has cleared.
56 A fault has cleared on voltage regulator '{VoltageRegulator}'.
|
| /openbmc/linux/arch/nios2/mm/ |
| D | fault.c | |