Re: libata fails to recover from HSM violation involving DRQ status

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Tejun Heo wrote:
Tejun Heo wrote:
..
Anyways, can you try to hack it into ata_bmdma_error_handler() and see
whether it actually works?  You can check for AC_ERR_HSM there and drain
data port if DRQ is set.  After HSM, ATA_NIEN is set and the port should
be quiescent at that point.

Sure, I'll do that here shortly.

Oh, and one more thing, was the drive SATA or PATA?

The controller, and libata, think the drive is SATA.
(but it really is PATA with a bridge between it and the controller).

Ah.. one more thing, is this draining also needed after DMA commands or
only after PIO commands?

Dunno about DMA -- this instance was just an IDENTIFY command (PIO).
I think the drive also does IDENTIFY_DMA, though, so I can try that too.

Cheers
-
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Filesystems]     [Linux SCSI]     [Linux RAID]     [Git]     [Kernel Newbies]     [Linux Newbie]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Samba]     [Device Mapper]

  Powered by Linux