Home
last modified time | relevance | path

Searched refs:errors (Results 1 – 200 of 407) sorted by relevance

123

/linux-4.1.27/drivers/ide/
Dide-eh.c15 rq->errors |= ERROR_RESET; in ide_ata_error()
28 rq->errors = ERROR_MAX; in ide_ata_error()
31 rq->errors |= ERROR_RECAL; in ide_ata_error()
42 if (rq->errors >= ERROR_MAX || blk_noretry_request(rq)) { in ide_ata_error()
48 rq->errors |= ERROR_RESET; in ide_ata_error()
50 if ((rq->errors & ERROR_RESET) == ERROR_RESET) { in ide_ata_error()
51 ++rq->errors; in ide_ata_error()
55 if ((rq->errors & ERROR_RECAL) == ERROR_RECAL) in ide_ata_error()
58 ++rq->errors; in ide_ata_error()
71 rq->errors |= ERROR_RESET; in ide_atapi_error()
[all …]
Dide-floppy.c101 rq->errors = uptodate ? 0 : IDE_DRV_ERROR_GENERAL; in ide_floppy_callback()
242 if (rq->errors >= ERROR_MAX) { in ide_floppy_do_request()
250 rq->errors = 0; in ide_floppy_do_request()
299 if (rq->cmd_type != REQ_TYPE_FS && rq->errors == 0) in ide_floppy_do_request()
300 rq->errors = -EIO; in ide_floppy_do_request()
Dide-devsets.c176 ret = rq->errors; in ide_devset_execute()
188 rq->errors = err; in ide_do_devset()
Dide-io.c144 rq->errors = 0; in ide_kill_rq()
147 rq->errors = IDE_DRV_ERROR_GENERAL; in ide_kill_rq()
148 else if (rq->cmd_type != REQ_TYPE_FS && rq->errors == 0) in ide_kill_rq()
149 rq->errors = -EIO; in ide_kill_rq()
274 rq->errors = 0; in execute_drive_cmd()
Dide-cd.c252 if (!rq->errors) in ide_cd_breathe()
255 rq->errors = 1; in ide_cd_breathe()
299 if (rq->cmd_type == REQ_TYPE_BLOCK_PC && !rq->errors) in cdrom_decode_status()
300 rq->errors = SAM_STAT_CHECK_CONDITION; in cdrom_decode_status()
330 if (++rq->errors > ERROR_MAX) in cdrom_decode_status()
377 } else if (++rq->errors > ERROR_MAX) in cdrom_decode_status()
678 if (uptodate <= 0 && rq->errors == 0) in cdrom_newpc_intr()
679 rq->errors = -EIO; in cdrom_newpc_intr()
1367 rq->errors = ILLEGAL_REQUEST; in ide_cdrom_prep_pc()
Dide-atapi.c447 pc->rq->errors++; in ide_pc_intr()
481 rq->errors = 0; in ide_pc_intr()
486 if (rq->errors == 0) in ide_pc_intr()
487 rq->errors = -EIO; in ide_pc_intr()
Dide-taskfile.c289 cmd->rq->errors = 0; in ide_pio_datablock()
331 rq->errors = err; in ide_finish_cmd()
Dide-ioctls.c229 ret = rq->errors; in generic_drive_reset()
Dide-dma.c493 hwif->rq->errors = 0; in ide_dma_timeout_retry()
/linux-4.1.27/Documentation/x86/x86_64/
Dmachinecheck5 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)
Dboot-options.txt21 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
44 0: always panic on uncorrected errors, log corrected errors
45 1: panic or SIGBUS on uncorrected errors, log corrected errors
46 2: SIGBUS or log uncorrected errors, log corrected errors
47 3: never panic or SIGBUS, log all errors (for testing only)
59 errors since we will not see details for all errors.
166 acpi=nocmcff Disable firmware first mode for corrected errors. This
/linux-4.1.27/lib/
Dcrc32.c980 int errors = 0; local
1006 errors++;
1018 if (errors)
1019 pr_warn("crc32c: %d self tests failed\n", errors);
1031 int errors = 0, runs = 0; local
1049 errors++;
1055 if (errors)
1056 pr_warn("crc32c_combine: %d/%d self tests failed\n", errors, runs);
1066 int errors = 0; local
1095 errors++;
[all …]
Drandom32.c420 int i, j, errors = 0, runs = 0; in prandom_state_selftest() local
448 errors++; in prandom_state_selftest()
454 if (errors) in prandom_state_selftest()
455 pr_warn("prandom: %d/%d self tests failed\n", errors, runs); in prandom_state_selftest()
DKconfig.kmemcheck57 Select the maximum number of errors to store in the queue. Since
58 errors can occur virtually anywhere and in any context, we need a
DKconfig.kgdb109 int "KDB: continue after catastrophic errors"
/linux-4.1.27/drivers/macintosh/
Dwindfarm_pid.c47 st->errors[i] = error; in wf_pid_run()
54 st->errors[st->index] = error; in wf_pid_run()
59 integ += st->errors[(st->index + hlen - i) % hlen]; in wf_pid_run()
63 deriv = st->errors[st->index] - in wf_pid_run()
64 st->errors[(st->index + hlen - 1) % hlen]; in wf_pid_run()
102 st->errors[i] = error; in wf_cpu_pid_run()
110 st->errors[st->index] = error; in wf_cpu_pid_run()
117 integ += st->errors[(st->index + hlen - i) % hlen]; in wf_cpu_pid_run()
Dwindfarm_pid.h40 s32 errors[WF_PID_MAX_HISTORY]; /* error history buffer */ member
77 s32 errors[WF_PID_MAX_HISTORY]; /* error history buffer */ member
/linux-4.1.27/kernel/
Dtest_kprobes.c26 static int errors, handler_errors, num_tests; variable
352 errors++; in init_test_probes()
357 errors++; in init_test_probes()
362 errors++; in init_test_probes()
367 errors++; in init_test_probes()
373 errors++; in init_test_probes()
378 errors++; in init_test_probes()
381 if (errors) in init_test_probes()
382 pr_err("BUG: %d out of %d tests failed\n", errors, num_tests); in init_test_probes()
/linux-4.1.27/Documentation/PCI/
Dpcieaer-howto.txt33 - Gathers the comprehensive error information if errors occurred.
93 PCI Express errors are classified into two types: correctable errors
94 and uncorrectable errors. This classification is based on the impacts
95 of those errors, which may result in degraded performance or function
98 Correctable errors pose no impacts on the functionality of the
100 intervention or any loss of data. These errors are detected and
101 corrected by hardware. Unlike correctable errors, uncorrectable
102 errors impact functionality of the interface. Uncorrectable errors
105 errors are further classified into non-fatal errors and fatal errors.
106 Non-fatal errors cause the particular transaction to be unreliable,
[all …]
Dpci-error-recovery.txt13 PCI errors on the bus, such as parity errors on the data and address
14 busses, as well as SERR and PERR errors. Some of the more advanced
15 chipsets are able to deal with these errors; these include PCI-E chipsets,
59 bus errors are easy to manage in the device driver. Indeed, most
62 mechanisms for dealing with SCSI bus errors and SCSI bus resets.
199 >>> this callback, errors triggered by them will be returned via
372 errors. See the discussion in powerpc/eeh-pci-error-recovery.txt
374 software errors.
/linux-4.1.27/drivers/md/bcache/
Dio.c165 unsigned errors; in bch_count_io_errors() local
179 errors = atomic_read(&ca->io_errors); in bch_count_io_errors()
181 old = errors; in bch_count_io_errors()
182 new = ((uint64_t) errors * 127) / 128; in bch_count_io_errors()
183 errors = atomic_cmpxchg(&ca->io_errors, in bch_count_io_errors()
185 } while (old != errors); in bch_count_io_errors()
192 unsigned errors = atomic_add_return(1 << IO_ERROR_SHIFT, in bch_count_io_errors() local
194 errors >>= IO_ERROR_SHIFT; in bch_count_io_errors()
196 if (errors < ca->set->error_limit) in bch_count_io_errors()
/linux-4.1.27/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;
Drwtop.pl49 $reads{$common_pid}{errors}{$ret}++;
75 $writes{$common_pid}{errors}{$ret}++;
/linux-4.1.27/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-4.1.27/drivers/acpi/apei/
DKconfig14 APEI allows to report errors (for example from the chipset)
27 platform hardware errors (such as that from chipset). It
29 errors are reported to firmware firstly, then reported to
39 PCIe AER errors may be reported via APEI firmware first mode.
46 Memory errors may be reported via APEI firmware first mode.
/linux-4.1.27/drivers/usb/
Dusb-skeleton.c61 int errors; /* the last request tanked */ member
154 res = dev->errors ? (dev->errors == -EPIPE ? -EPIPE : -EIO) : 0; in skel_flush()
155 dev->errors = 0; in skel_flush()
179 dev->errors = urb->status; in skel_read_bulk_callback()
271 rv = dev->errors; in skel_read()
274 dev->errors = 0; in skel_read()
351 dev->errors = urb->status; in skel_write_bulk_callback()
393 retval = dev->errors; in skel_write()
396 dev->errors = 0; in skel_write()
644 dev->errors = -EPIPE; in skel_post_reset()
/linux-4.1.27/drivers/edac/
De752x_edac.c517 static void do_global_error(int fatal, u32 errors) in do_global_error() argument
522 if (errors & (1 << i)) { in do_global_error()
535 static inline void global_error(int fatal, u32 errors, int *error_found, in global_error() argument
541 do_global_error(fatal, errors); in global_error()
551 static void do_hub_error(int fatal, u8 errors) in do_hub_error() argument
556 if (errors & (1 << i)) in do_hub_error()
562 static inline void hub_error(int fatal, u8 errors, int *error_found, in hub_error() argument
568 do_hub_error(fatal, errors); in hub_error()
608 static void do_nsi_error(int fatal, u32 errors) in do_nsi_error() argument
613 if (errors & (1 << i)) in do_nsi_error()
[all …]
Di7300_edac.c358 unsigned long errors; in i7300_process_error_global() local
368 errors = error_reg; in i7300_process_error_global()
369 errnum = find_first_bit(&errors, in i7300_process_error_global()
384 errors = error_reg; in i7300_process_error_global()
385 errnum = find_first_bit(&errors, in i7300_process_error_global()
417 unsigned long errors; in i7300_process_fbd_error() local
427 errors = error_reg & FERR_FAT_FBD_ERR_MASK ; in i7300_process_fbd_error()
428 errnum = find_first_bit(&errors, in i7300_process_fbd_error()
450 bank, ras, cas, errors, specific); in i7300_process_fbd_error()
463 errors = error_reg & FERR_NF_FBD_ERR_MASK; in i7300_process_fbd_error()
[all …]
DKconfig15 EDAC is designed to report errors in the core system.
16 These are low-level errors that are reported in the CPU or
18 memory errors, cache errors, PCI errors, thermal throttling, etc..
77 Some systems are able to detect and correct errors in main
80 errors). EDAC will also try to decode where these errors
85 bool "Output ACPI APEI/GHES BIOS detected errors via EDAC"
111 Support for error detection and correction of DRAM ECC errors on
121 errors into DRAM.
/linux-4.1.27/drivers/staging/comedi/drivers/
Djr3_pci.c121 u16 errors; member
279 u16 errors; in jr3_pci_ai_insn_read() local
285 errors = get_u16(&spriv->channel->errors); in jr3_pci_ai_insn_read()
287 (errors & (watch_dog | watch_dog2 | sensor_change))) { in jr3_pci_ai_insn_read()
458 int errors; in jr3_pci_poll_subdevice() local
465 errors = get_u16(&channel->errors); in jr3_pci_poll_subdevice()
467 if (errors != spriv->errors) in jr3_pci_poll_subdevice()
468 spriv->errors = errors; in jr3_pci_poll_subdevice()
471 if (errors & (watch_dog | watch_dog2 | sensor_change)) in jr3_pci_poll_subdevice()
479 if ((errors & (watch_dog | watch_dog2)) || in jr3_pci_poll_subdevice()
Djr3_pci.h555 u32 errors; /* offset 0x00f1 */ member
/linux-4.1.27/arch/x86/tools/
Dinsn_sanity.c240 int errors = 0; in main() local
264 errors++; in main()
274 (errors) ? "Failure" : "Success", in main()
277 errors, in main()
280 return errors ? 1 : 0; in main()
/linux-4.1.27/block/
Dblk-exec.c83 rq->errors = -ENXIO; in blk_execute_rq_nowait()
84 __blk_end_request_all(rq, rq->errors); in blk_execute_rq_nowait()
133 if (rq->errors) in blk_execute_rq()
Dbsg-lib.c59 err = job->req->errors = result; in bsg_job_done()
86 blk_end_request_all(rq, rq->errors); in bsg_softirq_done()
181 req->errors = ret; in bsg_request_fn()
Dscsi_ioctl.c259 hdr->status = rq->errors & 0xff; in blk_complete_sghdr_rq()
260 hdr->masked_status = status_byte(rq->errors); in blk_complete_sghdr_rq()
261 hdr->msg_status = msg_byte(rq->errors); in blk_complete_sghdr_rq()
262 hdr->host_status = host_byte(rq->errors); in blk_complete_sghdr_rq()
263 hdr->driver_status = driver_byte(rq->errors); in blk_complete_sghdr_rq()
509 err = rq->errors & 0xff; /* only 8 bit SCSI status */ in sg_scsi_ioctl()
Dbsg.c398 dprintk("rq %p bio %p 0x%x\n", rq, bio, rq->errors); in blk_complete_sgv4_hdr_rq()
402 hdr->device_status = rq->errors & 0xff; in blk_complete_sgv4_hdr_rq()
403 hdr->transport_status = host_byte(rq->errors); in blk_complete_sgv4_hdr_rq()
404 hdr->driver_status = driver_byte(rq->errors); in blk_complete_sgv4_hdr_rq()
438 if (!ret && rq->errors < 0) in blk_complete_sgv4_hdr_rq()
439 ret = rq->errors; in blk_complete_sgv4_hdr_rq()
Dblk-mq.c211 rq->errors = 0; in blk_mq_rq_ctx_init()
387 blk_mq_end_request(rq, rq->errors); in __blk_mq_complete_request()
560 rq->errors = -EIO; in blk_mq_abort_requeue_list()
561 blk_mq_end_request(rq, rq->errors); in blk_mq_abort_requeue_list()
638 rq->errors = -EIO; in blk_mq_check_expired()
832 rq->errors = -EIO; in __blk_mq_run_hw_queue()
833 blk_mq_end_request(rq, rq->errors); in __blk_mq_run_hw_queue()
1296 rq->errors = -EIO; in blk_mq_make_request()
1297 blk_mq_end_request(rq, rq->errors); in blk_mq_make_request()
/linux-4.1.27/Documentation/ABI/testing/
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.
Dsysfs-devices-edac5 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
Dsysfs-class-net-statistics59 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.
Dsysfs-class-mtd130 Maximum number of bit errors that the device is capable of
143 maximum number of bit errors that were corrected on any single
156 interpreted to mean simply "one or more bit errors were
158 dangerously high number of bit errors were corrected on one or
Dsysfs-memory-page-offline33 triggering IO errors if needed. Note this may kill
Dsysfs-ata106 Number of time libata decided to lower the speed of link due to errors.
/linux-4.1.27/tools/testing/selftests/rcutorture/bin/
Dparse-build.sh47 print_bug $title build errors:
58 print_warning $title build errors:
/linux-4.1.27/drivers/acpi/
Dbus.c228 u32 errors; in acpi_run_osc() local
268 errors = *((u32 *)out_obj->buffer.pointer) & ~(1 << 0); in acpi_run_osc()
269 if (errors) { in acpi_run_osc()
270 if (errors & OSC_REQUEST_ERROR) in acpi_run_osc()
273 if (errors & OSC_INVALID_UUID_ERROR) in acpi_run_osc()
276 if (errors & OSC_INVALID_REVISION_ERROR) in acpi_run_osc()
279 if (errors & OSC_CAPABILITIES_MASK_ERROR) { in acpi_run_osc()
/linux-4.1.27/arch/um/drivers/
Dpcap_user.c20 char errors[PCAP_ERRBUF_SIZE]; in pcap_user_init() local
23 pri->promisc, 0, errors); in pcap_user_init()
26 "'%s'\n", errors); in pcap_user_init()
/linux-4.1.27/drivers/staging/lustre/lnet/selftest/
Dping_test.c76 int errors; in ping_client_fini() local
81 errors = atomic_read(&sn->sn_ping_errors); in ping_client_fini()
82 if (errors) in ping_client_fini()
83 CWARN("%d pings have failed.\n", errors); in ping_client_fini()
/linux-4.1.27/Documentation/networking/
Dxfrm_proc.txt16 All errors which is not matched others
50 Outbound errors
53 All errors which is not matched others
Dcops.txt44 RX packets:0 errors:0 dropped:0 overruns:0 frame:0
45 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 coll:0
Daltera_tse.txt88 Ethtool is supported. Driver statistics and internal errors can be taken using:
141 received. This count does not include any error packets such as CRC errors,
142 length errors, or alignment errors.
171 a count of the number of packets received containing errors that prevented the
175 is a count of the number of packets that could not be transmitted due to errors.
Dixgb.txt188 behavior after modifying this register may be undefined (possibly errors of
342 Excessive CRC errors may be observed if the Intel(R) PRO/10GbE CX4
345 The CRC errors may be received either by the Intel(R) PRO/10GbE CX4
352 Excessive CRC errors may be observed if the Intel(R) PRO/10GbE CX4 Server
357 Excessive CRC errors may be observed using Fujitsu 24AWG cable assemblies that
359 errors may be received either by the CX4 Server adapter or at the switch. If
D3c509.txt150 If an EtherLink III appears to transmit packets, but the "Tx carrier errors"
203 error is mixed with 0x82 errors it is the result of a host incorrectly set
206 Both of these errors are the result of network problems that should be
Dnetif-msg.txt21 0 Minimal messages, only essential information on fatal errors.
Drds.txt138 ENOBUFS errors returned by sendmsg.
295 then maintained forever -- if there are transport errors, the
333 no errors, call rds_ib_process_recv()
Dpktgen.txt84 pkts-sofar: 10000000 errors: 39664
91 763292pps 390Mb/sec (390805504bps) errors: 39664
Dcan.txt227 ECUs. The occurrence of detected errors are important for diagnosis
236 errors may be selected. The reception of error messages is disabled
513 errors are divided into different error classes that may be filtered
1048 re-started bus-errors arbit-lost error-warn error-pass bus-off
1050 RX: bytes packets errors dropped overrun mcast
1052 TX: bytes packets errors dropped carrier collsns
1095 "re-started bus-errors arbit-lost error-warn error-pass bus-off"
1096 Shows the number of restarts, bus and arbitration lost errors,
1098 bus-off state. RX overrun errors are listed in the "overrun"
1138 A device may enter the "bus-off" state if too many errors occurred on
Digb.txt86 for "other" interrupts such as link status change and errors. All
/linux-4.1.27/drivers/pci/pcie/aer/
DKconfig.debug14 to trigger various real hardware errors. Software based
15 error injection can fake almost all kinds of errors with the
/linux-4.1.27/Documentation/
Dedac.txt35 The 'edac' kernel module goal is to detect and report errors that occur
41 Errors (UE) are the primary errors being harvested. These types of errors
69 in order to determine if errors are occurring on data transfers.
71 The presence of PCI Parity errors must be examined with a grain of salt.
95 NMI NMI notification of ECC errors
99 These errors are usually bus errors, ECC errors, thermal throttling
258 errors that have occurred on this csrow. If panic_on_ue is set
268 errors that have occurred on this csrow. This
336 to it. With this label in the module, when errors occur
369 to it. With this label in the module, when errors occur
[all …]
Ddigsig.txt17 memory allocation errors handling, has been refactored according to kernel
18 coding style, and checkpatch.pl reported errors and warnings have been fixed.
Dbad_memory.txt37 Example: memtest86+ reported here errors at address 0x18691458, 0x18698424 and
DSubmitChecklist17 =n. No gcc warnings/errors, no linker warnings/errors.
Dbcache.txt33 from disk or invalidating cache entries. For unrecoverable errors (meta data
110 Bcache tries to transparently handle IO errors to/from the cache device without
111 affecting normal operation; if it sees too many errors (the threshold is
118 - For writethrough writes, if the write to the cache errors we just switch to
348 These determines how many errors we accept before disabling the cache.
431 Number of errors that have occurred, decayed by io_error_halflife.
Dkmemcheck.txt17 4. Reporting errors
33 programmer errors that the compiler is not able to find through static
131 (fixed-size) buffer. Since errors can occur virtually anywhere and in
138 than 64 errors within an irqs-off section, then the code is likely to
171 some real errors, but disabling it would probably produce a lot of
651 ability to find (real) errors in other parts of the same struct.
693 4. Reporting errors
698 maintainers. Instead, I encourage maintainers and developers to find errors
Dapplying-patches.txt87 except for errors which is nice to prevent errors from scrolling out of the
93 Common errors when patching
177 As I already mentioned above, these errors should never happen if you apply
179 So if you get these errors with kernel.org patches then you should probably
DDMA-API.txt290 a mapping. A driver can check for these errors by testing the returned
631 errors will only silently counted. This limitation exist to prevent the code
651 numbers of errors found.
675 all errors again.
685 driver filter at boot time. The debug code will only print errors for that
697 to check DMA mapping errors on addresses returned by dma_map_single() and
DIntel-IOMMU.txt70 When errors are reported, the DMA engine signals via an interrupt. The fault
Dmd.txt378 should be replaced, either due to errors or
407 errors
408 An approximate count of read errors that have been detected on
532 performing 'resync', md will count the number of errors that are
536 than sectors, this may be larger than the number of actual errors
Dsysfs-rules.txt170 propagate errors wherever possible. Common errors include, but are not
/linux-4.1.27/include/trace/events/
Dblock.h74 __field( int, errors )
85 __entry->errors = rq->errors;
95 __entry->nr_sector, __entry->errors)
154 __field( int, errors )
163 __entry->errors = rq->errors;
173 __entry->nr_sector, __entry->errors)
/linux-4.1.27/drivers/net/fddi/skfp/
Dpcmplc.c1080 u_long errors ; in lem_evaluate() local
1090 errors = inpw(PLC(((int) phy->np),PL_LINK_ERR_CTR)) ; in lem_evaluate()
1091 lem->lem_errors += errors ; in lem_evaluate()
1092 mib->fddiPORTLem_Ct += errors ; in lem_evaluate()
1094 errors = lem->lem_errors ; in lem_evaluate()
1105 if (!errors) ber = 15 ; in lem_evaluate()
1106 else if (errors <= 9) ber = 9 ; in lem_evaluate()
1107 else if (errors <= 99) ber = 8 ; in lem_evaluate()
1108 else if (errors <= 999) ber = 7 ; in lem_evaluate()
1109 else if (errors <= 9999) ber = 6 ; in lem_evaluate()
[all …]
/linux-4.1.27/drivers/video/fbdev/omap2/dss/
Ddispc-compat.c337 u32 errors; in dispc_error_worker() local
347 errors = dispc_compat.error_irqs; in dispc_error_worker()
360 if (bit & errors) { in dispc_error_worker()
375 if (bit & errors) { in dispc_error_worker()
397 if (errors & DISPC_IRQ_OCP_ERR) { in dispc_error_worker()
408 dispc_compat.irq_error_mask |= errors; in dispc_error_worker()
/linux-4.1.27/drivers/net/wireless/iwlwifi/dvm/
Drxon.c780 u32 errors = 0; in iwl_check_rxon_cmd() local
785 errors |= BIT(0); in iwl_check_rxon_cmd()
789 errors |= BIT(1); in iwl_check_rxon_cmd()
794 errors |= BIT(2); in iwl_check_rxon_cmd()
798 errors |= BIT(3); in iwl_check_rxon_cmd()
803 errors |= BIT(4); in iwl_check_rxon_cmd()
810 errors |= BIT(5); in iwl_check_rxon_cmd()
815 errors |= BIT(6); in iwl_check_rxon_cmd()
821 errors |= BIT(7); in iwl_check_rxon_cmd()
827 errors |= BIT(8); in iwl_check_rxon_cmd()
[all …]
/linux-4.1.27/Documentation/acpi/apei/
Deinj.txt67 write should be the last step when injecting errors.
114 in controlling where the errors are injected. Your BIOS may support an
121 the target of the injection. For processor-related errors (type 0x1, 0x2
131 For memory errors (type 0x8, 0x10 and 0x20) the address is set using
133 express errors (type 0x40, 0x80 and 0x100) the segment, bus, device and
144 An ACPI 5.0 BIOS may also allow vendor-specific errors to be injected.
158 # cat available_error_type # See which errors can be injected
/linux-4.1.27/drivers/scsi/device_handler/
Dscsi_dh_hp_sw.c139 HP_SW_NAME, req->errors); in hp_sw_tur()
206 if (error || host_byte(req->errors) != DID_OK || in start_stop_endio()
207 msg_byte(req->errors) != COMMAND_COMPLETE) { in start_stop_endio()
210 HP_SW_NAME, req->errors); in start_stop_endio()
Dscsi_dh_alua.c167 ALUA_DH_NAME, rq->errors); in submit_vpd_inquiry()
210 ALUA_DH_NAME, rq->errors); in submit_rtpg()
234 if (host_byte(req->errors) != DID_OK || in stpg_endio()
235 msg_byte(req->errors) != COMMAND_COMPLETE) { in stpg_endio()
Dscsi_dh_emc.c344 rq->errors); in send_inquiry_cmd()
394 CLARIION_NAME, rq->errors); in send_trespass_cmd()
/linux-4.1.27/drivers/block/drbd/
DKconfig47 Say Y here if you want to simulate IO errors, in order to test DRBD's
50 The actual simulation of IO errors is done by writing 3 values to
68 Example: Simulate data write errors on /dev/drbd0 with a probability of 5%.
/linux-4.1.27/drivers/block/
Dnbd.c101 int error = req->errors ? -EIO : 0; in nbd_end_request()
350 req->errors++; in nbd_read_stat()
364 req->errors++; in nbd_read_stat()
436 req->errors++; in nbd_clear_que()
444 req->errors++; in nbd_clear_que()
474 req->errors = 0; in nbd_handle_req()
488 req->errors++; in nbd_handle_req()
503 req->errors++; in nbd_handle_req()
562 req->errors++; in do_nbd_request()
Dhd.c421 if (++req->errors >= MAX_ERRORS || (hd_error & BBD_ERR)) { in bad_rw_intr()
424 } else if (req->errors % RESET_FREQ == 0) in bad_rw_intr()
426 else if ((hd_error & TRK0_ERR) || req->errors % RECAL_FREQ == 0) in bad_rw_intr()
544 if (++hd_req->errors >= MAX_ERRORS) { in hd_times_out()
Dvirtio_blk.c126 req->errors = virtio32_to_cpu(vblk->vdev, vbr->in_hdr.errors); in virtblk_request_done()
128 req->errors = (error != 0); in virtblk_request_done()
Dcciss.c1849 blk_end_request_all(rq, (rq->errors == 0) ? 0 : -EIO); in cciss_softirq_done()
3127 rq->errors = 0; in complete_command()
3130 rq->errors = make_status_bytes(0, 0, 0, DRIVER_TIMEOUT); in complete_command()
3137 rq->errors = evaluate_target_status(h, cmd, &retry_cmd); in complete_command()
3156 rq->errors = make_status_bytes(SAM_STAT_GOOD, in complete_command()
3164 rq->errors = make_status_bytes(SAM_STAT_GOOD, in complete_command()
3172 rq->errors = make_status_bytes(SAM_STAT_GOOD, in complete_command()
3180 rq->errors = make_status_bytes(SAM_STAT_GOOD, in complete_command()
3188 rq->errors = make_status_bytes(SAM_STAT_GOOD, in complete_command()
3196 rq->errors = make_status_bytes(SAM_STAT_GOOD, in complete_command()
[all …]
Dataflop.c620 fd_request->errors++; in fd_error()
621 if (fd_request->errors >= MAX_ERRORS) { in fd_error()
625 else if (fd_request->errors == RECALIBRATE_ERRORS) { in fd_error()
1389 read_track = (ReqCmd == READ && fd_request->errors == 0); in setup_req_params()
Dfloppy.c539 static int *errors; variable
1425 } else if (*errors >= DP->max_errors.reporting) { in interpret_errors()
2048 err_count = ++(*errors); in bad_flp_intr()
2192 errors = &format_errors; in do_format()
2675 *errors < DP->max_errors.read_track && in make_raw_rw_request()
2869 errors = &(current_req->errors); in redo_fd_request()
/linux-4.1.27/arch/mips/math-emu/
Ddsemul.c90 MIPS_FPU_EMU_INC_STATS(errors); in mips_dsemul()
136 MIPS_FPU_EMU_INC_STATS(errors); in do_dsemulret()
Dcp1emu.c1057 MIPS_FPU_EMU_INC_STATS(errors); in cop1Emulate()
1062 MIPS_FPU_EMU_INC_STATS(errors); in cop1Emulate()
1075 MIPS_FPU_EMU_INC_STATS(errors); in cop1Emulate()
1080 MIPS_FPU_EMU_INC_STATS(errors); in cop1Emulate()
1091 MIPS_FPU_EMU_INC_STATS(errors); in cop1Emulate()
1096 MIPS_FPU_EMU_INC_STATS(errors); in cop1Emulate()
1109 MIPS_FPU_EMU_INC_STATS(errors); in cop1Emulate()
1114 MIPS_FPU_EMU_INC_STATS(errors); in cop1Emulate()
1471 MIPS_FPU_EMU_INC_STATS(errors); in fpux_emu()
1476 MIPS_FPU_EMU_INC_STATS(errors); in fpux_emu()
[all …]
Dme-debugfs.c58 FPU_STAT_CREATE(errors); in debugfs_fpuemu()
/linux-4.1.27/Documentation/filesystems/
Djfs.txt29 errors=continue Keep going on a filesystem error.
30 errors=remount-ro(*) Remount the filesystem read-only on an error.
31 errors=panic Panic and halt the machine if an error occurs.
Dext3.txt106 errors=remount-ro Remount the filesystem read-only on an error.
107 errors=continue Keep going on a filesystem error.
108 errors=panic Panic and halt the machine if an error occurs.
109 (These mount options override the errors behavior
Dhpfs.txt38 errors=continue,remount-ro,panic (default remount-ro)
39 Behaviour when filesystem errors found.
40 chkdsk=no,errors,always (default errors)
120 again :-). chkdsk happily ignores these errors and only low-level disk
144 driver allows you to do it. chkdsk ignores such errors.
Docfs2.txt44 errors=remount-ro(*) Remount the filesystem read-only on an error.
45 errors=panic Panic and halt the machine if an error occurs.
Dnilfs2.txt54 errors=continue Keep going on a filesystem error.
55 errors=remount-ro(*) Remount the filesystem read-only on an error.
56 errors=panic Panic and halt the machine if an error occurs.
Dxfs-self-describing-metadata.txt23 manual task of verifying that things like single bit errors or misplaced writes
56 ensure that common types of errors are easily detectable. Hence the concept of
83 hence a 32 bit CRC is more than sufficient to detect multi-bit errors in
166 error (same as for IO errors), and if it needs to take special action due to a
169 error numbers for different errors as necessary.
Dgfs2-uevents.txt56 The OFFLINE uevent is only generated due to filesystem errors and is used
Dntfs.txt176 errors=opt What to do when critical filesystem errors are found.
187 errors=continue,errors=recover
/linux-4.1.27/fs/btrfs/
Dcompression.c71 int errors; member
164 cb->errors = 1; in end_compressed_bio_read()
189 cb->errors = 1; in end_compressed_bio_read()
200 if (cb->errors) { in end_compressed_bio_read()
237 if (cb->errors) in end_compressed_writeback()
250 if (cb->errors) in end_compressed_writeback()
278 cb->errors = 1; in end_compressed_bio_write()
352 cb->errors = 0; in btrfs_submit_compressed_write()
607 cb->errors = 0; in btrfs_submit_compressed_read()
Dbtrfs_inode.h297 int errors; member
Dtransaction.c926 bool errors = false; in btrfs_wait_marked_extents() local
959 errors = true; in btrfs_wait_marked_extents()
964 errors = true; in btrfs_wait_marked_extents()
968 errors = true; in btrfs_wait_marked_extents()
971 if (errors && !werr) in btrfs_wait_marked_extents()
/linux-4.1.27/Documentation/ide/
DChangeLog.ide-cd.1994-200432 * 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
DChangeLog.ide-tape.1995-2002185 * 1 : 0+output errors only
195 * errors from 100 to 1000 in idetape_get_logical_blk
243 * cause DMA errors.
DChangeLog.ide-floppy.1996-200235 * errors in syslog. The culprit is
/linux-4.1.27/drivers/cpufreq/
Dpcc-cpufreq.c308 u32 errors; in pcc_cpufreq_do_osc() local
341 errors = *((u32 *)out_obj->buffer.pointer) & ~(1 << 0); in pcc_cpufreq_do_osc()
342 if (errors) { in pcc_cpufreq_do_osc()
370 errors = *((u32 *)out_obj->buffer.pointer) & ~(1 << 0); in pcc_cpufreq_do_osc()
371 if (errors) { in pcc_cpufreq_do_osc()
/linux-4.1.27/drivers/spi/
Dspi-davinci.c527 u32 buf, status, errors = 0, spidat1; in davinci_spi_process_events() local
539 errors = status & SPIFLG_ERROR_MASK; in davinci_spi_process_events()
552 return errors; in davinci_spi_process_events()
589 u32 errors = 0; in davinci_spi_bufs() local
713 errors = davinci_spi_process_events(dspi); in davinci_spi_bufs()
714 if (errors) in davinci_spi_bufs()
738 if (errors) { in davinci_spi_bufs()
739 ret = davinci_spi_check_error(dspi, errors); in davinci_spi_bufs()
/linux-4.1.27/drivers/staging/media/omap4iss/
DTODO4 * Fix checkpatch errors and warnings
/linux-4.1.27/scripts/
Dkernel-doc169 my $errors = 0;
427 ++$errors;
1776 ++$errors;
1815 ++$errors;
1843 ++$errors;
2358 ++$errors;
2612 if ($verbose && $errors) {
2613 print STDERR "$errors errors\n";
2619 exit($errors);
/linux-4.1.27/Documentation/device-mapper/
Ddm-flakey.txt26 <down interval>: Number of seconds device returns errors.
30 unreliability, all I/O returns errors.
Dzero.txt36 to this device, it will start returning I/O errors.
Dsnapshot.txt40 useless and be disabled, returning errors. So it is important to monitor
107 --refresh); but if it is left active it will simply return I/O errors.
/linux-4.1.27/fs/jfs/
Dsuper.c294 char *errors = args[0].from; in parse_options() local
295 if (!errors || !*errors) in parse_options()
297 if (!strcmp(errors, "continue")) { in parse_options()
301 } else if (!strcmp(errors, "remount-ro")) { in parse_options()
305 } else if (!strcmp(errors, "panic")) { in parse_options()
311 errors); in parse_options()
/linux-4.1.27/drivers/mtd/nand/
Dfsl_ifc_nand.c283 int errors; in check_read_ecc() local
285 errors = (reg >> ((3 - bufnum % 4) * 8)) & 15; in check_read_ecc()
287 return errors; in check_read_ecc()
333 int errors; in fsl_ifc_run_command() local
342 errors = check_read_ecc(mtd, ctrl, eccstat, i); in fsl_ifc_run_command()
344 if (errors == 15) { in fsl_ifc_run_command()
359 mtd->ecc_stats.corrected += errors; in fsl_ifc_run_command()
362 errors); in fsl_ifc_run_command()
Domap_elm.c292 int i, j, errors = 0; in elm_error_correction() local
323 errors += err_vec[i].error_count; in elm_error_correction()
/linux-4.1.27/drivers/staging/i2o/
DREADME.ioctl50 Returns 0 if no errors occur, and -1 otherwise. If an error occurs,
76 This function returns 0 if no errors occur. If an error occurs, -1
105 This function returns 0 if no errors occur. If an error occurs, -1
140 ops->resbuf if no errors occur. If an error occurs, -1 is returned
224 This function returns 0 no errors occur. If an error occurs, -1
266 This function returns 0 if no errors occur. If an error occurs, -1
303 This function returns 0 if no errors occur. If an error occurs, -1
389 are 0 and -1. All errors are reported through errno.
/linux-4.1.27/Documentation/powerpc/
Deeh-pci-error-recovery.txt16 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
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
314 Reiserfs does not tolerate errors returned from the block device.
/linux-4.1.27/include/linux/
Dslab_def.h54 unsigned long errors; member
/linux-4.1.27/arch/mips/include/asm/
Dfpu_emulator.h41 unsigned long errors; member
/linux-4.1.27/include/uapi/linux/
Dvirtio_blk.h138 __virtio32 errors; member
/linux-4.1.27/Documentation/ia64/
Derr_inject.txt6 errors from Linux. The tool is a test bed for IPF MC work flow including
14 provides a combination of various errors and calls the driver's interface
15 (sysfs interface) to inject errors or query error injection capabilities.
29 this sample application to inject errors.
49 #On cpu2, inject only total 0x10 errors, interval 5 seconds
54 #On cpu4, inject and consume total 0x10 errors, interval 5 seconds
59 #On cpu15, inject and consume total 0x10 errors, interval 5 seconds
830 /* Create a shm segment which will be used to inject/consume errors on.*/
961 printf("\t-i: inject errors. default: off\n");
978 printf("input to inject single or multiple errors ");
[all …]
/linux-4.1.27/arch/powerpc/platforms/powernv/
DMakefile10 obj-$(CONFIG_MEMORY_FAILURE) += opal-memory-errors.o
/linux-4.1.27/arch/x86/math-emu/
DMakefile12 C_OBJS =fpu_entry.o errors.o \
/linux-4.1.27/Documentation/scsi/
Dufs.txt116 Error handling module handles Host controller fatal errors,
117 Device fatal errors and UIC interconnect layer related errors.
DChangeLog.ips117 errors if an error occurs while trying to read/write
120 - Fixed read/write errors when the adapter is using an
Daic7xxx.txt169 10 errors are reported to the user. These errors are
172 problem, continuing to report the errors just degrades
221 Definition: Toggles the detection of PCI parity errors.
226 errors and real parity errors. The symptom of
/linux-4.1.27/Documentation/devicetree/bindings/powerpc/fsl/
Dpamu.txt23 is for PAMU hardware errors, such as PAMU operation errors
24 and ECC errors.
/linux-4.1.27/tools/perf/Documentation/
Dperf-data.txt35 Be more verbose (show counter open errors, etc).
/linux-4.1.27/Documentation/fault-injection/
Dnotifier-error-inject.txt4 Notifier error injection provides the ability to inject artificial errors to
17 injecting artificial errors to CPU notifier chain callbacks.
Dfault-injection.txt20 injects disk IO errors on devices permitted by setting
26 injects MMC data errors on devices permitted by setting
240 echo "Injecting errors into the module $module... (interrupt to stop)"
/linux-4.1.27/fs/fat/
Dmisc.c33 if (opts->errors == FAT_ERRORS_PANIC) in __fat_fs_error()
35 else if (opts->errors == FAT_ERRORS_RO && !(sb->s_flags & MS_RDONLY)) { in __fat_fs_error()
Dinode.c908 if (opts->errors == FAT_ERRORS_CONT) in fat_show_options()
910 else if (opts->errors == FAT_ERRORS_PANIC) in fat_show_options()
1051 opts->errors = FAT_ERRORS_RO; in parse_options()
1158 opts->errors = FAT_ERRORS_CONT; in parse_options()
1161 opts->errors = FAT_ERRORS_PANIC; in parse_options()
1164 opts->errors = FAT_ERRORS_RO; in parse_options()
/linux-4.1.27/drivers/media/platform/vivid/
DKconfig18 Error injection is supported to test rare errors that are hard
/linux-4.1.27/drivers/md/
Ddm-mpath.c1155 static void pg_init_done(void *data, int errors) in pg_init_done() argument
1164 switch (errors) { in pg_init_done()
1169 errors = 0; in pg_init_done()
1173 "Error %d.", m->hw_handler_name, errors); in pg_init_done()
1193 errors = 0; in pg_init_done()
1205 if (errors) { in pg_init_done()
1207 DMERR("Could not failover device. Error %d.", errors); in pg_init_done()
1281 if (!error && !clone->errors) in do_end_io()
/linux-4.1.27/drivers/staging/iio/Documentation/
Dsysfs-bus-iio-ad71928 alternate cycles, to eliminate DC errors.
/linux-4.1.27/Documentation/video4linux/bttv/
DPROBLEMS55 You will always get pixel errors when e.g. using more than 1 card in full
59 - Some S3 cards and the Matrox Mystique will produce pixel errors with
/linux-4.1.27/Documentation/devicetree/bindings/sound/
Dmvebu-audio.txt16 the data flow, and the second for errors.
/linux-4.1.27/drivers/crypto/nx/
Dnx_debugfs.c83 dfs->dfs_root, (u32 *)&drv->stats.errors); in nx_debugfs_init()
Dnx.h73 atomic_t errors; member
/linux-4.1.27/drivers/xen/
Dxen-scsiback.c267 static void scsiback_print_status(char *sense_buffer, int errors, in scsiback_print_status() argument
274 pending_req->cmnd[0], status_byte(errors), msg_byte(errors), in scsiback_print_status()
275 host_byte(errors), driver_byte(errors)); in scsiback_print_status()
378 int errors; in scsiback_cmd_done() local
382 errors = pending_req->result; in scsiback_cmd_done()
384 if (errors && log_print_stat) in scsiback_cmd_done()
385 scsiback_print_status(sense_buffer, errors, pending_req); in scsiback_cmd_done()
388 scsiback_do_resp_with_sense(sense_buffer, errors, resid, pending_req); in scsiback_cmd_done()
/linux-4.1.27/Documentation/locking/
Dlocktorture.txt103 high-level errors and reports from the main 'torture'
123 (E): true/false values if there were errors acquiring the lock. This should
142 checked for such errors. The "rmmod" command forces a "SUCCESS",
Dww-mutex-design.txt323 Some of the errors which will be warned about:
336 - Normal lockdep errors that can result in deadlocks.
338 Some of the lockdep errors that can result in deadlocks:
/linux-4.1.27/Documentation/devicetree/bindings/mtd/
Dnand.txt17 errors per {size} bytes".
/linux-4.1.27/Documentation/filesystems/nfs/
Dfault_injection.txt4 Fault injection is a method for forcing errors that may not normally occur, or
5 may be difficult to reproduce. Forcing these errors in a controlled environment
/linux-4.1.27/Documentation/cdrom/
Dide-cd152 this are Sony and Toshiba drives. You will get errors if you try to
172 In most cases, you should probably check with `dmesg' for any errors
202 errors with a status value of 0xff.
221 b. Timeout/IRQ errors.
223 - If you always get timeout errors, interrupts from the drive are
276 - If you get errors from mount, it may help to check `dmesg' to see
277 if there are any more specific errors from the driver or from the
289 not ISO 9660 or has errors in the filesystem structure).
291 - If you see `not a block device' errors, check that the definitions
/linux-4.1.27/drivers/staging/media/mn88473/
DTODO10 * I2C errors
/linux-4.1.27/drivers/staging/media/mn88472/
DTODO10 * I2C errors
/linux-4.1.27/scripts/genksyms/
Dgenksyms.c50 static int errors; variable
682 errors++; in export_symbol()
725 errors++; in error_with_pos()
874 return errors != 0; in main()
/linux-4.1.27/Documentation/dmaengine/
Ddmatest.txt80 dmatest: result dma0chan0-copy0: #1: No errors with src_off=0x7bf dst_off=0x8ad len=0x3fea (0)
82 The message format is unified across the different types of errors. A number in
/linux-4.1.27/drivers/mtd/
Drfd_ftl.c85 int errors; member
134 part->errors = 1; in build_block_map()
228 part->errors = 1; in scan_header()
786 else if (part->errors) { in rfd_ftl_add_mtd()
/linux-4.1.27/arch/blackfin/
DKconfig.debug39 bool "Try to make Hardware errors exact"
42 By default, the Blackfin hardware errors are not exact - the error
45 signal to be killed. If you are getting HW errors in your system,
95 catching common programming errors such as NULL pointer dereferences.
/linux-4.1.27/net/decnet/
DTODO17 o Verify errors etc. against POSIX 1003.1g (draft)
/linux-4.1.27/drivers/infiniband/hw/qib/
Dqib_sd7220.c888 int cnt, sofar, req, idx, errors; in qib_sd7220_prog_vfy() local
891 errors = 0; in qib_sd7220_prog_vfy()
906 ++errors; in qib_sd7220_prog_vfy()
910 return errors ? -errors : sofar; in qib_sd7220_prog_vfy()
/linux-4.1.27/drivers/scsi/osd/
DKconfig38 errors that might be regularly returned for some filesystem
/linux-4.1.27/Documentation/hwmon/
Dw83l785ts36 and cause read errors. Or maybe the W83L785TS-S chip is simply unreliable,
/linux-4.1.27/arch/m68k/ifpsp060/
DCHANGES78 For instruction read access errors, the info stacked is:
100 For data read/write access errors, the info stacked is:
/linux-4.1.27/drivers/dma/xilinx/
Dxilinx_vdma.c849 u32 errors = status & XILINX_VDMA_DMASR_ALL_ERR_MASK; in xilinx_vdma_irq_handler() local
851 errors & XILINX_VDMA_DMASR_ERR_RECOVER_MASK); in xilinx_vdma_irq_handler()
854 (errors & ~XILINX_VDMA_DMASR_ERR_RECOVER_MASK)) { in xilinx_vdma_irq_handler()
857 chan, errors, in xilinx_vdma_irq_handler()
/linux-4.1.27/Documentation/isdn/
DREADME.pcbit28 - The driver often triggers errors in the board that I and the
/linux-4.1.27/drivers/usb/gadget/udc/
Dfsl_udc_core.c1598 int errors = 0; in process_ep_req() local
1612 errors = hc32_to_cpu(curr_td->size_ioc_sts); in process_ep_req()
1613 if (errors & DTD_ERROR_MASK) { in process_ep_req()
1614 if (errors & DTD_STATUS_HALTED) { in process_ep_req()
1615 ERR("dTD error %08x QH=%d\n", errors, pipe); in process_ep_req()
1618 tmp &= ~errors; in process_ep_req()
1625 if (errors & DTD_STATUS_DATA_BUFF_ERR) { in process_ep_req()
1629 } else if (errors & DTD_STATUS_TRANSACTION_ERR) { in process_ep_req()
1635 errors); in process_ep_req()
Dmv_udc_core.c135 u32 errors; in process_ep_req() local
152 errors = curr_dtd->size_ioc_sts & DTD_ERROR_MASK; in process_ep_req()
153 if (!errors) { in process_ep_req()
172 errors); in process_ep_req()
173 if (errors & DTD_STATUS_HALTED) { in process_ep_req()
175 curr_dqh->size_ioc_int_sts &= ~errors; in process_ep_req()
177 } else if (errors & DTD_STATUS_DATA_BUFF_ERR) { in process_ep_req()
179 } else if (errors & DTD_STATUS_TRANSACTION_ERR) { in process_ep_req()
1995 udc->errors++; in irq_process_error()
Dmv_udc.h207 int errors; member
Dmv_u3d.h274 unsigned int errors; member
Dfsl_qe_udc.h344 u32 errors; /* USB ERRORs count */ member
/linux-4.1.27/drivers/bluetooth/
DKconfig112 communication may have bit errors, overrun errors or burst
113 errors and thereby making CTS/RTS lines unnecessary.
/linux-4.1.27/Documentation/video4linux/
Dsi470x.txt104 Increase tune_timeout, if you often get -EIO errors.
108 If you get any errors from snd_usb_audio, please report them to the ALSA people.
/linux-4.1.27/Documentation/block/
Drequest.txt51 int errors DB Error counts
/linux-4.1.27/kernel/gcov/
DKconfig50 which are not linked to the kernel image to prevent linker errors.
/linux-4.1.27/Documentation/sound/oss/
DPSS17 get IRQ errors be sure to check the interrupt is set to
DVIBRA1611 to setup because the kernel reported a lot of DMA errors and wouldn't
/linux-4.1.27/Documentation/devicetree/bindings/usb/
Ddwc3.txt27 amount of 8B10B errors occur.
/linux-4.1.27/drivers/usb/misc/
Dusbtest.c1810 unsigned long errors; member
1824 ctx->errors += urb->error_count; in iso_callback()
1826 ctx->errors += urb->number_of_packets; in iso_callback()
1828 ctx->errors++; in iso_callback()
1830 ctx->errors++; in iso_callback()
1852 if (ctx->errors) in iso_callback()
1855 ctx->errors, ctx->packet_count); in iso_callback()
2000 else if (context.errors > context.packet_count / 10) in test_iso_queue()
/linux-4.1.27/Documentation/input/
Dcs461x.txt42 errors.
/linux-4.1.27/kernel/trace/
Dblktrace.c723 what, rq->errors, rq->cmd_len, rq->cmd); in blk_add_trace_rq()
727 rq->cmd_flags, what, rq->errors, 0, NULL); in blk_add_trace_rq()
958 rq_data_dir(rq), BLK_TA_REMAP, !!rq->errors, in blk_add_trace_rq_remap()
984 BLK_TA_DRV_DATA, rq->errors, len, data); in blk_add_driver_data()
987 BLK_TA_DRV_DATA, rq->errors, len, data); in blk_add_driver_data()
/linux-4.1.27/Documentation/vm/
Dhwpoison.txt3 Upcoming Intel CPUs have support for recovering from some memory errors
61 This allows applications who can process memory errors in a gentle
Dovercommit-accounting20 pages but will receive errors on memory allocation as
/linux-4.1.27/Documentation/kbuild/
Dkbuild.txt179 KBUILD_MODPOST_WARN can be set to avoid errors in case of undefined
180 symbols in the final module linking stage. It changes such errors
/linux-4.1.27/Documentation/w1/slaves/
Dw1_ds242343 example from the read with crc errors:
/linux-4.1.27/Documentation/usb/
DURB.txt73 // ISO only: packets are only "best effort"; each can have errors
74 int error_count; // number of errors
201 handler, you should have a look at urb->status to detect any USB errors.
/linux-4.1.27/Documentation/development-process/
D4.Coding209 many of those errors as possible before our code goes into the mainline
218 potential errors. Quite often, these warnings point to real problems.
244 - DEBUG_SLAB can find a variety of memory allocation and use errors; it
248 number of common locking errors.
284 Other kinds of errors can be found with the "sparse" static analysis tool.
300 Other kinds of portability errors are best found by compiling your code for
/linux-4.1.27/drivers/scsi/mpt3sas/
DKconfig26 # the risks and costs of program errors, damage to or loss of data,
/linux-4.1.27/drivers/scsi/mpt2sas/
DKconfig26 # the risks and costs of program errors, damage to or loss of data,
/linux-4.1.27/drivers/staging/lustre/include/linux/lnet/
Dlnetst.h473 __u32 errors; member
/linux-4.1.27/drivers/net/ethernet/qlogic/qlcnic/
Dqlcnic_ctx.c1109 esw_stats->errors = le64_to_cpu(stats->errors); in qlcnic_get_port_stats()
1202 esw_stats->errors = QLCNIC_STATS_NOT_AVAIL; in qlcnic_get_eswitch_stats()
1226 QLCNIC_ADD_ESW_STATS(esw_stats->errors, in qlcnic_get_eswitch_stats()
1227 port_stats.errors); in qlcnic_get_eswitch_stats()
/linux-4.1.27/Documentation/security/
Dkeys-request-key.txt191 The moment one succeeds, all pending errors are discarded and the found key is
195 error. Note that several errors may have come from LSM.
/linux-4.1.27/drivers/gpu/drm/tegra/
Ddsi.c1118 u16 errors; in tegra_dsi_read_response() local
1126 errors = (value >> 8) & 0xffff; in tegra_dsi_read_response()
1128 errors); in tegra_dsi_read_response()
1130 if (errors & BIT(i)) in tegra_dsi_read_response()
/linux-4.1.27/arch/x86/include/asm/
Dapicdef.h284 u32 errors; member
/linux-4.1.27/drivers/memory/
DKconfig76 Say Y for reporting of errors from the Freescale CoreNet
/linux-4.1.27/drivers/scsi/aic7xxx/
DKconfig.aic79xx65 driver errors.
DKconfig.aic7xxx70 driver errors.
/linux-4.1.27/drivers/scsi/ufs/
Dufshcd.h450 u32 errors; member
DKconfig29 # program errors, damage to or loss of data, programs or equipment,
/linux-4.1.27/Documentation/gpio/
Dconsumer.txt56 errors and an absence of GPIO for optional GPIO parameters. For the common
150 checked, since the get/set calls don't return errors and since misconfiguration
185 The get/set calls do not return errors because "invalid GPIO" should have been
/linux-4.1.27/drivers/net/ethernet/intel/e1000/
De1000_main.c3957 u8 errors = (u8)(status_err >> 24); in e1000_rx_checksum() local
3966 if (unlikely(errors & E1000_RXD_ERR_TCPE)) { in e1000_rx_checksum()
4093 u8 status, u8 errors, in e1000_tbi_should_accept() argument
4099 if (TBI_ACCEPT(hw, status, errors, length, last_byte)) { in e1000_tbi_should_accept()
4177 (rx_desc->errors & E1000_RXD_ERR_FRAME_ERR_MASK))) { in e1000_clean_jumbo_rx_irq()
4181 rx_desc->errors, in e1000_clean_jumbo_rx_irq()
4252 status | rx_desc->errors << 24, in e1000_clean_jumbo_rx_irq()
4278 ((u32)(rx_desc->errors) << 24), in e1000_clean_jumbo_rx_irq()
4430 if (unlikely(rx_desc->errors & E1000_RXD_ERR_FRAME_ERR_MASK)) { in e1000_clean_rx_irq()
4432 rx_desc->errors, in e1000_clean_rx_irq()
[all …]
/linux-4.1.27/Documentation/video4linux/cx2341x/
Dfw-dma.txt39 - The driver checks the DMA status register for any errors.
/linux-4.1.27/Documentation/networking/caif/
DREADME65 upon errors.
/linux-4.1.27/drivers/media/pci/bt8xx/
Dbttvp.h483 unsigned int errors; member
/linux-4.1.27/drivers/w1/slaves/
DKconfig31 to the chip's output register in order to detect errors.
/linux-4.1.27/Documentation/serial/
Ddriver236 IGNPAR - ignore parity and framing errors
237 IGNBRK - ignore break errors, If IGNPAR is also
238 set, ignore overrun errors as well.
/linux-4.1.27/arch/ia64/
DKconfig487 tristate "MCA recovery from errors other than TLB."
513 call MC error injection PAL procedures to inject various errors.
526 firmware extensions, such as the ability to inject memory-errors
/linux-4.1.27/drivers/video/fbdev/omap2/displays-new/
Dpanel-dsi-cm.c396 u8 errors = 0; in dsicm_num_errors_show() local
407 &errors); in dsicm_num_errors_show()
419 return snprintf(buf, PAGE_SIZE, "%d\n", errors); in dsicm_num_errors_show()
/linux-4.1.27/drivers/net/ethernet/realtek/
DKconfig98 reset sequence, in the face of severe receive errors. This "new"
/linux-4.1.27/Documentation/ABI/
DREADME25 errors or security problems are found in them. Userspace
/linux-4.1.27/fs/xfs/
DKconfig81 not cause the kernel to panic on non-fatal errors.
/linux-4.1.27/Documentation/filesystems/cifs/
DCHANGES97 This reduces the number of EAGAIN errors returned by TCP/IP in
135 Enable experimental Kerberos support. Return writebehind errors on flush
304 (this reduces the EBADF bad file handle errors that can be logged under heavy
684 Fix errors in reconnecting after TCP session failure. Fix module unloading
696 and on revalidate errors. Fix cases where pid is now tgid. Fix return code
713 Retry on ENOSPC and EAGAIN socket errors.
758 which recently started returning errors due to
773 Fix errors displayed on failed mounts to be more understandable.
781 of openfile linked list. Allow writebehind caching errors to

123