Searched refs:faulty (Results 1 – 24 of 24) sorted by relevance
| /Linux-v5.10/drivers/md/ |
| D | Makefile | 29 faulty-y += md-faulty.o
42 obj-$(CONFIG_MD_FAULTY) += faulty.o
|
| D | md.h | 773 int faulty = test_bit(Faulty, &rdev->flags); in rdev_dec_pending() local
774 if (atomic_dec_and_test(&rdev->nr_pending) && faulty) { in rdev_dec_pending()
|
| D | Kconfig | 175 The "faulty" module allows for a block device that occasionally returns
|
| /Linux-v5.10/Documentation/admin-guide/media/ |
| D | dvb-usb-dibusb-mb-cardlist.rst | 21 * - Artec T1 USB1.1 TVBOX with AN2235 (faulty USB IDs)
|
| /Linux-v5.10/Documentation/networking/device_drivers/ethernet/netronome/ |
| D | nfp.rst | 170 alignment errors. The cause is usually faulty cables or SFPs.
214 * An error on the MAC/physical layer. Usually due to faulty cables or
|
| /Linux-v5.10/Documentation/admin-guide/ |
| D | md.rst | 195 raid5, linear, multipath, faulty.
254 For arrays with data redundancy (i.e. not raid0, linear, faulty,
455 faulty
474 it were not faulty are blocked.
499 Writing ``faulty`` simulates a failure on the device.
528 This file responds to select/poll. Any change to ``faulty``
|
| D | hw_random.rst | 33 hardware is faulty or has been tampered with). Data is only
|
| /Linux-v5.10/Documentation/driver-api/soundwire/ |
| D | error_handling.rst | 47 driver will return a -ETIMEOUT. Such timeouts are symptoms of a faulty
|
| /Linux-v5.10/arch/arm/mm/ |
| D | proc-v6.S | 235 teq r5, r6 @ check for the faulty core
|
| D | Kconfig | 1019 bool "PL310 errata: cache sync operation may be faulty"
|
| /Linux-v5.10/drivers/media/usb/dvb-usb/ |
| D | Kconfig | 62 bool "Support faulty USB IDs"
65 Support for faulty USB IDs due to an invalid EEPROM on some Artec devices.
|
| /Linux-v5.10/Documentation/hwmon/ |
| D | dme1737.rst | 153 returns 1 when a faulty diode or an unconnected input is detected and 0
269 detects a faulty thermal diode or an
|
| D | lm90.rst | 376 the status register is read and the faulty temperature channel is logged.
|
| /Linux-v5.10/arch/s390/boot/ |
| D | head.S | 360 # the save area and does disabled wait with a faulty address.
|
| /Linux-v5.10/Documentation/networking/ |
| D | plip.rst | 103 above calculation. It isn't an important issue, unless the wire is faulty,
|
| /Linux-v5.10/arch/arm/ |
| D | Kconfig | 899 bool "ARM errata: DMB operation may be faulty"
938 bool "ARM errata: TLBIASIDIS and TLBIMVAIS operations can broadcast a faulty ASID"
942 r2p0) erratum. A faulty ASID can be sent to the other CPUs for the
955 (r2p*) erratum. Under very rare conditions, a faulty
975 bool "ARM errata: possible faulty MMU translations following an ASID switch"
|
| /Linux-v5.10/Documentation/fault-injection/ |
| D | fault-injection.rst | 5 See also drivers/md/md-faulty.c and "every_nth" module option for scsi_debug.
|
| /Linux-v5.10/arch/sparc/ |
| D | Kconfig | 251 printed in the event of a memory error, so that the faulty DIMM
|
| /Linux-v5.10/Documentation/PCI/ |
| D | msi-howto.rst | 265 Some devices are known to have faulty MSI implementations. Usually this
|
| /Linux-v5.10/Documentation/userspace-api/media/v4l/ |
| D | dev-subdev.rst | 51 such as contrast adjustment, white balance or faulty pixels correction.
|
| /Linux-v5.10/Documentation/scsi/ |
| D | sym53c8xx_2.rst | 798 On a faulty SCSI BUS, any error condition among SGE (0x08), UDC (0x04) and
|
| D | ncr53c8xx.rst | 1587 On a faulty SCSI BUS, any error condition among SGE (0x08), UDC (0x04) and
|
| /Linux-v5.10/Documentation/driver-api/ |
| D | libata.rst | 687 be anything - driver bug, faulty device, controller and/or cable.
|
| /Linux-v5.10/Documentation/sparc/oradax/ |
| D | dax-hv-api.txt | 1069 …s may result in multiple failures until RAS software can identify and isolate the faulty component.
|
