| /openbmc/qemu/docs/system/devices/ |
| H A D | net.rst | 183 As passt runs with no privileges, it relies on passt-repair to save and 185 The passt-repair helper needs to have the CAP_NET_ADMIN capability, or run as root. If passt-repair… 190 Before being able to run passt-repair, the CAP_NET_ADMIN capability must be set 193 setcap cap_net_admin+eip ./passt-repair 197 passt --vhost-user --socket ~/passt_src.socket --repair-path ~/passt-repair_src.socket 200 communicate with passt-repair. The default value is the ``--socket`` path 201 appended with ``.repair``. 203 Start passt-repair:: 205 passt-repair ~/passt-repair_src.socket 214 passt --vhost-user --socket ~/passt_dst.socket --repair-path ~/passt-repair_dst.socket [all …]
|
| /openbmc/openbmc/poky/meta/recipes-extended/watchdog/watchdog-config/ |
| H A D | watchdog.conf | 18 #repair-binary = /usr/sbin/repair 19 #repair-timeout =
|
| /openbmc/phosphor-dbus-interfaces/yaml/com/ibm/ipzvpd/ |
| H A D | VER0.interface.yaml | 2 Implement to represent the VER0 record (contains vendor repair data) in IPZ 12 The "#I" keyword. Contains the repair data.
|
| H A D | VEIR.interface.yaml | 2 Implement to represent the VEIR record (contains elastic interface repair 12 The "#I" keyword. Contains the repair data.
|
| H A D | MER0.interface.yaml | 2 Implement to represent the MER0 record (contains manufacturing repair data) 12 The "#I" keyword. Contains the repair data.
|
| H A D | VWML.interface.yaml | 19 The "#I" keyword.Contains the repair data.
|
| H A D | CP00.interface.yaml | 27 The "#R" keyword.Array repair Data.
|
| /openbmc/openbmc/meta-openembedded/meta-filesystems/recipes-utils/fatcat/ |
| H A D | fatcat_1.1.1.bb | 1 SUMMARY = "FAT filesystems explore, extract, repair, and forensic tool" 3 explore, extract, repair, recover and forensic them. It currently supports \
|
| /openbmc/qemu/tests/qemu-iotests/tests/ |
| H A D | parallels-checks.out | 21 == repair image == 49 == repair image == 88 == check the first cluster with self-repair == 115 == TEST DATA_OFF THROUGH REPAIR == 120 == repair image ==
|
| H A D | parallels-checks | 87 echo "== repair image ==" 117 echo "== repair image ==" 156 echo "== check the first cluster with self-repair ==" 188 echo "== TEST DATA_OFF THROUGH REPAIR ==" 196 echo "== repair image =="
|
| /openbmc/openbmc/meta-openembedded/meta-filesystems/recipes-utils/xfsprogs/ |
| H A D | xfsprogs_6.6.0.bb | 19 PACKAGES =+ "${PN}-fsck ${PN}-mkfs ${PN}-repair libhandle" 23 RDEPENDS:${PN} = "${PN}-fsck ${PN}-mkfs ${PN}-repair" 27 FILES:${PN}-repair = "${base_sbindir}/xfs_repair"
|
| /openbmc/qemu/tests/qemu-iotests/ |
| H A D | 060 | 57 # The repair process will create a large file - so check for availability first 267 # Repair the image 280 # Repair the image 289 # Repair the image 301 # Repair the image 310 # Repair the image 335 # The actual repair should have happened (because of the dirty bit), 371 # Fails the first repair because the corruption prevents the check 438 # Fails the first repair because the corruption prevents the check
|
| H A D | 039 | 96 echo "== Data should still be accessible after repair ==" 101 echo "== Opening a dirty image read/write should repair it =="
|
| H A D | 039.out | 41 == Data should still be accessible after repair == 45 == Opening a dirty image read/write should repair it ==
|
| H A D | 036.out | 33 === Repair image ===
|
| H A D | 217 | 82 # As there are only leaks, this should be able to fully repair the
|
| /openbmc/u-boot/arch/arm/mach-tegra/tegra124/ |
| H A D | cpu.c | 114 * Request the Flow Controller perform RAM repair whenever it turns on in tegra124_ram_repair() 115 * a power rail that requires RAM repair. in tegra124_ram_repair() 119 /* Request SW trigerred RAM repair by setting req bit */ in tegra124_ram_repair() 129 debug("Ram Repair cluster0 failed\n"); in tegra124_ram_repair() 141 debug("Ram Repair cluster1 failed\n"); in tegra124_ram_repair()
|
| /openbmc/openbmc/meta-openembedded/meta-oe/dynamic-layers/meta-python/recipes-connectivity/lirc/lirc/ |
| H A D | 0001-Unbolt-ubuntu-hack.patch | 21 dnl Ubuntu's systemd pkg-config seems broken beyond repair. So:
|
| /openbmc/openbmc/poky/meta/recipes-core/initscripts/initscripts-1.0/ |
| H A D | checkfs.sh | 44 echo "fsck failed. Please repair manually."
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | Bahyph | 7 …ility of such damages. If any such situation arises, you responsible for repair. Use of this softw…
|
| H A D | GCR-docs | 22 THE COST OF ALL NECESSARY REPAIR OR CORRECTION.
|
| H A D | SAX-PD | 10 …. Should SAX prove defective, you assume the cost of all necessary servicing, repair or correction.
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/HardwareIsolation/ |
| H A D | Entry.interface.yaml | 41 Critical hardware to repair or replace.
|
| /openbmc/docs/designs/ |
| H A D | hw-fault-monitor.md | 26 criteria trigger repair actions in the host BIOS or kernel. In addition, the 27 hardware fault monitor could receive repair action requests via Redfish from 167 of any repair actions that need to be triggered based on the latest fault
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/monit/ |
| H A D | monit_5.35.2.bb | 3 Monit conducts automatic maintenance and repair and can execute meaningful \
|