From: Robert Hancock <hancockrwd@gmail.com>
To: bl0 <bl0-052@playker.info>
Cc: linux-ide@vger.kernel.org, linux-pci@vger.kernel.org,
Tejun Heo <tj@kernel.org>, Jeff Garzik <jeff@garzik.org>
Subject: Re: sata_sil data corruption, possible workarounds
Date: Tue, 08 Jan 2013 22:48:43 -0600 [thread overview]
Message-ID: <50ECF6AB.30007@gmail.com> (raw)
In-Reply-To: <kb9pa2$mi8$1@ger.gmane.org>
On 12/24/2012 08:37 AM, bl0 wrote:
> On Tuesday 18 December 2012 16:23, bl0 wrote:
>
>> On Monday 17 December 2012 06:44, Robert Hancock wrote:
>>
>>> But it seems quite likely that
>>> whatever magic numbers this code is picking don't work on your system
>>> for some reason. It appears the root cause is likely a bug in the SiI
>>> chip. There shouldn't be any region why messing around with these values
>>> should cause data corruption other than that.
>>
>> Do you think something should be done about it in the linux sata_sil
>> driver? For a lack of a better solution, here is my suggestion. There is
>> already one option 'slow_down' for problematic disks. Another option, for
>> example 'cache_line_workaround', could be added for problematic
>> motherboards. If enabled, the most straightforward way is to set cache
>> line size to 0 and not worry about the fifo_cfg register.
>
> Here is the code I currently have, attached as a diff. (This diff is not
> against the latest git tree, it's against an older linux version which I
> use.)
I wouldn't mind something like this as an option, anyway. Jeff, Tejun,
thoughts?
next prev parent reply other threads:[~2013-01-09 4:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <kahap3$mur$1@ger.gmane.org>
[not found] ` <50CCF1E0.9070804@gmail.com>
2012-12-16 12:21 ` sata_sil data corruption, possible workarounds bl0
2012-12-17 5:44 ` Robert Hancock
[not found] ` <kaq1n6$hqa$1@ger.gmane.org>
2012-12-19 3:44 ` Robert Hancock
[not found] ` <kaujmk$op$1@ger.gmane.org>
2013-01-07 4:11 ` Robert Hancock
[not found] ` <kb9pa2$mi8$1@ger.gmane.org>
2013-01-09 4:48 ` Robert Hancock [this message]
2013-01-09 19:17 ` Tejun Heo
2013-01-11 10:28 ` bl0
2013-01-11 13:53 ` Mark Lord
2013-01-11 13:54 ` Mark Lord
2013-01-14 17:58 ` Jeff Garzik
2013-01-15 7:44 ` bl0
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50ECF6AB.30007@gmail.com \
--to=hancockrwd@gmail.com \
--cc=bl0-052@playker.info \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=tj@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).