Home
last modified time | relevance | path

Searched full:faulty (Results 1 – 25 of 49) sorted by relevance

12

/openbmc/openbmc/meta-openpower/recipes-bsp/guard/
H A Dguard_git.bb2 SUMMARY = "Guard the faulty components"
3 DESCRIPTION = "Provide a way to guard the faulty component from the system"
/openbmc/docs/designs/
H A Dguard-on-bmc.md6 the system downtime can be prevented by isolating the faulty components. This
14 guarding the system from faulty components.
18 **Guard**: Guarding the system against failures by permanently isolating faulty
30 The guard in the servers is for managing a record of faulty components to keep
31 them out of service. The list of faulty but guarded components can be stored in
74 - The clearing of the records after the replacement of the faulty component
H A Dhw-fault-monitor.md57 - Guard On BMC records and manages a list of faulty components for isolation.
58 (Both the host and the BMC may identify faulty components and create guard
/openbmc/openbmc/meta-openembedded/meta-filesystems/recipes-filesystems/burnia/
H A Dlibburn_1.5.6.bb9 file://0001-Bug-fix-Faulty-signal-handler-prototype-spoiled-comp.patch"
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/testdisk/
H A Dtestdisk_7.2.bb1 … make non-booting disks bootable again when these symptoms are caused by faulty software, certain …
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-benchmark/memtester/
H A Dmemtester_4.7.1.bb1 SUMMARY = "Utility to test for faulty memory subsystem"
/openbmc/openbmc/meta-openembedded/meta-filesystems/recipes-filesystems/burnia/libburn/
H A D0001-Bug-fix-Faulty-signal-handler-prototype-spoiled-comp.patch4 Subject: [PATCH] Bug fix: Faulty signal handler prototype spoiled compilation
/openbmc/openbmc/meta-raspberrypi/recipes-graphics/userland/files/
H A D0005-interface-remove-faulty-assert-to-make-weston-happy-.patch4 Subject: [PATCH] interface: remove faulty assert() to make weston happy at
/openbmc/openbmc/poky/meta/recipes-devtools/dpkg/dpkg/
H A Darch_pm.patch8 because of faulty code added to Arch.pm in the latest
/openbmc/u-boot/drivers/crypto/
H A Dace_sha.c106 debug("ACE was not setup properly or it is faulty\n"); in hw_sha256()
113 debug("ACE was not setup properly or it is faulty\n"); in hw_sha1()
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/State/Leak/
H A DDetector.interface.yaml48 The state cannot be determined as the detector may be faulty.
/openbmc/u-boot/drivers/crypto/fsl/
H A Dfsl_hash.c205 printf("CAAM was not setup properly or it is faulty\n"); in hw_sha256()
212 printf("CAAM was not setup properly or it is faulty\n"); in hw_sha1()
/openbmc/openbmc/poky/meta/recipes-support/appstream/appstream/
H A D0003-Fix-PACKAGE_PREFIX_DIR-in-qt-cmake-AppStreamQtConfig.patch23 | * The installation package was faulty and references files it does not
/openbmc/bmcweb/redfish-core/include/registries/
H A Dpower_message_registry.hpp52 "Check the breaker hardware and replace any faulty components.",
76 … "Check the circuit and connected devices, and disconnect or replace any faulty devices.",
679 "Check the power supply hardware and replace any faulty component.",
739 "Check the power supply hardware and replace any faulty component.",
775 "Check the power supply hardware and replace any faulty component.",
H A Dstorage_device_message_registry.hpp162 "Ensure all cables are properly and securely connected. Replace faulty cables.",
174 "Ensure all cables are properly and securely connected. Replace faulty cables.",
/openbmc/u-boot/post/drivers/
H A Dmemory.c16 * This sequence also helps isolate and identify what is faulty.
81 * map (related by the faulty address line) mapping to one physical
108 * not "mirrored" onto the base address due to a faulty address line.
/openbmc/phosphor-led-manager/fault-monitor/
H A Dfru-fault-monitor.hpp68 * @param[in] path - Inventory path of the faulty unit.
/openbmc/openbmc/meta-security/recipes-perl/perl/files/
H A Dlibwhisker2.patch4 Subject: [PATCH] Mandir and perl install dir were overwritten with faulty
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-graphics/glm/glm/
H A DglmTargets.cmake92 * The installation package was faulty and contained
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Common/Callout/
H A DREADME.md5 A callout is typically an indication of a faulty hardware component in a system.
/openbmc/openbmc/poky/meta/recipes-devtools/pkgconfig/
H A Dpkgconfig_git.bb25 # Because of a faulty test, the current auto mode always evaluates to no,
/openbmc/u-boot/drivers/fastboot/
H A Dfb_common.c134 * This only happens if image is somehow faulty so we start in fastboot_boot()
/openbmc/dbus-sensors/
H A DREADME.md54 is set to false if the sensor is determined to be faulty.
/openbmc/qemu/util/
H A Dcpuinfo-riscv.c22 /* Skip the faulty instruction */ in sigill_handler()
/openbmc/openbmc/poky/meta/recipes-devtools/clang/clang/
H A D0014-cmake-Fix-configure-for-packages-using-find_package.patch16 | * The installation package was faulty and contained

12