/openbmc/u-boot/lib/efi_selftest/ |
H A D | efi_selftest.c | 73 * @failures counter that will be incremented if a failure occurs 76 static int setup(struct efi_unit_test *test, unsigned int *failures) in setup() argument 86 ++*failures; in setup() 98 * @failures counter that will be incremented if a failure occurs 101 static int execute(struct efi_unit_test *test, unsigned int *failures) in execute() argument 111 ++*failures; in execute() 123 * @failures counter that will be incremented if a failure occurs 126 static int teardown(struct efi_unit_test *test, unsigned int *failures) in teardown() argument 136 ++*failures; in teardown() 185 * failures returns EFI_ST_SUCCESS if all test steps succeeded [all …]
|
/openbmc/linux/lib/ |
H A D | test_meminit.c | 20 if (failures) \ 22 __func__, failures, num_tests); \ 93 int failures = 0, num_tests = 0; in test_pages() local 97 num_tests += do_alloc_pages_order(i, &failures); in test_pages() 100 *total_failures += failures; in test_pages() 155 int failures = 0, num_tests = 0; in test_kvmalloc() local 160 num_tests += do_kmalloc_size(size, &failures); in test_kvmalloc() 161 num_tests += do_vmalloc_size(size, &failures); in test_kvmalloc() 165 *total_failures += failures; in test_kvmalloc() 380 int failures = 0, num_tests = 0; in test_kmemcache() local [all …]
|
/openbmc/openbmc/poky/meta/classes/ |
H A D | report-error.bbclass | 74 data['failures'] = [] 100 # server will refuse failures longer than param specified in project.settings.py 110 jsondata['failures'].append(taskdata) 119 data['failures'] = [] 125 data['failures'].append(taskdata) 135 data['failures'] = [] 140 data['failures'].append(taskdata) 149 failures = jsondata['failures'] 150 if(len(failures) > 0):
|
/openbmc/linux/tools/testing/selftests/kvm/x86_64/ |
H A D | tsc_scaling_sync.c | 46 unsigned long failures = 0; in run_vcpu() local 75 failures++; in run_vcpu() 83 return (void *)failures; in run_vcpu() 99 unsigned long failures = 0; in main() local 103 failures += (unsigned long)this_cpu_failures; in main() 106 TEST_ASSERT(!failures, "TSC sync failed"); in main()
|
/openbmc/openpower-sbe-interface/ |
H A D | sbe_chipOp_handler.hpp | 22 * device and obtain the expected response .Internal device driver failures 26 * - Device driver internal failures 47 * - SBE Internal failures 60 * exception for any SBE internal failures. 63 * - Device driver failures 64 * - SBE internal failures
|
/openbmc/gpioplus/src/gpioplus/internal/ |
H A D | fd.hpp | 23 * @throws std::system_error for underlying syscall failures 32 * @throws std::system_error for underlying syscall failures 72 * @throws std::system_error for underlying syscall failures 78 * @throws std::system_error for underlying syscall failures 85 * @throws std::system_error for underlying syscall failures
|
/openbmc/linux/drivers/scsi/snic/ |
H A D | snic_stats.h | 17 atomic64_t fail; /* IO Failures */ 19 atomic64_t alloc_fail; /* Alloc Failures */ 36 atomic64_t dev_reset_fail; /* Device Reset Failures */ 42 atomic64_t hba_reset_fail; /* hba/firmware failures */ 45 atomic64_t snic_reset_fail; /* snic reset failures */
|
/openbmc/u-boot/test/ |
H A D | run | 13 [ $? -ne 0 ] && failures=$((failures+1)) 19 failures=0 56 if [ $failures == 0 ]; then
|
/openbmc/linux/Documentation/mm/ |
H A D | hwpoison.rst | 29 users, because memory failures could happen anytime and anywhere, 51 memory failures too. The expectation is that most applications 60 All memory failures cause a panic. Do not attempt recovery. 121 injected failures, not for real memory failures. Once any hardware 128 Only handle memory failures to pages associated with the file
|
/openbmc/linux/kernel/module/ |
H A D | stats.c | 29 * loading failures to enable improvements either for kernel module auto-loading 31 * provided to track all possible failures in the finit_module() path and memory 57 * failures. 114 * failures: 120 * * invalid_kread_bytes: bytes allocated and then freed on failures which 131 * failures can happen if we had a check in between a successful kernel_read_file_from_fd() 144 * to begin to process prior requests. Although duplicate failures can be 151 * failures. These failures can occur because: 164 * freed due to failures after we did all the sanity checks of the module 185 * private space for our module using layout_and_allocate(). These failures [all …]
|
/openbmc/linux/Documentation/fault-injection/ |
H A D | fault-injection.rst | 13 injects slab allocation failures. (kmalloc(), kmem_cache_alloc(), ...) 17 injects page allocation failures. (alloc_pages(), get_free_pages(), ...) 21 injects failures in user memory access functions. (copy_from_user(), get_user(), ...) 29 injects kernel RPC client and server failures. 85 specifies the interval between failures, for calls to 93 specifies how many times failures may happen at most. A value of -1 116 Any positive value limits failures to only processes indicated by 141 default is 'Y', setting it to 'N' will also inject failures into 149 default is 'Y', setting it to 'N' will also inject failures 155 failures. [all …]
|
/openbmc/openbmc/poky/scripts/lib/resulttool/ |
H A D | junit.py | 18 failures = 0 30 failures += 1 42 testsuite_node.set("failures", "%s" % failures)
|
/openbmc/linux/tools/testing/fault-injection/ |
H A D | failcmd.sh | 5 # failcmd.sh - run a command with injecting slab/page allocation failures 12 # Run command with injecting slab/page allocation failures by fault 31 specifies how many times failures may happen at most. 59 inject slab allocation failures 61 inject page allocation failures
|
/openbmc/openbmc/poky/scripts/contrib/ |
H A D | devtool-stress.py | 105 failures = 0 131 failures += 1 140 if failures: 151 failures = 0 194 failures += 1 203 if failures:
|
/openbmc/openbmc/poky/meta/lib/oeqa/core/ |
H A D | runner.py | 72 # Print the errors/failures early to aid/speed debugging, its a pain 74 for t in ['failures', 'errors', 'skipped', 'expectedFailures']: 92 …g += " (successes=%d, skipped=%d, failures=%d, errors=%d)" % (len(self.successes), len(self.skippe… 96 result_types = {'failures': 'FAILED', 'errors': 'ERROR', 'skipped': 'SKIPPED', 197 # Class setup failures wouldn't enter stopTest so would never display 235 # Override as we unexpected successes aren't failures for us 236 return (len(self.failures) == len(self.errors) == 0) 239 # Account for expected failures
|
/openbmc/gpioplus/src/gpioplus/ |
H A D | handle.hpp | 78 * @throws std::system_error for underlying syscall failures 91 * @throws std::system_error for underlying syscall failures 99 * @throws std::system_error for underlying syscall failures 106 * @throws std::system_error for underlying syscall failures
|
H A D | event.hpp | 68 * @throws std::system_error for underlying syscall failures 82 * @throws std::system_error for underlying syscall failures 90 * @throws std::system_error for underlying syscall failures
|
/openbmc/u-boot/test/py/tests/ |
H A D | test_efi_selftest.py | 19 m = u_boot_console.p.expect(['Summary: 0 failures', 'Press any key']) 21 raise Exception('Failures occurred during the EFI selftest') 119 m = u_boot_console.p.expect(['Summary: 0 failures', 'Press any key']) 121 raise Exception('Failures occurred during the EFI selftest') 198 m = u_boot_console.p.expect(['Summary: 0 failures', 'Press any key']) 200 raise Exception('Failures occurred during the EFI selftest')
|
/openbmc/qemu/linux-user/ |
H A D | linuxload.c | 107 /* FIXME - handle put_user() failures */ in loader_build_argptr() 115 /* FIXME - handle put_user() failures */ in loader_build_argptr() 120 /* FIXME - handle put_user() failures */ in loader_build_argptr() 125 /* FIXME - handle put_user() failures */ in loader_build_argptr() 130 /* FIXME - handle put_user() failures */ in loader_build_argptr() 135 /* FIXME - handle put_user() failures */ in loader_build_argptr()
|
/openbmc/qemu/bsd-user/ |
H A D | bsdload.c | 110 /* FIXME - handle put_user() failures */ in loader_build_argptr() 114 /* FIXME - handle put_user() failures */ in loader_build_argptr() 119 /* FIXME - handle put_user() failures */ in loader_build_argptr() 122 /* FIXME - handle put_user() failures */ in loader_build_argptr() 127 /* FIXME - handle put_user() failures */ in loader_build_argptr()
|
/openbmc/linux/include/linux/ |
H A D | hte.h | 122 * non-zero for failures. 124 * non-zero for failures. 126 * non-zero for failures. 128 * non-zero for failures. 155 * physical ids, return 0 for the success and negative for the failures.
|
/openbmc/openbmc/meta-phosphor/recipes-phosphor/chassis/ |
H A D | obmc-host-failure-reboots.bb | 1 SUMMARY = "Enables reboots on host failures" 3 on host failures"
|
/openbmc/docs/designs/ |
H A D | bmc-service-failure-debug-and-recovery.md | 11 The capability to debug critical failures of the BMC firmware is essential to 14 This design addresses a few classes of failures: 32 As such, failures of BMC subsystems may impact external consumers. 38 Complexity and coupling drive concern around the risk of critical failures in 100 Failures of platform data transports generally leave out-of-band interfaces 152 ## Handling platform-data-transport-provider failures 165 …| Graceful reboot request | Normal circumstances or recovery from platform data provider failures | 442 ## Handling platform-data-provider failures 446 As noted above, these types of failures usually yield a system that can continue 476 failures and do the following when one fails from within the configuration
|
/openbmc/ibm-logging/ |
H A D | dbus.hpp | 41 * Returns an empty map if there are any failures. 57 * Returns an empty map if there are any failures. 88 * Returns an empty map if there are any failures.
|
/openbmc/phosphor-hwmon/ |
H A D | meson.options | 8 description: 'Set sensor value to -errno on read failures.', 20 …description: 'Update functional property on read failures. Incompatible with negative-errno-on-fa…
|