Re: CK804 SATA Errors (still got them)

[Robert Hancock <hancockr@shaw.ca>]

Alistair John Strachan wrote:
> Hi Robert,
> 
> Despite all the work that went into making these less frequent with ADMA,
> they're still possible to trigger.
> 
> alistair@damocles:~$ cat /proc/version
> Linux version 2.6.21-rc2-damocles (root@damocles) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 SMP Wed Feb 28 21:58:41 GMT 2007
> 
> alistair@damocles:~$ dmesg | tail -n 13
> ata1: EH in ADMA mode, notifier 0x0 notifier_error 0x0 gen_ctl 0x1501000 status 0x500 next cpb count 0x0 next cpb idx 0x0
> ata1: CPB 0: ctl_flags 0xd, resp_flags 0x1
> ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
> ata1.00: cmd ca/00:38:ae:08:c2/00:00:00:00:00/e0 tag 0 cdb 0x0 data 28672 out
>          res 40/00:00:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata1: soft resetting port
> ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata1.00: configured for UDMA/133
> ata1: EH complete
> SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB)
> sda: Write Protect is off
> sda: Mode Sense: 00 3a 00 00
> SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> 
> These cause the same ~30 second stalls. Machine was not under load.
> 
> No 3rd party modules were loaded.

This one seems a bit different. This time it's not related to NCQ vs. 
non-NCQ (this is a non-NCQ write here), it's in ADMA mode (so it's 
presumably not related to switching between ADMA and register mode, 
unless perhaps a flush cache or something executed just before), and 
from the CPB data it appears the command completed but the controller's 
registers aren't indicating that it has. Not sure if I've seen one like 
that before..

How easily can you reproduce this?

-- 
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/