Searched full:errors (Results 1 – 25 of 511) sorted by relevance
12345678910>>...21
| /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 …]
|
| /Documentation/PCI/ |
| D | pcieaer-howto.rst | 41 - Gathers the comprehensive error information if errors occurred.
91 When PCIe AER errors are captured, the counters / statistics are also exposed
102 PCIe errors are classified into two types: correctable errors
103 and uncorrectable errors. This classification is based on the impact
104 of those errors, which may result in degraded performance or function
107 Correctable errors pose no impacts on the functionality of the
109 intervention or any loss of data. These errors are detected and
112 Unlike correctable errors, uncorrectable
113 errors impact functionality of the interface. Uncorrectable errors
116 errors are further classified into non-fatal errors and fatal errors.
[all …]
|
| /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)
|
| /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-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.
|
| 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-fs-ubifs | 6 Exposes magic errors: every node starts with a magic number.
18 Exposes node errors. Every node embeds its type.
30 Exposes crc errors: every node embeds a crc checksum.
|
| D | debugfs-pfo-nx-crypto | 13 errors:
14 A u32 providing a total count of errors since the driver was loaded. The
15 only errors counted here are those returned from the hcall, H_COP_OP.
|
| D | sysfs-platform-dfl-port | 78 What: /sys/bus/platform/devices/dfl-port.0/errors/errors
82 Description: Read-Write. Read this file to get errors detected on port and
84 to clear errors. Write fails with -EINVAL if input parsing
89 What: /sys/bus/platform/devices/dfl-port.0/errors/first_error
96 What: /sys/bus/platform/devices/dfl-port.0/errors/first_malformed_req
|
| D | sysfs-devices-edac | 5 counters for UE and CE errors on the given memory controller.
8 computing errors/time. Since the counters are always reset
35 errors that have occurred on this memory controller. If
44 which DIMM slot is having errors.
50 errors that have occurred on this memory controller. This
61 information as to which DIMM slot is having errors. Memory is
117 to it. With this label in the module, when errors occur
146 errors that have occurred on this DIMM. This count is very important
155 errors that have occurred on this DIMM. If panic_on_ue is set, this
|
| D | sysfs-driver-qat_ras | 5 Description: (RO) Reports the number of correctable errors detected by the device.
13 Description: (RO) Reports the number of non fatal errors detected by the device.
21 Description: (RO) Reports the number of fatal errors detected by the device.
|
| D | sysfs-bus-mdio | 18 What: /sys/bus/mdio_bus/devices/.../statistics/errors
19 What: /sys/class/mdio_bus/.../statistics/errors
24 Total number of transfer errors for this MDIO bus.
56 Total number of transfer errors for this MDIO bus address.
|
| D | sysfs-class-fpga-manager | 46 programming errors to userspace. This is a list of strings for
52 with errors not cleared
57 * reconfig IP protocol error - protocol errors detected by
|
| /Documentation/filesystems/ |
| 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
|
| 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 …]
|
| /Documentation/driver-api/ |
| D | libata.rst | 378 This chapter describes how errors are handled under libata. Readers are
543 Errors which aren't ATA device errors are treated as ATA device
544 errors by setting ATA_ERR bit. Better error descriptor which can
545 properly represent ATA and other errors/exceptions is needed.
556 errors and other errors quite often require reset to return to known
560 - ATA errors are directly handled in the interrupt handler and PIO
561 errors in pio_task. This is problematic for advanced error handling
600 ATA errors and exceptions
611 which are not errors (say, power or hotplug events), or to describe both
612 errors and non-error exceptional conditions. Where explicit distinction
[all …]
|
| /Documentation/devicetree/bindings/arm/tegra/ |
| D | nvidia,tegra194-cbb.yaml | 18 This driver handles errors due to illegal register accesses reported
19 by the NOCs inside the CBB. NOCs reporting errors are cluster NOCs
29 errors due to illegal accesses from CCPLEX are reported by interrupts.
60 A secure interrupt is received for SEC(firewall) & SLV errors and a
61 non-secure interrupt is received for TMO & DEC errors.
|
| /Documentation/networking/ |
| D | xfrm_proc.rst | 19 Inbound errors
23 All errors which is not matched others
79 Outbound errors
82 All errors which is not matched others
|
| /Documentation/admin-guide/RAS/ |
| D | main.rst | 40 hardware errors, and, when possible correcting them in runtime. It should
47 * CPU – detect errors at instruction execution and at L1/L2/L3 caches;
48 * Memory – add error correction logic (ECC) to detect and correct errors;
54 to identify if the probability of hardware errors is increasing, and, on such
56 those errors are correctable.
58 Types of errors
62 Codes that allow error correction when the number of errors on a bit packet
63 is below a threshold. If the number of errors is above, those mechanisms
70 That defines some categories of errors:
73 corrected the error. Such errors are usually not fatal, although some
[all …]
|
| D | error-decoding.rst | 13 errors. If not, one can still decode such errors by supplying the
|
| /Documentation/admin-guide/ |
| D | filesystem-monitoring.rst | 23 errors to cascade after the initial failure, hiding the original failure
27 it simply counts additional errors. This ensures that the most
67 `error_count` tracks the number of errors that occurred and were
77 procedure. Errors that are not related to an inode are reported with an
|
| D | jfs.rst | 36 errors=continue
38 errors=remount-ro(*)
40 errors=panic
|
| /Documentation/ |
| D | Kconfig | 16 bool "Warn if there are errors at ABI files"
21 have errors that would break them for being parsed by
|
| /Documentation/userspace-api/gpio/ |
| D | error-codes.rst | 9 .. _gpio-errors:
74 Since errors may have side effects such as a driver reset,
75 applications should abort on unexpected errors, or otherwise
|
| /Documentation/devicetree/bindings/memory-controllers/ |
| D | xlnx,zynq-ddrc-a05.yaml | 15 (16-bit) configuration. It is capable of correcting single bit ECC errors
16 and detecting double bit ECC errors.
|
12345678910>>...21