Lines Matching full:errors

403 This chapter describes how errors are handled under libata. Readers are
569    Errors which aren't ATA device errors are treated as ATA device
570    errors by setting ATA_ERR bit. Better error descriptor which can
571    properly represent ATA and other errors/exceptions is needed.
582    errors and other errors quite often require reset to return to known
586 -  ATA errors are directly handled in the interrupt handler and PIO
587    errors in pio_task. This is problematic for advanced error handling
626 ATA errors and exceptions
637 which are not errors (say, power or hotplug events), or to describe both
638 errors and non-error exceptional conditions. Where explicit distinction
680 transmission errors sometimes cause this kind of errors.
685 These are errors detected and reported by ATA/ATAPI devices indicating
686 device problems. For this type of errors, STATUS and ERROR register
688 errors are detected by ATA/ATAPI devices and reported using the same
689 mechanism as device errors. Those cases are described later in this
692 For ATA commands, this type of errors are indicated by !BSY && ERR
707 Of errors detected as above, the following are not ATA/ATAPI device
708 errors but ATA bus errors and should be handled according to
720     ICRC errors and on cases where a device is not able to complete a
721     command. Combined with the fact that MWDMA and PIO transfer errors
723     that ABRT bit alone could indicate transfer errors.
726     errors can turn on ABRT. So, this is kind of gray area. Some
729 ATA/ATAPI device errors can be further categorized as follows.
731 Media errors
750 Other errors
753     of things including ICRC and Address errors. Heuristics needed.
773 PACKET command. For this kind of errors, sense data should be acquired
774 to gather information regarding the errors. REQUEST SENSE packet command
777 Once sense data is acquired, this type of errors can be handled
778 similarly to other SCSI errors. Note that sense data may indicate ATA
800 Note that ATA bus errors can be reported as ATA device NCQ errors. This
811 over ATA bus (SATA or PATA). This type of errors can be indicated by
822 -  Unknown/random errors, timeouts and all sorts of weirdities.
824 As described above, transmission errors can cause wide variety of
828 of heuristic when dealing with errors and timeouts. For example,
829 encountering repetitive ABRT errors for known supported command is
832 Once it's determined that ATA bus errors have possibly occurred,
842 BMDMA Status register. This type of errors must be logged as it
851 usually caused by lost interrupts. This type of errors must be logged.
863 Timeouts can also be caused by transmission errors. Refer to
987     If more than $N (3?) transmission errors happen in 15 minutes,