From: Bill Davidsen <davidsen@tmr.com>
To: David Sanchez <david.sanchez@lexbox.fr>
Cc: Jeff Garzik <jgarzik@pobox.com>, linux-kernel@vger.kernel.org
Subject: Re: How to Force PIO mode on sata promise (Linux 2.6.10)
Date: Thu, 22 Sep 2005 12:36:55 -0400 [thread overview]
Message-ID: <4332DDA7.4080901@tmr.com> (raw)
In-Reply-To: <17AB476A04B7C842887E0EB1F268111E026FBD@xpserver.intra.lexbox.org>
David Sanchez wrote:
> Hi Chris,
> It was a good idea but it doesn't resolve the problem...
>
> I add my card into the dma_black_list of the libata to force DMA disabled and the problem seems to no more appear...maybe PIO is so slow that the data has no time to be corrupted...
> But I can NOT affirm that the problem is the DMA.
>
> I try the linux kernel 2.4,2.6.11, 2.6.12 and 2.6.13. More I try 2 different toolchains and the problem persists...
>
> Another idea??
You disable DMA and the problem goes away, that seems to point to DMA as
the problem, and since others aren't having the same problem with the
DMA code in the kernel it certainly suggests the DMA hardware really is
the problem, or is causing it. It's remotely possible that the kernel
has a bug in the code just for your controller, although unlikely.
Have you run memtest86 on your memory? I have seen cases where memory
was marginal and using CPU and DMA was enough to cause it to fail, but
only when people had played with the memory timing in the BIOS. I
suspect the SATA disk has a higher datarate than anything else in your
system, so it could trigger some marginal cases in the memory system.
Unlikely, but possible.
ideas:
test your memory if you haven't
Check that your BIOS is up-to-date
check your BIOS memory timing settings
See if the controller came with tools to adjust DMA timing
try writing to a PATA drive while reading from the SATA
to generate high DMA rate, look for corruption there
try another controller of the same type
try another controler of another supported type
to see that it's not your drive
accept that your controller *belongs* on the blacklist
Since you asked for ideas, these are probably in order of easy to difficult.
--
-bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
last possible moment - but no longer" -me
next prev parent reply other threads:[~2005-09-22 16:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-22 8:03 How to Force PIO mode on sata promise (Linux 2.6.10) David Sanchez
2005-09-22 16:09 ` Chris Wedgwood
2005-09-22 16:36 ` Bill Davidsen [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-09-23 8:34 David Sanchez
2005-09-23 9:47 ` Clemens Koller
2005-09-21 14:48 David Sanchez
2005-09-22 9:04 ` Clemens Koller
2005-09-21 12:28 David Sanchez
2005-09-21 14:02 ` Clemens Koller
2005-09-22 3:01 ` Chris Wedgwood
2005-09-21 7:34 David Sanchez
2005-09-21 11:46 ` Jeff Garzik
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=4332DDA7.4080901@tmr.com \
--to=davidsen@tmr.com \
--cc=david.sanchez@lexbox.fr \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@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).