| /kernel/linux/linux-4.19/Documentation/PCI/ |
| D | pcieaer-howto.txt | 33 - Gathers the comprehensive error information if errors occurred.
78 When PCIe AER errors are captured, the counters / statistics are also exposed
90 PCI Express errors are classified into two types: correctable errors
91 and uncorrectable errors. This classification is based on the impacts
92 of those errors, which may result in degraded performance or function
95 Correctable errors pose no impacts on the functionality of the
97 intervention or any loss of data. These errors are detected and
98 corrected by hardware. Unlike correctable errors, uncorrectable
99 errors impact functionality of the interface. Uncorrectable errors
102 errors are further classified into non-fatal errors and fatal errors.
[all …]
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-4.19/Documentation/x86/x86_64/ |
| D | machinecheck | 5 by the CPU. Uncorrected errors typically cause a machine check
14 When you see the "Machine check errors logged" message in the system
38 How often to poll for corrected machine check errors, in seconds
45 check errors (but some corrected errors might be still reported
58 0: always panic on uncorrected errors, log corrected errors
59 1: panic or SIGBUS on uncorrected errors, log corrected errors
60 2: SIGBUS or log uncorrected errors, log corrected errors
61 3: never panic or SIGBUS, log all errors (for testing only)
|
| D | boot-options.txt | 21 Don't make logs for corrected errors. All events reported
24 of corrected errors.
26 Disable features for corrected errors, e.g. polling timer
30 there is an agent checking/clearing corrected errors
48 0: always panic on uncorrected errors, log corrected errors
49 1: panic or SIGBUS on uncorrected errors, log corrected errors
50 2: SIGBUS or log uncorrected errors, log corrected errors
51 3: never panic or SIGBUS, log all errors (for testing only)
63 errors since we will not see details for all errors.
174 acpi=nocmcff Disable firmware first mode for corrected errors. This
|
| /kernel/linux/linux-4.19/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 …]
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-4.19/drivers/md/bcache/ |
| D | io.c | 54 /* IO errors */
57 unsigned int errors; in bch_count_backing_io_errors() local
73 errors = atomic_add_return(1, &dc->io_errors); in bch_count_backing_io_errors()
74 if (errors < dc->error_limit) in bch_count_backing_io_errors()
95 unsigned int errors; in bch_count_io_errors() local
101 * successfully do so, we rescale the errors once: in bch_count_io_errors()
109 errors = atomic_read(&ca->io_errors); in bch_count_io_errors()
111 old = errors; in bch_count_io_errors()
112 new = ((uint64_t) errors * 127) / 128; in bch_count_io_errors()
113 errors = atomic_cmpxchg(&ca->io_errors, in bch_count_io_errors()
[all …]
|
| /kernel/linux/linux-5.10/drivers/md/bcache/ |
| D | io.c | 54 /* IO errors */
57 unsigned int errors; in bch_count_backing_io_errors() local
73 errors = atomic_add_return(1, &dc->io_errors); in bch_count_backing_io_errors()
74 if (errors < dc->error_limit) in bch_count_backing_io_errors()
95 unsigned int errors; in bch_count_io_errors() local
101 * successfully do so, we rescale the errors once: in bch_count_io_errors()
109 errors = atomic_read(&ca->io_errors); in bch_count_io_errors()
111 old = errors; in bch_count_io_errors()
112 new = ((uint64_t) errors * 127) / 128; in bch_count_io_errors()
113 errors = atomic_cmpxchg(&ca->io_errors, in bch_count_io_errors()
[all …]
|
| /kernel/linux/linux-5.10/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.
208 Disable firmware first mode for corrected errors. This
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-4.19/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:
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 …]
|
| /kernel/linux/linux-5.10/tools/testing/selftests/bpf/ |
| D | test_tunnel.sh | 162 # causing errors at get_tunnel_{key/opt}.
730 local errors=0
734 errors=$(( $errors + $? ))
738 errors=$(( $errors + $? ))
742 errors=$(( $errors + $? ))
746 errors=$(( $errors + $? ))
750 errors=$(( $errors + $? ))
754 errors=$(( $errors + $? ))
758 errors=$(( $errors + $? ))
762 errors=$(( $errors + $? ))
[all …]
|
| /kernel/linux/linux-5.10/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 */ \
|
| /kernel/linux/linux-4.19/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 */ \
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-4.19/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 …]
|
| /kernel/linux/linux-5.10/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" },
|
| /kernel/linux/linux-4.19/drivers/net/ethernet/pasemi/ |
| D | pasemi_mac_ethtool.c | 35 { "rx-crc-errors" },
36 { "rx-undersize-errors" },
37 { "rx-oversize-errors" },
38 { "rx-short-fragment-errors" },
39 { "rx-jabber-errors" },
54 { "tx-crc-errors" },
55 { "tx-undersize-errors" },
56 { "tx-oversize-errors" },
|
| /kernel/linux/linux-4.19/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
|
| /kernel/linux/linux-5.10/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
|