Mark Lord schrieb:
(...)
ata6: exception Emask 0x10 SAct 0x0 SErr 0x180000 action 0x6 frozen
ata6: edma_err 0x00000020
ata6: hard resetting port
ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata6.00: configured for UDMA/133
ata6: EH pending after completion, repeating EH (cnt=4)
ata6: exception Emask 0x10 SAct 0x0 SErr 0x4010000 action 0x7
ata6: edma_err 0x00000010, dev connect
ata6: hard resetting port
..
Translation:
"libata reset the link, and everything appeared okay,
so it reissued the failed command and continued.
No data loss."
And today kernel (2.6.23.1) in the same machine have spoken to
not-mere-mortals again:
ata6: exception Emask 0x10 SAct 0x0 SErr 0x0 action 0x6 frozen
ata6: edma_err 0x00000020
ata6: hard resetting port
ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata6.00: configured for UDMA/133
ata6: EH complete
sd 5:0:0:0: [sde] 781422768 512-byte hardware sectors (400088 MB)
sd 5:0:0:0: [sde] Write Protect is off
sd 5:0:0:0: [sde] Mode Sense: 00 3a 00 00
sd 5:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
As I understand it now, your previous translation would fit here (or
not, as SErr differs?):
> Translation:
> "libata reset the link, and everything appeared okay,
> so it reissued the failed command and continued.
> No data loss."
But why was the port reseted? There was no CRC error as before, was there?
What worries me is that it always happens for the same drive.
--
Tomasz Chmielewski
http://wpkg.org
-
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
