Re: libata interface fatal error

[Florian Effenberger <florian@effenberger.org>]

Hi,

thanks for the fast reply!

> Looks like a genuine transmission/interface error to me.  How often does
> this occur?  Please try to connect the drive to another port using and
> possibly different power lane.  Also, testing with another drive is a
> good way to track down where the problem is.

it occurs as soon as the drive is being used heavily (load of about 2,x 
on the machine when running our test scripts). About 15 times in 2 or 3 
hours. Will try to change port, power supply and drive.

> Yeah, libata EH is working properly so there shouldn't be any problem
> other than the error messages and a bit slower transfer speed.

So, even if the errors are still there, there is nothing real to worry 
about for me?

There are now new errors with hard errors, is this still ok?

===
ata4.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x2 frozen
ata4.00: cmd 60/80:00:00:09:97/00:00:0a:00:00/40 tag 0 cdb 0x0 data 65536 in
          res 40/00:04:00:67:14/00:00:1c:00:00/40 Emask 0x4 (timeout)
ata4: soft resetting port
ata4: softreset failed (1st FIS failed)
ata4: softreset failed, retrying in 5 secs
ata4: hard resetting port
ata4: port is slow to respond, please be patient (Status 0x80)
ata4: port failed to respond (30 secs, Status 0x80)
ata4: COMRESET failed (device not ready)
ata4: hardreset failed, retrying in 5 secs
ata4: hard resetting port
ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata4.00: configured for UDMA/133
ata4: EH complete
SCSI device sdd: 625142448 512-byte hdwr sectors (320073 MB)
sdd: Write Protect is off
sdd: Mode Sense: 00 3a 00 00
SCSI device sdd: write cache: enabled, read cache: enabled, doesn't 
support DPO or FUA
===

Florian