Home
last modified time | relevance | path

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

1234567

/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
/openbmc/linux/drivers/md/
H A Dmd-faulty.c3 * faulty.c : Multiple Devices driver for Linux
12 * The "faulty" personality causes some requests to fail.
30 * persisting-faulty blocks. When a new fault is requested that would
338 .name = "faulty",
363 MODULE_ALIAS("md-personality-10"); /* faulty */
364 MODULE_ALIAS("md-faulty");
H A Dmd.h75 * Not working: faulty==1 in_sync==0
76 * Fully working: faulty==0 in_sync==1
79 * faulty==0 in_sync==0
81 * It can never have faulty==1, in_sync==1
141 Faulty, /* device is known to have a fault */ enumerator
193 * this device was known to be faulty,
635 /* error_handler must set ->faulty and clear ->in_sync
836 int faulty = test_bit(Faulty, &rdev->flags); in rdev_dec_pending() local
837 if (atomic_dec_and_test(&rdev->nr_pending) && faulty) { in rdev_dec_pending()
H A DMakefile34 faulty-y += md-faulty.o
47 obj-$(CONFIG_MD_FAULTY) += faulty.o
H A Draid10.c492 * When the device is faulty, it is not necessary to in raid10_end_write_request()
495 if (!test_bit(Faulty, &rdev->flags)) in raid10_end_write_request()
519 * rebuilding or Faulty. This is because we cannot use in raid10_end_write_request()
526 !test_bit(Faulty, &rdev->flags)) in raid10_end_write_request()
773 if (rdev == NULL || test_bit(Faulty, &rdev->flags) || in read_balance()
785 test_bit(Faulty, &rdev->flags)) in read_balance()
1479 if (rdev && (test_bit(Faulty, &rdev->flags))) in raid10_write_request()
1481 if (rrdev && (test_bit(Faulty, &rrdev->flags))) in raid10_write_request()
1779 if (rdev && (test_bit(Faulty, &rdev->flags))) in raid10_handle_discard()
1781 if (rrdev && (test_bit(Faulty, &rrdev->flags))) in raid10_handle_discard()
[all …]
H A Dmd-multipath.c39 !test_bit(Faulty, &rdev->flags)) { in multipath_map()
177 set_bit(Faulty, &rdev->flags); in multipath_error()
202 i,!test_bit(Faulty, &tmp->rdev->flags), in print_multipath_conf()
383 if (!test_bit(Faulty, &rdev->flags)) in multipath_run()
H A Draid1.c474 * When the device is faulty, it is not necessary to in raid1_end_write_request()
477 if (!test_bit(Faulty, &rdev->flags)) in raid1_end_write_request()
502 * rebuilding or Faulty. This is because we cannot use in raid1_end_write_request()
509 !test_bit(Faulty, &rdev->flags)) in raid1_end_write_request()
643 || test_bit(Faulty, &rdev->flags)) in read_balance()
1412 if (!rdev || test_bit(Faulty, &rdev->flags)) in raid1_write_request()
1626 * @rdev is marked as &Faulty excluding case when array is failed and
1649 set_bit(Faulty, &rdev->flags); in raid1_error()
1681 !test_bit(Faulty, &rdev->flags), in print_conf()
1720 && !test_bit(Faulty, &repl->flags) in raid1_spare_active()
[all …]
H A Dmd.c513 !test_bit(Faulty, &rdev->flags)) { in submit_flushes()
924 if (!test_bit(Faulty, &rdev->flags) in super_written()
954 if (test_bit(Faulty, &rdev->flags)) in md_super_write()
1288 clear_bit(Faulty, &rdev->flags); in super_90_validate()
1383 set_bit(Faulty, &rdev->flags); in super_90_validate()
1496 test_bit(Faulty, &rdev2->flags)) in super_90_sync()
1512 if (test_bit(Faulty, &rdev2->flags)) in super_90_sync()
1530 /* now set the "removed" and "faulty" bits on any missing devices */ in super_90_sync()
1799 clear_bit(Faulty, &rdev->flags); in super_1_validate()
1922 * It could happen that our rdev was marked as Faulty, and all other in super_1_validate()
[all …]
/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/linux/drivers/staging/media/omap4iss/
H A Diss_ipipeif.h43 * @fpc_en: Faulty pixels correction enabled (1) or disabled (0)
46 * @fpc: Faulty pixels correction configuration
/openbmc/linux/drivers/media/platform/ti/omap3isp/
H A Dispccdc.h110 * @fpc_en: Faulty pixels correction enabled (1) or disabled (0)
113 * @fpc: Faulty pixels correction configuration
/openbmc/linux/Documentation/admin-guide/
H A Dmd.rst195 raid5, linear, multipath, faulty.
254 For arrays with data redundancy (i.e. not raid0, linear, faulty,
455 faulty
474 it were not faulty are blocked.
499 Writing ``faulty`` simulates a failure on the device.
528 This file responds to select/poll. Any change to ``faulty``
/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/openbmc/meta-openembedded/meta-oe/recipes-benchmark/memtester/
H A Dmemtester_4.6.0.bb1 SUMMARY = "Utility to test for faulty memory subsystem"
/openbmc/linux/Documentation/devicetree/bindings/power/supply/
H A Drohm,bd99954.yaml103 # battery is expected to be faulty if battery voltage exceeds this limit.
104 # Charger will then enter to a "battery faulty" -state
/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/bmcweb/redfish-core/include/registries/
H A Dpower_message_registry.hpp49 "Check the breaker hardware and replace any faulty components.",
73 … "Check the circuit and connected devices, and disconnect or replace any faulty devices.",
676 "Check the power supply hardware and replace any faulty component.",
736 "Check the power supply hardware and replace any faulty component.",
772 "Check the power supply hardware and replace any faulty component.",
/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/linux/arch/arm/mm/
H A Dabort-ev6.S25 * Faulty SWP instruction on 1136 doesn't set bit 11 in DFSR.
/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/linux/Documentation/admin-guide/media/
H A Ddvb-usb-dibusb-mb-cardlist.rst21 * - Artec T1 USB1.1 TVBOX with AN2235 (faulty USB IDs)
/openbmc/linux/include/uapi/linux/raid/
H A Dmd_p.h78 #define MD_DISK_FAULTY 0 /* disk is faulty / operational */
303 * into the 'roles' value. If a device is spare or faulty, then it doesn't
306 __le16 dev_roles[]; /* role in array, or 0xffff for a spare, or 0xfffe for faulty */
/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/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.

1234567