| /Linux-v6.1/Documentation/PCI/ |
| D | pcieaer-howto.rst | 41 - Gathers the comprehensive error information if errors occurred.
92 When PCIe AER errors are captured, the counters / statistics are also exposed
105 PCI Express errors are classified into two types: correctable errors
106 and uncorrectable errors. This classification is based on the impacts
107 of those errors, which may result in degraded performance or function
110 Correctable errors pose no impacts on the functionality of the
112 intervention or any loss of data. These errors are detected and
113 corrected by hardware. Unlike correctable errors, uncorrectable
114 errors impact functionality of the interface. Uncorrectable errors
117 errors are further classified into non-fatal errors and fatal errors.
[all …]
|
| /Linux-v6.1/tools/testing/selftests/arm64/abi/ |
| D | syscall-abi.c | 65 int errors = 0; in check_gpr() local
76 errors++; in check_gpr()
80 return errors; in check_gpr()
97 int errors = 0; in check_fpr() local
107 errors++; in check_fpr()
112 return errors; in check_fpr()
132 int errors = 0; in check_z() local
151 errors++; in check_z()
161 errors++; in check_z()
169 errors++; in check_z()
[all …]
|
| /Linux-v6.1/drivers/md/bcache/ |
| D | io.c | 55 /* IO errors */
58 unsigned int errors; in bch_count_backing_io_errors() local
74 errors = atomic_add_return(1, &dc->io_errors); in bch_count_backing_io_errors()
75 if (errors < dc->error_limit) in bch_count_backing_io_errors()
96 unsigned int errors; in bch_count_io_errors() local
102 * successfully do so, we rescale the errors once: in bch_count_io_errors()
110 errors = atomic_read(&ca->io_errors); in bch_count_io_errors()
112 old = errors; in bch_count_io_errors()
113 new = ((uint64_t) errors * 127) / 128; in bch_count_io_errors()
114 errors = atomic_cmpxchg(&ca->io_errors, in bch_count_io_errors()
[all …]
|
| /Linux-v6.1/Documentation/driver-api/soundwire/ |
| D | error_handling.rst | 5 The SoundWire PHY was designed with care and errors on the bus are going to
7 errors. Examples of this design can be found in the synchronization
8 mechanism (sync loss after two errors) and short CRCs used for the Bulk
11 The errors can be detected with multiple mechanisms:
13 1. Bus clash or parity errors: This mechanism relies on low-level detectors
15 and audio data. The current implementation only logs such errors.
17 restarting from a known position. In the case of such errors outside of a
21 and after a number of such errors are detected the bus might be reset. Note
22 that bus clashes due to programming errors (two streams using the same bit
27 not be responsible for the errors so resetting them individually is not a
[all …]
|
| /Linux-v6.1/Documentation/ABI/testing/ |
| D | sysfs-bus-pci-devices-aer_stats | 5 statistical counters indicate the errors "as seen/reported by the device".
8 errors may be "seen" / reported by the link partner and not the
16 Description: List of correctable errors seen and reported by this
17 PCI device using ERR_COR. Note that since multiple errors may
20 total of all the errors in the file. Sample output::
37 Description: List of uncorrectable fatal errors seen and reported by this
38 PCI device using ERR_FATAL. Note that since multiple errors may
41 total of all the errors in the file. Sample output::
67 Description: List of uncorrectable nonfatal errors seen and reported by this
68 PCI device using ERR_NONFATAL. Note that since multiple errors
[all …]
|
| D | sysfs-platform-dfl-fme | 48 What: /sys/bus/platform/devices/dfl-fme.0/errors/pcie0_errors
52 Description: Read-Write. Read this file for errors detected on pcie0 link.
53 Write this file to clear errors logged in pcie0_errors. Write
57 What: /sys/bus/platform/devices/dfl-fme.0/errors/pcie1_errors
61 Description: Read-Write. Read this file for errors detected on pcie1 link.
62 Write this file to clear errors logged in pcie1_errors. Write
66 What: /sys/bus/platform/devices/dfl-fme.0/errors/nonfatal_errors
70 Description: Read-only. It returns non-fatal errors detected.
72 What: /sys/bus/platform/devices/dfl-fme.0/errors/catfatal_errors
76 Description: Read-only. It returns catastrophic and fatal errors detected.
[all …]
|
| D | sysfs-mce | 8 detected by the CPU. Uncorrected errors typically cause a
45 How often to poll for corrected machine check errors, in
52 0 means no polling for corrected machine check errors
53 (but some corrected errors might be still reported
80 Disables polling and CMCI for corrected errors.
87 Disables logging for corrected errors.
88 All reported corrected errors will be cleared silently.
91 errors.
|
| /Linux-v6.1/drivers/fpga/ |
| D | dfl-afu-error.c | 30 /* mask or unmask port errors by the error mask register. */
49 /* clear port errors. */
64 * clear Port Errors in afu_port_err_clear()
68 * - Set PORT Error mask to all 1 to mask errors in afu_port_err_clear()
69 * - Clear all errors in afu_port_err_clear()
70 * - Set Port mask to all 0 to enable errors in afu_port_err_clear()
71 * - All errors start capturing new errors in afu_port_err_clear()
78 dev_err(dev, "Could not clear errors, device in AP6 state.\n"); in afu_port_err_clear()
87 /* Mask all errors */ in afu_port_err_clear()
90 /* Clear errors if err input matches with current port errors.*/ in afu_port_err_clear()
[all …]
|
| /Linux-v6.1/Documentation/ABI/removed/ |
| D | sysfs-mce | 27 0 always panic on uncorrected errors, log corrected errors
28 1 panic or SIGBUS on uncorrected errors, log corrected errors
29 2 SIGBUS or log uncorrected errors, log corrected errors
30 3 never panic or SIGBUS, log all errors (for testing only)
|
| /Linux-v6.1/Documentation/driver-api/ |
| D | libata.rst | 403 This chapter describes how errors are handled under libata. Readers are
569 Errors which aren't ATA device errors are treated as ATA device
570 errors by setting ATA_ERR bit. Better error descriptor which can
571 properly represent ATA and other errors/exceptions is needed.
582 errors and other errors quite often require reset to return to known
586 - ATA errors are directly handled in the interrupt handler and PIO
587 errors in pio_task. This is problematic for advanced error handling
626 ATA errors and exceptions
637 which are not errors (say, power or hotplug events), or to describe both
638 errors and non-error exceptional conditions. Where explicit distinction
[all …]
|
| /Linux-v6.1/tools/testing/selftests/bpf/ |
| D | test_tunnel.sh | 637 local errors=0
641 errors=$(( $errors + $? ))
645 errors=$(( $errors + $? ))
649 errors=$(( $errors + $? ))
653 errors=$(( $errors + $? ))
657 errors=$(( $errors + $? ))
661 errors=$(( $errors + $? ))
665 errors=$(( $errors + $? ))
669 errors=$(( $errors + $? ))
673 errors=$(( $errors + $? ))
[all …]
|
| /Linux-v6.1/include/uapi/linux/ |
| D | sonet.h | 11 __HANDLE_ITEM(section_bip); /* section parity errors (B1) */ \
12 __HANDLE_ITEM(line_bip); /* line parity errors (B2) */ \
13 __HANDLE_ITEM(path_bip); /* path parity errors (B3) */ \
14 __HANDLE_ITEM(line_febe); /* line parity errors at remote */ \
15 __HANDLE_ITEM(path_febe); /* path parity errors at remote */ \
16 __HANDLE_ITEM(corr_hcs); /* correctable header errors */ \
17 __HANDLE_ITEM(uncorr_hcs); /* uncorrectable header errors */ \
|
| /Linux-v6.1/drivers/net/ethernet/pasemi/ |
| D | pasemi_mac_ethtool.c | 24 { "rx-crc-errors" },
25 { "rx-undersize-errors" },
26 { "rx-oversize-errors" },
27 { "rx-short-fragment-errors" },
28 { "rx-jabber-errors" },
43 { "tx-crc-errors" },
44 { "tx-undersize-errors" },
45 { "tx-oversize-errors" },
|
| /Linux-v6.1/arch/sparc/include/asm/ |
| D | hypervisor.h | 88 * ERRORS: This service does not return.
118 * ERRORS: HV_EBADALIGN Buffer is badly aligned
143 * ERRORS: This service does not return.
242 * ERRORS: ENOCPU Invalid CPU ID
269 * ERRORS: ENOCPU Invalid CPU ID
293 * ERRORS: No possible error.
310 * ERRORS: ENOCPU cpuid refers to a CPU that does not exist
331 * ERRORS: ENORADDR Invalid base real address
379 * ERRORS: EINVAL Invalid queue
397 * ERRORS: EBADALIGN Mondo data is not 64-byte aligned or CPU list
[all …]
|
| D | estate.h | 15 * errors 2) uncorrectable E-cache errors. Such events only occur on reads
23 * for uncorrectable ECC errors and system errors.
31 * 4) As the result of such errors on instruction vector fetch can generate any
38 /* CEEN enables the ECC_error trap for hardware corrected ECC errors. System bus
|
| /Linux-v6.1/drivers/ufs/core/ |
| D | ufs-debugfs.c | 42 PRT("PHY Adapter Layer errors (except LINERESET): %llu\n", PA_ERR); in ufs_debugfs_stats_show()
43 PRT("Data Link Layer errors: %llu\n", DL_ERR); in ufs_debugfs_stats_show()
44 PRT("Network Layer errors: %llu\n", NL_ERR); in ufs_debugfs_stats_show()
45 PRT("Transport Layer errors: %llu\n", TL_ERR); in ufs_debugfs_stats_show()
46 PRT("Generic DME errors: %llu\n", DME_ERR); in ufs_debugfs_stats_show()
47 PRT("Auto-hibernate errors: %llu\n", AUTO_HIBERN8_ERR); in ufs_debugfs_stats_show()
48 PRT("IS Fatal errors (CEFES, SBFES, HCFES, DFES): %llu\n", FATAL_ERR); in ufs_debugfs_stats_show()
49 PRT("DME Link Startup errors: %llu\n", LINK_STARTUP_FAIL); in ufs_debugfs_stats_show()
50 PRT("PM Resume errors: %llu\n", RESUME_ERR); in ufs_debugfs_stats_show()
51 PRT("PM Suspend errors : %llu\n", SUSPEND_ERR); in ufs_debugfs_stats_show()
|
| /Linux-v6.1/Documentation/filesystems/ |
| D | zonefs.rst | 179 additional conditions that result in I/O errors.
198 * Unaligned write errors: These errors result from the host issuing write
201 enforces sequential file write for sequential zones, unaligned write errors
208 * Delayed write errors: similarly to regular block devices, if the device side
209 write cache is enabled, write errors may occur in ranges of previously
212 errors can propagate through a stream of cached sequential data for a zone
215 All I/O errors detected by zonefs are notified to the user with an error code
217 actions taken by zonefs in response to I/O errors depend on the I/O type (read
221 * For read I/O errors, zonefs does not execute any particular recovery action,
226 * For write I/O errors, zonefs I/O error recovery is always executed.
[all …]
|
| D | ocfs2-online-filecheck.rst | 15 Then, a mount option (errors=continue) is introduced, which would return the
42 When there are errors in the OCFS2 filesystem, they are usually accompanied
68 <ERROR> says what kind of errors was found. For the detailed error numbers,
92 file metadata. In case of errors, the filesystem would fix the errors
94 the inode must first be checked for errors before performing a final fix.
98 fixed/checked, the detailed errors which were fixed/checked are printed in the
|
| /Linux-v6.1/Documentation/admin-guide/ |
| D | ras.rst | 36 hardware errors, and, when possible correcting them in runtime. It should
43 * CPU – detect errors at instruction execution and at L1/L2/L3 caches;
44 * Memory – add error correction logic (ECC) to detect and correct errors;
50 to identify if the probability of hardware errors is increasing, and, on such
52 those errors are correctable.
54 Types of errors
58 Codes that allow error correction when the number of errors on a bit packet
59 is below a threshold. If the number of errors is above, those mechanisms
66 That defines some categories of errors:
69 corrected the error. Such errors are usually not fatal, although some
[all …]
|
| /Linux-v6.1/drivers/scsi/csiostor/ |
| D | csio_scsi.h | 97 * ready errors
100 * ready errors
104 * errors.
107 uint32_t n_busy_error; /* No. of -EBUSY errors */
109 uint32_t n_rsperror; /* No. of response errors */
111 uint32_t n_ovflerror; /* No. of overflow errors */
112 uint32_t n_unflerror; /* No. of underflow errors */
114 * ready errors
116 uint32_t n_rdev_lost_error;/* No. of rdev lost errors */
117 uint32_t n_rdev_logo_error;/* No. of rdev logo errors */
[all …]
|
| /Linux-v6.1/drivers/mtd/tests/ |
| D | nandbiterrs.c | 11 * 0 - artificially inserting bit errors until the ECC fails
18 * Depending on the NAND, the first bit errors will appear after
23 * exceptionally good and not generate bit errors before that. Try
55 MODULE_PARM_DESC(mode, "0=incremental errors, 1=overwrite test");
126 /* Reads page into rbuffer. Returns number of corrected bit errors (>=0)
199 * errors into the page, while verifying each step. */
223 pr_info("Read reported %d corrected bit errors\n", err); in incremental_errors_test()
237 pr_info("Successfully corrected %d bit errors per subpage\n", in incremental_errors_test()
254 This eventually develops bit errors (bits written as '1' will slowly become
262 /* We don't expect more than this many correctable bit errors per in overwrite_test()
[all …]
|
| /Linux-v6.1/tools/testing/selftests/arm64/fp/ |
| D | sve-ptrace.c | 251 uint32_t *in, uint32_t *out, int *errors) in check_u32() argument
256 (*errors)++; in check_u32()
328 int errors = 0; in ptrace_set_sve_get_sve_data() local
386 errors++; in ptrace_set_sve_get_sve_data()
395 errors++; in ptrace_set_sve_get_sve_data()
400 read_buf + SVE_PT_SVE_FPSR_OFFSET(vq), &errors); in ptrace_set_sve_get_sve_data()
402 read_buf + SVE_PT_SVE_FPCR_OFFSET(vq), &errors); in ptrace_set_sve_get_sve_data()
404 ksft_test_result(errors == 0, "Set and get %s data for VL %u\n", in ptrace_set_sve_get_sve_data()
424 int errors = 0; in ptrace_set_sve_get_fpsimd_data() local
480 errors++; in ptrace_set_sve_get_fpsimd_data()
[all …]
|
| /Linux-v6.1/drivers/acpi/apei/ |
| D | Kconfig | 15 APEI allows to report errors (for example from the chipset)
28 platform hardware errors (such as that from chipset). It
30 errors are reported to firmware firstly, then reported to
40 PCIe AER errors may be reported via APEI firmware first mode.
52 Memory errors may be reported via APEI firmware first mode.
|
| /Linux-v6.1/drivers/macintosh/ |
| D | windfarm_pid.c | 46 st->errors[i] = error; in wf_pid_run()
53 st->errors[st->index] = error; in wf_pid_run()
58 integ += st->errors[(st->index + hlen - i) % hlen]; in wf_pid_run()
62 deriv = st->errors[st->index] - in wf_pid_run()
63 st->errors[(st->index + hlen - 1) % hlen]; in wf_pid_run()
101 st->errors[i] = error; in wf_cpu_pid_run()
109 st->errors[st->index] = error; in wf_cpu_pid_run()
116 integ += st->errors[(st->index + hlen - i) % hlen]; in wf_cpu_pid_run()
|
| /Linux-v6.1/arch/alpha/include/asm/ |
| D | mce.h | 20 /* Machine Check Frame for uncorrectable errors (Large format)
21 * --- This is used to log uncorrectable errors such as
22 * double bit ECC errors.
23 * --- These errors are detected by both processor and systems.
43 fault or D-cache parity errors */
52 unsigned long fill_syndrome; /* For correcting ECC errors. */
|
