linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>, Bernd Schubert <bs@q-leap.de>
Cc: linux-ide@vger.kernel.org, linux-scsi@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] faster workaround
Date: Thu, 11 Oct 2007 10:59:01 -0400	[thread overview]
Message-ID: <470E3A35.4000104@garzik.org> (raw)
In-Reply-To: <20071011155024.46007973@the-village.bc.nu>

Alan Cox wrote:
>> The problem is that the 3112 generates Data FIS's of a size other than a 
>> multiple of 512 bytes.  Spec-legal, but exposed firmware bugs in many 
>> early SATA drives.  Early Seagate hard drives choked when the formula 
>> (sector%15)==1 was satisfied (or something along those lines).
> 
> And the 3114 is the same ?

3114 should not be affected by this problem (see below).

Most likely we are led down this road because the 'slow_down' module 
parameter has an excellent capacity for hiding all manner of problems.

As a tangent from this thread, this is why I was OK with adding the 
libata.dma even for SATA.  Sometimes knobs are found useful by users, 
though perhaps not its original intended use.  Sometimes masking a 
hardware problem can help you get through the rest of your day on hold 
with vendor support :)


>> 2) Once we identified, over time, the set of drives affected by this 
>> 3112 quirk (aka drives that didn't fully comply to SATA spec), the 
>> debugging of corruption cases largely shifted to the standard routine: 
>> update the BIOS, replace the cables/RAM/power/mainboard/slot/etc. to be 
>> certain of problem location.
> 
> Except for the continued series of later SI + Nvidia chipset (mostly)
> pattern which seems unanswered but also being later chips I assume
> unrelated to this problem.

The SIL_FLAG_MOD15WRITE flag is set in sil_port_info[] is set according 
to the best info we have from SiI, which indicates that 3114 and 3512 do 
not have the same problem as the 3112.

	Jeff



  reply	other threads:[~2007-10-11 14:59 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-08 15:09 sil3114 data corruption Bernd Schubert
2007-10-10  9:12 ` Bernd Schubert
2007-10-11 12:09   ` [PATCHES] " Bernd Schubert
2007-10-11 12:15     ` [PATCH 1/3] " Bernd Schubert
2007-10-11 12:20       ` [PATCH 2/3] " Bernd Schubert
2007-10-11 12:33     ` [PATCH 3/3] faster workaround Bernd Schubert
2007-10-11 13:26       ` Alan Cox
2007-10-11 14:19         ` Jeff Garzik
2007-10-11 14:39           ` Bernd Schubert
2007-10-11 15:04             ` Jeff Garzik
2007-10-11 15:18               ` Bernd Schubert
2007-10-12 21:08                 ` Jeff Garzik
2007-10-15 10:18                   ` Bernd Schubert
2007-10-11 14:50           ` Alan Cox
2007-10-11 14:59             ` Jeff Garzik [this message]
2007-10-23  8:08               ` Tejun Heo
2007-10-23 17:28                 ` Bernd Schubert
2007-10-24 13:39                 ` Soeren Sonnenburg

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=470E3A35.4000104@garzik.org \
    --to=jeff@garzik.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bs@q-leap.de \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.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).