J.A. Magallón wrote:
scsi4 : ata_piix
scsi5 : ata_piix
ata3: SATA max UDMA/133 cmd 0xc000 ctl 0xc400 bmdma 0xd000 irq 18
ata4: SATA max UDMA/133 cmd 0xc800 ctl 0xcc00 bmdma 0xd008 irq 18
ata4.00: ATA-8: ST3500820AS, SD25, max UDMA/133
ata4.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 0/32)
ata4.00: configured for UDMA/133
ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
ata4.00: cmd b0/d8:00:00:4f:c2/00:00:00:00:00/00 tag 0
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
ata4.00: status: { DRDY }
Can you bisect to see when this problem starts? I'm pretty sure it's
software, either interrupt-related or the libata driver itself.
See http://ata.wiki.kernel.org/index.php/Libata_error_messages for a
full explanation of that error message.
Most notable: "DRDY" == device ready == device says everything is OK,
from it's perspective. "timeout" usually means an interrupt wasn't
delivered from your ATA controller, when we were expecting one.
Jeff
--
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
