Searched full:errors (Results 1 – 25 of 434) sorted by relevance
12345678910>>...18
| /Documentation/ABI/testing/ |
| 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-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:
38 Description: List of uncorrectable fatal errors seen and reported by this
39 PCI device using ERR_FATAL. Note that since multiple errors may
42 total of all the errors in the file. Sample output:
69 Description: List of uncorrectable nonfatal errors seen and reported by this
70 PCI device using ERR_NONFATAL. Note that since multiple errors
[all …]
|
| 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-class-fpga-manager | 47 programming errors to userspace. This is a list of strings for
53 with errors not cleared
58 * reconfig IP protocol error - protocol errors detected by
|
| D | sysfs-class-net-statistics | 59 Indicates the number of receive FIFO errors seen by this
69 alignment errors. Note that the specific meaning depends on
136 because of carrier errors (e.g: physical link down). See the
181 reported as heartbeat errors. See the driver for the exact
201 late collisions errors.
|
| /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/x86/x86_64/ |
| D | machinecheck.rst | 8 by the CPU. Uncorrected errors typically cause a machine check
17 When you see the "Machine check errors logged" message in the system
40 How often to poll for corrected machine check errors, in seconds
47 check errors (but some corrected errors might be still reported
60 0: always panic on uncorrected errors, log corrected errors
61 1: panic or SIGBUS on uncorrected errors, log corrected errors
62 2: SIGBUS or log uncorrected errors, log corrected errors
63 3: never panic or SIGBUS, log all errors (for testing only)
|
| D | boot-options.rst | 25 Don't make logs for corrected errors. All events reported
28 of corrected errors.
30 Disable features for corrected errors, e.g. polling timer
34 there is an agent checking/clearing corrected errors
52 0: always panic on uncorrected errors, log corrected errors
53 1: panic or SIGBUS on uncorrected errors, log corrected errors
54 2: SIGBUS or log uncorrected errors, log corrected errors
55 3: never panic or SIGBUS, log all errors (for testing only)
67 errors since we will not see details for all errors.
204 Disable firmware first mode for corrected errors. This
|
| /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 …]
|
| /Documentation/filesystems/ |
| D | ocfs2-online-filecheck.txt | 12 Then, a mount option (errors=continue) is introduced, which would return the
39 When there are errors in the OCFS2 filesystem, they are usually accompanied
64 <ERROR> says what kind of errors was found. For the detailed error numbers,
87 file metadata. In case of errors, the filesystem would fix the errors
89 the inode must first be checked for errors before performing a final fix.
93 fixed/checked, the detailed errors which were fixed/checked are printed in the
|
| /Documentation/networking/ |
| D | xfrm_proc.txt | 15 Inbound errors
18 All errors which is not matched others
56 Outbound errors
59 All errors which is not matched others
|
| /Documentation/driver-api/ |
| D | libata.rst | 403 This chapter describes how errors are handled under libata. Readers are
580 Errors which aren't ATA device errors are treated as ATA device
581 errors by setting ATA_ERR bit. Better error descriptor which can
582 properly represent ATA and other errors/exceptions is needed.
593 errors and other errors quite often require reset to return to known
597 - ATA errors are directly handled in the interrupt handler and PIO
598 errors in pio_task. This is problematic for advanced error handling
637 ATA errors and exceptions
648 which are not errors (say, power or hotplug events), or to describe both
649 errors and non-error exceptional conditions. Where explicit distinction
[all …]
|
| /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 …]
|
| D | jfs.rst | 36 errors=continue
38 errors=remount-ro(*)
40 errors=panic
|
| /Documentation/virt/kvm/devices/ |
| D | arm-vgic.txt | 30 Errors:
61 Errors:
103 Errors:
113 Errors:
123 Errors:
|
| D | xive.txt | 73 Errors: none
79 Errors: none
90 Errors:
107 Errors:
142 Errors:
155 Errors:
|
| /Documentation/devicetree/bindings/memory-controllers/ |
| D | synopsys.txt | 9 These both ECC controllers correct single bit ECC errors and detect double bit
10 ECC errors.
|
| /Documentation/firmware-guide/acpi/apei/ |
| D | einj.rst | 72 write should be the last step when injecting errors.
122 in controlling where the errors are injected. Your BIOS may support an
129 the target of the injection. For processor-related errors (type 0x1, 0x2
139 For memory errors (type 0x8, 0x10 and 0x20) the address is set using
141 express errors (type 0x40, 0x80 and 0x100) the segment, bus, device and
152 An ACPI 5.0 BIOS may also allow vendor-specific errors to be injected.
166 # cat available_error_type # See which errors can be injected
|
| /Documentation/core-api/ |
| D | errseq.rst | 5 An errseq_t is a way of recording errors in one place, and allowing any
9 The initial use case for this is tracking errors for file
18 Note that there is a risk of collisions if new errors are being recorded
36 any new errors have occurred since that sampling was done, and atomically
38 record errors in one place, and then have a number of "watchers" that
66 errseq_t wd_err; /* for recording errors */
|
| /Documentation/ide/ |
| D | ChangeLog.ide-cd.1994-2004 | 32 * of ATAPI errors.
55 * Suppress printing normal unit attention errors and
56 * some drive not ready errors.
67 * Fix handling of errors occurring before the
140 * Fix errors on CDROMSTOP (If you have a "Dolphin",
168 * removed this support because it produced errors.
169 * It produced errors _only_ for non-writers. duh.
234 * sense errors are handled.
247 * - Stop spewing errors to log when magicdev polls with
|
| /Documentation/media/uapi/ |
| D | gen-errors.rst | 17 .. _gen-errors:
98 Since errors may have side effects such as a driver reset,
99 applications should abort on unexpected errors, or otherwise
|
| /Documentation/powerpc/ |
| D | eeh-pci-error-recovery.rst | 16 hardware features allow PCI bus errors to be cleared and a PCI
23 Another "traditional" technique is to ignore such errors, which
27 reliable and robust by protecting it from PCI errors, and giving
34 Causes of EEH Errors
38 electrical connections. The vast majority of EEH errors seen in
49 years. Other possible causes of EEH errors include data or
50 address line parity errors (for example, due to poor electrical
52 errors (due to software, device firmware, or device PCI hardware bugs).
60 and recover from EEH errors will be presented. This is followed
318 Reiserfs does not tolerate errors returned from the block device.
|
| /Documentation/media/uapi/mediactl/ |
| D | media-request-ioc-queue.rst | 63 Other errors can be returned if the contents of the request contained
68 errors that occur when the request is applied to the hardware. The
84 :ref:`Generic Error Codes <gen-errors>` chapter.
|
12345678910>>...18