Lines Matching full:errors

378 This chapter describes how errors are handled under libata. Readers are
543    Errors which aren't ATA device errors are treated as ATA device
544    errors by setting ATA_ERR bit. Better error descriptor which can
545    properly represent ATA and other errors/exceptions is needed.
556    errors and other errors quite often require reset to return to known
560 -  ATA errors are directly handled in the interrupt handler and PIO
561    errors in pio_task. This is problematic for advanced error handling
600 ATA errors and exceptions
611 which are not errors (say, power or hotplug events), or to describe both
612 errors and non-error exceptional conditions. Where explicit distinction
654 transmission errors sometimes cause this kind of errors.
659 These are errors detected and reported by ATA/ATAPI devices indicating
660 device problems. For this type of errors, STATUS and ERROR register
662 errors are detected by ATA/ATAPI devices and reported using the same
663 mechanism as device errors. Those cases are described later in this
666 For ATA commands, this type of errors are indicated by !BSY && ERR
681 Of errors detected as above, the following are not ATA/ATAPI device
682 errors but ATA bus errors and should be handled according to
694     ICRC errors and on cases where a device is not able to complete a
695     command. Combined with the fact that MWDMA and PIO transfer errors
697     that ABRT bit alone could indicate transfer errors.
700     errors can turn on ABRT. So, this is kind of gray area. Some
703 ATA/ATAPI device errors can be further categorized as follows.
705 Media errors
724 Other errors
727     of things including ICRC and Address errors. Heuristics needed.
747 PACKET command. For this kind of errors, sense data should be acquired
748 to gather information regarding the errors. REQUEST SENSE packet command
751 Once sense data is acquired, this type of errors can be handled
752 similarly to other SCSI errors. Note that sense data may indicate ATA
774 Note that ATA bus errors can be reported as ATA device NCQ errors. This
785 over ATA bus (SATA or PATA). This type of errors can be indicated by
796 -  Unknown/random errors, timeouts and all sorts of weirdities.
798 As described above, transmission errors can cause wide variety of
802 of heuristic when dealing with errors and timeouts. For example,
803 encountering repetitive ABRT errors for known supported command is
806 Once it's determined that ATA bus errors have possibly occurred,
816 BMDMA Status register. This type of errors must be logged as it
825 usually caused by lost interrupts. This type of errors must be logged.
837 Timeouts can also be caused by transmission errors. Refer to
961     If more than $N (3?) transmission errors happen in 15 minutes,