Home
last modified time | relevance | path

Searched refs:fault (Results 1 – 25 of 158) sorted by relevance

1234567

/openbmc/phosphor-power/
H A Delog-errors.hpp12 namespace sdbusplus::error::org::open_power::witherspoon::fault namespace
16 namespace sdbusplus::error::org::open_power::witherspoon::fault namespace
20 namespace sdbusplus::error::org::open_power::witherspoon::fault namespace
24 namespace sdbusplus::error::org::open_power::witherspoon::fault namespace
28 namespace sdbusplus::error::org::open_power::witherspoon::fault namespace
32 namespace sdbusplus::error::org::open_power::witherspoon::fault namespace
36 namespace sdbusplus::error::org::open_power::witherspoon::fault namespace
40 namespace sdbusplus::error::org::open_power::witherspoon::fault namespace
44 namespace sdbusplus::error::org::open_power::witherspoon::fault namespace
48 namespace sdbusplus::error::org::open_power::witherspoon::fault namespace
[all …]
/openbmc/witherspoon-pfault-analysis/
H A Delog-errors.hpp13 namespace sdbusplus::error::org::open_power::witherspoon::fault namespace
17 namespace sdbusplus::error::org::open_power::witherspoon::fault namespace
21 namespace sdbusplus::error::org::open_power::witherspoon::fault namespace
25 namespace sdbusplus::error::org::open_power::witherspoon::fault namespace
29 namespace sdbusplus::error::org::open_power::witherspoon::fault namespace
33 namespace sdbusplus::error::org::open_power::witherspoon::fault namespace
37 namespace sdbusplus::error::org::open_power::witherspoon::fault namespace
41 namespace sdbusplus::error::org::open_power::witherspoon::fault namespace
45 namespace sdbusplus::error::org::open_power::witherspoon::fault namespace
49 namespace sdbusplus::error::org::open_power::witherspoon::fault namespace
[all …]
/openbmc/docs/designs/
H A Dhw-fault-monitor.md14 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>
69 goal of the fault monitor is to enable rich error logging (OEM and CPU vendor
73 - The fault monitor must be able to handle receiving fault information that is
[all …]
/openbmc/openbmc/meta-facebook/meta-yosemite4/recipes-phosphor/gpio/
H A Dphosphor-gpio-monitor_%.bbappend19 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/phosphor-power/phosphor-regulators/docs/config_file/
H A Dlog_phase_fault.md5 Logs a redundant phase fault error for a voltage regulator. This action should
6 be executed if a fault is detected during
14 A phase fault occurs when a phase stops functioning properly. The redundancy
17 The phase fault type indicates the level of redundancy remaining **after** the
18 fault has occurred:
25 If additional data about the fault was previously captured using
33 | type | yes | string | Phase fault type. Specify one of the following: "n+1", "n". |
H A Dphase_fault_detection.md11 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-power/phosphor-regulators/docs/
H A Dphase_fault_monitoring.md9 Voltage regulators can be monitored for redundant phase faults. If a fault is
15 A phase fault must be detected two consecutive times (15 seconds apart) before
19 A phase fault error will only be logged for a regulator once per system boot.
21 ## How phase fault detection is defined
23 Phase fault detection is defined for a voltage regulator using the
37 - Phase fault detection will continue with the next regulator.
38 - Phase fault detection will be attempted again for this regulator during the
/openbmc/openbmc/meta-facebook/meta-yosemite4/recipes-phosphor/gpio/phosphor-gpio-monitor/
H A Dnic-power-fault@.service2 Description=nic-power-fault
6 ExecStart=/usr/libexec/phosphor-gpio-monitor/nic-power-fault
7 SyslogIdentifier=nic-power-fault
H A Dslot-hsc-fault@.service2 Description=slot hsc-fault:%i
6 ExecStart=/usr/libexec/phosphor-gpio-monitor/slot-hsc-fault %i
7 SyslogIdentifier=slot-hsc-fault%i
H A Dmedusa-power-module-fault.service2 Description=Detect medusa power module fault
6 ExecStart=/usr/libexec/phosphor-gpio-monitor/medusa-power-module-fault
7 SyslogIdentifier=medusa-power-module-fault
H A Dfan-board-efuse-fault@.service2 Description=fan board power-fault:%i
6 ExecStart=/usr/libexec/phosphor-gpio-monitor/fan-board-efuse-fault %i
7 SyslogIdentifier=fan-board-efuse-fault%i
H A Dmedusa-hsc-fault@.service2 Description=Detect medusa hsc fault on position %i
6 ExecStart=/usr/libexec/phosphor-gpio-monitor/medusa-hsc-fault %i
7 SyslogIdentifier=Medusa hsc fault on position %i
/openbmc/openbmc/meta-facebook/meta-yosemite4/recipes-phosphor/dbus/
H A Dphosphor-dbus-monitor-config.bbappend1 PHOSPHOR_DBUS_MONITOR_CONFIGS:append = " fan-fault-led"
3 PHOSPHOR_DBUS_MONITOR_CONFIGS:append = " slot-fault-led"
4 PHOSPHOR_DBUS_MONITOR_CONFIGS:append = " fan-fault-poweroff-policy"
/openbmc/phosphor-power/phosphor-power-sequencer/docs/
H A Dpgood_faults.md9 (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-facebook/meta-catalina/recipes-phosphor/gpio/
H A Dphosphor-gpio-monitor_%.bbappend13 file://vr-fault-assert-log@.service \
14 file://vr-fault-deassert-log@.service \
15 file://vr-fault-event-logger \
41 vr-fault-assert-log@.service \
42 vr-fault-deassert-log@.service \
64 install -m 0755 ${UNPACKDIR}/vr-fault-event-logger \
65 ${D}${libexecdir}/${PN}/vr-fault-event-logger
/openbmc/phosphor-led-manager/test/
H A Dutest-group-priority.cpp143 const std::string fault = "fault"; in TEST_F() local
150 {fault, Layout::Action::Off, 0, 0, std::nullopt}, in TEST_F()
156 {fault, Layout::Action::Off, 0, 0, std::nullopt}, in TEST_F()
162 {fault, Layout::Action::On, 0, 0, std::nullopt}, in TEST_F()
168 {fault, Layout::Action::Blink, dutyon, period, std::nullopt}, in TEST_F()
174 {fault, Layout::Action::Blink, dutyon, period, std::nullopt}, in TEST_F()
180 {fault, Layout::Action::On, 0, 0, std::nullopt}, in TEST_F()
196 {fault, Layout::Action::Off}, in TEST_F()
204 {fault, Layout::Action::Off}, in TEST_F()
212 {fault, Layout::Action::On}, in TEST_F()
[all …]
/openbmc/openbmc/meta-facebook/meta-minerva/recipes-phosphor/gpio/
H A Dphosphor-gpio-monitor_%.bbappend9 vr-fault-assert-log@.service \
10 vr-fault-deassert-log@.service \
24 file://vr-fault-event-logger \
49 install -m 0755 ${UNPACKDIR}/vr-fault-event-logger ${D}${libexecdir}/${PN}/
/openbmc/openbmc/meta-facebook/meta-harma/recipes-phosphor/gpio/phosphor-gpio-monitor/
H A Dvr-fault-deassert-log@.service6 ExecStart=/usr/libexec/phosphor-gpio-monitor/vr-fault-event-logger "deassert" "%i"
7 SyslogIdentifier=%i-vr-fault-deassert
H A Dvr-fault-assert-log@.service6 ExecStart=/usr/libexec/phosphor-gpio-monitor/vr-fault-event-logger "assert" "%i"
7 SyslogIdentifier=%i-vr-fault-assert
/openbmc/openbmc/meta-facebook/meta-minerva/recipes-phosphor/gpio/phosphor-gpio-monitor/
H A Dvr-fault-deassert-log@.service6 ExecStart=/usr/libexec/phosphor-gpio-monitor/vr-fault-event-logger "deassert" "%i"
7 SyslogIdentifier=%i-vr-fault-deassert
H A Dvr-fault-assert-log@.service6 ExecStart=/usr/libexec/phosphor-gpio-monitor/vr-fault-event-logger "assert" "%i"
7 SyslogIdentifier=%i-vr-fault-assert
/openbmc/openbmc/meta-facebook/meta-santabarbara/recipes-phosphor/gpio/phosphor-gpio-monitor/
H A Dvr-fault-deassert-log@.service6 ExecStart=/usr/libexec/phosphor-gpio-monitor/vr-fault-event-logger "deassert" "%i"
7 SyslogIdentifier=%i-vr-fault-deassert
H A Dvr-fault-assert-log@.service6 ExecStart=/usr/libexec/phosphor-gpio-monitor/vr-fault-event-logger "assert" "%i"
7 SyslogIdentifier=%i-vr-fault-assert
/openbmc/openbmc/meta-facebook/meta-catalina/recipes-phosphor/gpio/phosphor-gpio-monitor/
H A Dvr-fault-assert-log@.service6 ExecStart=/usr/libexec/phosphor-gpio-monitor/vr-fault-event-logger "assert" "%i"
7 SyslogIdentifier=%i-vr-fault-assert
H A Dvr-fault-deassert-log@.service6 ExecStart=/usr/libexec/phosphor-gpio-monitor/vr-fault-event-logger "deassert" "%i"
7 SyslogIdentifier=%i-vr-fault-deassert

1234567