Home
last modified time | relevance | path

Searched refs:errors (Results 1 – 25 of 666) sorted by relevance

12345678910>>...27

/Linux-v5.4/lib/
Dcrc32test.c667 int errors = 0; in crc32c_test() local
692 errors++; in crc32c_test()
701 if (errors) in crc32c_test()
702 pr_warn("crc32c: %d self tests failed\n", errors); in crc32c_test()
714 int errors = 0, runs = 0; in crc32c_combine_test() local
732 errors++; in crc32c_combine_test()
738 if (errors) in crc32c_combine_test()
739 pr_warn("crc32c_combine: %d/%d self tests failed\n", errors, runs); in crc32c_combine_test()
749 int errors = 0; in crc32_test() local
777 errors++; in crc32_test()
[all …]
/Linux-v5.4/drivers/md/bcache/
Dio.c57 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
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()
115 } while (old != errors); in bch_count_io_errors()
121 unsigned int errors = atomic_add_return(1 << IO_ERROR_SHIFT, in bch_count_io_errors() local
[all …]
/Linux-v5.4/Documentation/ABI/testing/
Dsysfs-platform-dfl-fme48 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 …]
Dsysfs-bus-pci-devices-aer_stats5 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 …]
Dsysfs-platform-dfl-port78 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
Ddebugfs-pfo-nx-crypto13 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.
/Linux-v5.4/Documentation/x86/x86_64/
Dmachinecheck.rst8 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)
Dboot-options.rst25 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
/Linux-v5.4/Documentation/PCI/
Dpcieaer-howto.rst41 - 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-v5.4/drivers/macintosh/
Dwindfarm_pid.c46 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-v5.4/Documentation/driver-api/soundwire/
Derror_handling.rst5 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-v5.4/tools/testing/selftests/bpf/
Dtest_tunnel.sh699 local errors=0
703 errors=$(( $errors + $? ))
707 errors=$(( $errors + $? ))
711 errors=$(( $errors + $? ))
715 errors=$(( $errors + $? ))
719 errors=$(( $errors + $? ))
723 errors=$(( $errors + $? ))
727 errors=$(( $errors + $? ))
731 errors=$(( $errors + $? ))
735 errors=$(( $errors + $? ))
[all …]
/Linux-v5.4/tools/perf/scripts/perl/
Drw-by-pid.pl36 $reads{$common_pid}{errors}{$ret}++;
58 $writes{$common_pid}{errors}{$ret}++;
102 foreach my $error (keys %{$reads{$pid}{errors}}) {
104 my $errcount = $reads{$pid}{errors}{$error} || 0;
142 foreach my $error (keys %{$writes{$pid}{errors}}) {
144 my $errcount = $writes{$pid}{errors}{$error} || 0;
/Linux-v5.4/kernel/
Dtest_kprobes.c17 static int errors, handler_errors, num_tests; variable
286 errors++; in init_test_probes()
291 errors++; in init_test_probes()
297 errors++; in init_test_probes()
302 errors++; in init_test_probes()
305 if (errors) in init_test_probes()
306 pr_err("BUG: %d out of %d tests failed\n", errors, num_tests); in init_test_probes()
/Linux-v5.4/tools/testing/selftests/powerpc/mm/
Dsubpage_prot.c35 int errors; variable
80 ++errors; in check_faulted()
119 errors = 0; in run_test()
130 if (errors) { in run_test()
131 printf("%d errors detected\n", errors); in run_test()
/Linux-v5.4/arch/x86/tools/
Dinsn_sanity.c227 int errors = 0; in main() local
251 errors++; in main()
259 fprintf((errors) ? stderr : stdout, in main()
262 (errors) ? "Failure" : "Success", in main()
265 errors, in main()
268 return errors ? 1 : 0; in main()
/Linux-v5.4/drivers/usb/
Dusb-skeleton.c59 int errors; /* the last request tanked */ member
151 res = dev->errors ? (dev->errors == -EPIPE ? -EPIPE : -EIO) : 0; in skel_flush()
152 dev->errors = 0; in skel_flush()
177 dev->errors = urb->status; in skel_read_bulk_callback()
268 rv = dev->errors; in skel_read()
271 dev->errors = 0; in skel_read()
349 dev->errors = urb->status; in skel_write_bulk_callback()
391 retval = dev->errors; in skel_write()
394 dev->errors = 0; in skel_write()
626 dev->errors = -EPIPE; in skel_post_reset()
/Linux-v5.4/drivers/acpi/apei/
DKconfig15 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-v5.4/drivers/edac/
De752x_edac.c516 static void do_global_error(int fatal, u32 errors) in do_global_error() argument
521 if (errors & (1 << i)) { in do_global_error()
534 static inline void global_error(int fatal, u32 errors, int *error_found, in global_error() argument
540 do_global_error(fatal, errors); in global_error()
550 static void do_hub_error(int fatal, u8 errors) in do_hub_error() argument
555 if (errors & (1 << i)) in do_hub_error()
561 static inline void hub_error(int fatal, u8 errors, int *error_found, in hub_error() argument
567 do_hub_error(fatal, errors); in hub_error()
607 static void do_nsi_error(int fatal, u32 errors) in do_nsi_error() argument
612 if (errors & (1 << i)) in do_nsi_error()
[all …]
Di7300_edac.c355 unsigned long errors; in i7300_process_error_global() local
365 errors = error_reg; in i7300_process_error_global()
366 errnum = find_first_bit(&errors, in i7300_process_error_global()
381 errors = error_reg; in i7300_process_error_global()
382 errnum = find_first_bit(&errors, in i7300_process_error_global()
414 unsigned long errors; in i7300_process_fbd_error() local
424 errors = error_reg & FERR_FAT_FBD_ERR_MASK ; in i7300_process_fbd_error()
425 errnum = find_first_bit(&errors, in i7300_process_fbd_error()
447 bank, ras, cas, errors, specific); in i7300_process_fbd_error()
460 errors = error_reg & FERR_NF_FBD_ERR_MASK; in i7300_process_fbd_error()
[all …]
/Linux-v5.4/drivers/staging/comedi/drivers/
Djr3_pci.c116 u16 errors; member
272 u16 errors; in jr3_pci_ai_insn_read() local
275 errors = get_u16(&spriv->sensor->errors); in jr3_pci_ai_insn_read()
277 (errors & (watch_dog | watch_dog2 | sensor_change))) { in jr3_pci_ai_insn_read()
446 int errors; in jr3_pci_poll_subdevice() local
450 errors = get_u16(&sensor->errors); in jr3_pci_poll_subdevice()
452 if (errors != spriv->errors) in jr3_pci_poll_subdevice()
453 spriv->errors = errors; in jr3_pci_poll_subdevice()
456 if (errors & (watch_dog | watch_dog2 | sensor_change)) in jr3_pci_poll_subdevice()
464 if ((errors & (watch_dog | watch_dog2)) || in jr3_pci_poll_subdevice()
/Linux-v5.4/drivers/base/test/
Dtest_async_driver_probe.c21 static atomic_t warnings, errors, timeout, async_completed; variable
34 atomic_inc(&errors); in test_probe()
250 } else if (!atomic_read(&errors) && !atomic_read(&warnings)) { in test_async_probe_init()
273 atomic_inc(&errors); in test_async_probe_init()
278 atomic_read(&errors), atomic_read(&warnings)); in test_async_probe_init()
/Linux-v5.4/Documentation/networking/
Dxfrm_proc.txt15 Inbound errors
18 All errors which is not matched others
56 Outbound errors
59 All errors which is not matched others
/Linux-v5.4/Documentation/filesystems/
Docfs2-online-filecheck.txt12 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
/Linux-v5.4/Documentation/driver-api/
Dlibata.rst403 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 …]

12345678910>>...27