Re: sata_sil.c, 3512 and SIL_QUIRK_MOD15WRITE

[Tejun Heo <htejun@gmail.com>]

Jon Kåre Hellan wrote:
> My Shuttle SN85G4V2 with Silicon Image 3512 SATA controller has been locking up
> frequently for a while. Console message:
> 
> ata1: command 0x35 timeout, stat 0x58 host_stat 0x61
> ata1: status=0x58 { DriveReady SeekComplete DataRequest }
> sd 0:0:0:0: SCSI error: return code = 0x8000002
> sda: Current: sense key: Aborted Command
>     Additional sense: Scsi parity error
> end_request: I/O error, dev sda, sector 57582833
> Buffer I/O error on device sda6, logical block 3097255
> lost page write due to I/O error on sda6
> ATA: abnormal status 0x58 on port 0xF8802087
> ATA: abnormal status 0x58 on port 0xF8802087
> 
> I have a Seagate ST3200822AS disk, which is on the blacklist in sata_sil.
> In sil_pci_tbl in drivers/sata/sata_sil.c, I changed 3512 from sil_3112 to
> sil_3112_m15w, enabling SIL_QUIRK_MOD15WRITE for my controller. With this, the
> lockups are gone.
> 
> Looks like MOD15WRITE was turned off for the 3512 between 2.6.13 and 2.6.14.
> This may have been a mistake, or else my system is unusually flaky. 
> 

Hello, Jon Kåre.

The m15w workaround is an extreme solution and tends to hide whatever 
bug/errata whether the problem actually is m15w or not. Unfortunately, 
in the past, we didn't have enough errata information and thus the m15w 
blacklist kept growing (oh... something wrong with Seagate drives? It 
must be m15w!).

Recently, Silicon Image has opened all the erratas and we're in the 
process of getting things done correctly. New errata workarounds are 
being implemented and devices not really affected by m15w are delisted, 
etc... And, unfortunately, due to insufficient information, turning off 
m15w for 3512 and 3114 was done before addind other needed workarounds 
causing problems for 3512 and 3114 users.

According to the errata information from Silicon Image, SiI3512 does not 
have m15w bug, neither does ST3200822AS. So, this must be something else 
and you're not an isolated case. One of my friends reported the same 
problem but I currently can't test it as he sold his motherboard 
*really* fast. :-( So, it would be very nice if you can test fixes we'll 
be able to come up with.

Carlos (Hi!), 3512 + some 7200.7 hangs. Can you think of any related errata?

Thanks.

-- 
tejun