Searched full:error (Results 1 – 25 of 1086) sorted by relevance
12345678910>>...44
| /Documentation/filesystems/bcachefs/ |
| D | errorcodes.rst | 3 bcachefs private error codes
6 In bcachefs, as a hard rule we do not throw or directly use standard error
7 codes (-EINVAL, -EBUSY, etc.). Instead, we define private error codes as needed
10 This gives us much better error messages and makes debugging much easier. Any
11 direct uses of standard error codes you see in the source code are simply old
14 Private error codes may subtype another error code, this allows for grouping of
16 errors), as well as specifying which standard error code should be returned at
19 At the module boundary, we use bch2_err_class() to convert to a standard error
20 code; this also emits a trace event so that the original error code be
23 Do not reuse error codes! Generally speaking, a private error code should only
[all …]
|
| /Documentation/fault-injection/ |
| D | notifier-error-inject.rst | 1 Notifier error injection
4 Notifier error injection provides the ability to inject artificial errors to
5 specified notifier chain callbacks. It is useful to test the error handling of
14 PM notifier error injection module
18 /sys/kernel/debug/notifier-error-inject/pm/actions/<notifier event>/error
26 Example: Inject PM suspend error (-12 = -ENOMEM)::
28 # cd /sys/kernel/debug/notifier-error-inject/pm/
29 # echo -12 > actions/PM_SUSPEND_PREPARE/error
31 bash: echo: write error: Cannot allocate memory
33 Memory hotplug notifier error injection module
[all …]
|
| /Documentation/PCI/ |
| D | pcieaer-howto.rst | 5 The PCI Express Advanced Error Reporting Driver Guide HOWTO
19 This guide describes the basics of the PCI Express (PCIe) Advanced Error
28 PCIe error signaling can occur on the PCIe link itself
30 defines two error reporting paradigms: the baseline capability and
31 the Advanced Error Reporting capability. The baseline capability is
33 set of error reporting requirements. Advanced Error Reporting
34 capability is implemented with a PCIe Advanced Error Reporting
35 extended capability structure providing more robust error reporting.
38 Error Reporting capability. The PCIe AER driver provides three basic
41 - Gathers the comprehensive error information if errors occurred.
[all …]
|
| /Documentation/ABI/testing/ |
| D | debugfs-cec-error-inj | 1 What: /sys/kernel/debug/cec/*/error-inj
6 The CEC Framework allows for CEC error injection commands through
7 debugfs. Drivers that support this will create an error-inj file
8 through which the error injection commands can be given.
18 implemented and that it will remove all current error injection
21 This ensures that you can always do 'echo clear >error-inj' to clear any
22 error injections without having to know the details of the driver-specific
25 Note that the output of 'error-inj' shall be valid as input to 'error-inj'.
28 $ cat error-inj >einj.txt
29 $ cat einj.txt >error-inj
[all …]
|
| D | sysfs-class-fpga-manager | 29 * firmware request error = firmware request failed
31 * write init error = Error while preparing FPGA for programming
33 * write error = Error while programming
35 * write complete error = Error while doing post programming
44 error or incompatible bitstream image. The intent of this
49 * reconfig operation error - invalid operations detected by
53 * reconfig CRC error - CRC error detected by
57 * reconfig IP protocol error - protocol errors detected by
59 * reconfig fifo overflow error - FIFO overflow detected by
|
| D | debugfs-cxl | 12 address to the device's Poison List and the error source is set
16 It is not an error to inject poison into an address that
17 already has poison present and no error is returned. If the
18 device returns 'Inject Poison Limit Reached' an -EBUSY error
32 for 64 bytes starting at address. It is not an error to clear
43 (RO) Prints the CXL protocol error types made available by
46 0x<error number> <error type>
48 The possible error types are (as of ACPI v6.5):
57 The <error number> can be written to einj_inject to inject
58 <error type> into a chosen dport.
[all …]
|
| D | sysfs-devices-platform-stratix10-rsu | 23 The state field has two parts: major error code in
24 upper 16 bits and minor error code in lower 16 bits.
27 Currently used only when major error is 0xF006
29 error code is the value reported by CPU to
34 0xF001 bitstream error
37 0xF004 internal error
38 0xF005 device error
40 0xF007 internal unknown error
49 reported the error.
59 0x0 no error
[all …]
|
| D | sysfs-bus-pci-devices-aer_stats | 23 Receiver Error 2
29 Corrected Internal Error 0
46 Surprise Down Error 0
57 Uncorrectable Internal Error 0
60 TLP Prefix Blocked Error 0
76 Surprise Down Error 0
87 Uncorrectable Internal Error 0
90 TLP Prefix Blocked Error 0
97 collectors) that are AER capable. These indicate the number of error messages as
100 device, so these counters include them and are thus cumulative of all the error
|
| /Documentation/firmware-guide/acpi/apei/ |
| D | output_format.rst | 7 APEI uses printk as hardware error reporting interface, the output
10 <error record> :=
11 APEI generic hardware error status
25 [, resource not accessible][, latent error]
27 <section type string> := generic processor error | memory error | \
28 PCIe error | unknown, <uuid string>
38 <proc error type strings>]
54 <processor error type strings># :=
55 [cache error][, TLB error][, bus error][, micro-architectural error]
78 [error_type: <integer>, <mem error type string>]
[all …]
|
| D | einj.rst | 4 APEI Error INJection
7 EINJ provides a hardware error injection mechanism. It is very useful
23 has an option to enable error injection. Look for something called WHEA
35 ...and to (optionally) enable CXL protocol error injection set::
45 This file shows which error types are supported:
48 Error Type Value Error Description
65 the available error types.
69 Set the value of the error type being injected. Possible error types
74 Write any integer to this file to trigger the error injection. Make
75 sure you have specified all necessary error parameters, i.e. this
[all …]
|
| /Documentation/networking/ |
| D | xfrm_proc.rst | 29 Header error
36 Transformation protocol specific error
40 Transformation mode specific error
43 Sequence error
68 Policy error
85 Bundle generation error
88 Bundle check error
94 Transformation protocol specific error
97 Transformation mode specific error
100 Sequence error
[all …]
|
| /Documentation/userspace-api/media/cec/ |
| D | cec-pin-error-inj.rst | 5 CEC Pin Framework Error Injection
16 over the bus it is easy to support error injection. This is ideal to
17 test how well CEC adapters can handle error conditions.
23 If ``CONFIG_CEC_PIN_ERROR_INJ`` is enabled, then error injection is available
25 now an ``error-inj`` file.
29 The error injection commands are not a stable ABI and may change in the
32 With ``cat error-inj`` you can see both the possible commands and the current
33 error injection status::
35 $ cat /sys/kernel/debug/cec/cec0/error-inj
36 # Clear error injections:
[all …]
|
| /Documentation/devicetree/bindings/edac/ |
| D | socfpga-eccmgr.txt | 18 - reg : Address and size for ECC error interrupt clear registers.
19 - interrupts : Should be single bit error interrupt, then double bit error
25 - reg : Address and size for ECC error interrupt clear registers.
27 - interrupts : Should be single bit error interrupt, then double bit error
63 - interrupts : Should be single bit error interrupt, then double bit error
74 - reg : Address and size for ECC error interrupt clear registers.
75 - interrupts : Should be single bit error interrupt, then double bit error
82 - interrupts : Should be single bit error interrupt, then double bit error
90 - interrupts : Should be single bit error interrupt, then double bit error
98 - interrupts : Should be single bit error interrupt, then double bit error
[all …]
|
| /Documentation/networking/device_drivers/ethernet/marvell/ |
| D | octeontx2.rst | 172 - Error due to operation of unmapped PF.
173 - Error due to disabled alloc/free for other HW blocks (NIX, SSO, TIM, DPI and AURA).
175 2. ERROR events
178 - AQ Doorbell Error.
182 - RAS Error Reporting for NPA_AQ_INST_S/NPA_AQ_RES_S.
186 - Error due to unmapped slot.
193 …state healthy error 2872 recover 2872 last_dump_date 2020-12-10 last_dump_time 09:39:09 grace_peri…
195 …state healthy error 2872 recover 2872 last_dump_date 2020-12-11 last_dump_time 04:43:04 grace_peri…
197 …state healthy error 2871 recover 2871 last_dump_date 2020-12-10 last_dump_time 09:39:17 grace_peri…
199 …state healthy error 0 recover 0 last_dump_date 2020-12-10 last_dump_time 09:32:40 grace_period 0 a…
[all …]
|
| /Documentation/admin-guide/ |
| D | filesystem-monitoring.rst | 7 File system Error Reporting
10 Fanotify supports the FAN_FS_ERROR event type for file system-wide error
26 error that occurred for a file system since the last notification, and
41 [ Generic Error Record (Mandatory) ]
49 Generic error record
52 The generic error record provides enough information for a file system
62 __s32 error;
66 The `error` field identifies the type of error using errno values.
68 suppressed to preserve the original error information, since the last
75 the error through the combination of fsid and file handle. A file system
|
| D | xfs.rst | 292 A volume knob for error reporting when internal errors occur.
301 Causes certain error conditions to call BUG(). Value is a bitmask;
382 Error handling
385 XFS can act differently according to the type of error found during its
386 operation. The implementation introduces the following concepts to the error
390 Defines how fast XFS should propagate an error upwards when a specific
391 error is found during the filesystem operation. It can propagate
395 -error classes:
396 Specifies the subsystem the error configuration will apply to, such as
398 different error handlers for which behaviour can be configured.
[all …]
|
| /Documentation/devicetree/bindings/arm/tegra/ |
| D | nvidia,tegra234-cbb.yaml | 22 fabric. Each Root MN contains a Error Monitor (EM) which detects and
23 logs error. Interrupts from various EM blocks are collated by Error
29 the interrupt from EN. Debug information includes Error Code, Error
31 Security Group etc on receiving error notification.
33 If the Error Response Disable (ERD) is set/enabled for an initiator,
34 then SError or Data abort exception error response is masked and an
57 - description: secure interrupt from error notifier
|
| D | nvidia,tegra194-cbb.yaml | 23 By default, the access issuing initiator is informed about the error
24 using SError or Data Abort exception unless the ERD (Error Response
26 SError or Data Abort is masked and the error is reported with interrupt.
30 If ERD is not set, then error is reported by SError.
38 The driver prints relevant debug information like Error Code, Error
40 etc on receiving error notification.
59 CCPLEX receives secure or nonsecure interrupt depending on error type.
70 for any error logged in their status register.
|
| /Documentation/driver-api/ |
| D | libata.rst | 329 :c:func:`irq_clear` hook, which simply clears the interrupt and error flags
375 Error handling
393 midlayer. libata internal commands are used for initialization and error
466 pio_task invokes :c:func:`ata_qc_complete`. In error cases, packet_task may
493 code path is taken and very little error handling takes place. A qc is
499 :c:func:`ata_qc_complete` is invoked with error status, which in turn invokes
514 timeout and ATAPI error completion. This function will check if a qc is active
541 - Error representation is too crude. Currently any and all error
542 conditions are represented with ATA STATUS and ERROR registers.
544 errors by setting ATA_ERR bit. Better error descriptor which can
[all …]
|
| /Documentation/userspace-api/media/dvb/ |
| D | frontend-stat-properties.rst | 49 the occurrence of an event, like bit error, block error, or lapsed
91 .. _DTV-STAT-PRE-ERROR-BIT-COUNT:
96 Measures the number of bit errors before the forward error correction
103 In order to get the BER (Bit Error Rate) measurement, it should be
116 - ``FE_SCALE_COUNTER`` - Number of error bits counted before the inner
127 :ref:`DTV_STAT_PRE_ERROR_BIT_COUNT <DTV-STAT-PRE-ERROR-BIT-COUNT>`
145 :ref:`DTV_STAT_PRE_ERROR_BIT_COUNT <DTV-STAT-PRE-ERROR-BIT-COUNT>`.
148 .. _DTV-STAT-POST-ERROR-BIT-COUNT:
153 Measures the number of bit errors after the forward error correction
160 In order to get the BER (Bit Error Rate) measurement, it should be
[all …]
|
| D | fe-read-ber.rst | 31 The bit error rate is stored into \*ber.
36 This ioctl call returns the bit error rate for the signal currently
45 On error -1 is returned, and the ``errno`` variable is set
48 Generic error codes are described at the
49 :ref:`Generic Error Codes <gen-errors>` chapter.
|
| /Documentation/userspace-api/media/ |
| D | gen-errors.rst | 6 Generic Error Codes
14 .. flat-table:: Generic error codes
49 allowed range. This is a widely used error code. See the
66 - On USB devices, the stream ioctl's can return this error, meaning
77 - I/O error. Typically used when there are problems communicating with
79 It's a 'Something is wrong, I give up!' type of error.
88 #. This list is not exhaustive; ioctls may return other error codes.
93 #. Request-specific error codes are listed in the individual
|
| /Documentation/userspace-api/media/mediactl/ |
| D | media-request-ioc-queue.rst | 40 common error codes. On error both the request and driver state are unchanged.
44 exception is the ``EIO`` error which signals a fatal error that requires
52 return an ``ENOENT`` error.
57 On success 0 is returned, on error -1 and the ``errno`` variable is set
58 appropriately. The generic error codes are described at the
59 :ref:`Generic Error Codes <gen-errors>` chapter.
|
| /Documentation/userspace-api/ioctl/ |
| D | cdrom.rst | 84 and -1 with errno set to an appropriate value on error. (Some
91 Individual drivers may return error codes not listed here.
116 error return:
137 error return:
161 error return:
192 error return:
221 error return:
246 error return:
250 - EIO I/O error reading TOC
276 error return:
[all …]
|
| /Documentation/userspace-api/gpio/ |
| D | error-codes.rst | 6 GPIO Error Codes
13 .. flat-table:: Common GPIO error codes
43 allowed range. This is a widely used error code.
61 - I/O error. Typically returned when there are problems communicating
64 It's a 'Something is wrong, I give up!' type of error.
73 #. This list is not exhaustive; ioctls may return other error codes.
78 #. Request-specific error codes are listed in the individual
|
12345678910>>...44