public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "Jan Engelhardt" <jengelh@medozas.de>,
	"Martin MOKREJŠ" <mmokrejs@ribosome.natur.cuni.cz>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.23.17 & 2.6.24.5 and maybe earlier: pata_marvell: need to disable DMA to get rid of '(ATA bus error)', 'ata7.00: status: { DRDY ERR }', 'ata7.00: error: { ICRC ABRT }'
Date: Fri, 02 May 2008 20:42:53 -0600	[thread overview]
Message-ID: <481BD12D.1030406@shaw.ca> (raw)
In-Reply-To: <fa.qfeYSQtlsXzGvFvBQEdF9TFFpNg@ifi.uio.no>

Alan Cox wrote:
>>> libata.dma=3 will stop DMA being used for CF devices (except those that
>>> decide to pretend to be ATA classes). This one comes up a lot as many CF
>>> adapters are simply not adequate for UDMA.
>> Perhaps the kernel could do this automatically once it sees the
>> status code?
> 
> We then hurt all the people with perfectly good working UDMA CF devices.
> The kernel will eventually fall back from UDMA to PIO but it favours
> working hardware by default.

I suspect they meant fall back on seeing the ABRT/ICRC error combination 
- which it does, eventually. Falling back on one occurrence would be too 
aggressive, though, as they can happen once in a blue moon, so there's 
little reason to slow down a working setup forever because of it..

       reply	other threads:[~2008-05-03  2:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.+9Q+WQnyiYTlpbXVIzn6aT2/gS0@ifi.uio.no>
     [not found] ` <fa.fKUfeQYS9BFD60fOMormQ25ard4@ifi.uio.no>
     [not found]   ` <fa.QYXSW2xjSxf6xnmd0rQGJhHLnrc@ifi.uio.no>
     [not found]     ` <fa.qfeYSQtlsXzGvFvBQEdF9TFFpNg@ifi.uio.no>
2008-05-03  2:42       ` Robert Hancock [this message]
2008-05-06 12:44         ` 2.6.23.17 & 2.6.24.5 and maybe earlier: pata_marvell: need to disable DMA to get rid of '(ATA bus error)', 'ata7.00: status: { DRDY ERR }', 'ata7.00: error: { ICRC ABRT }' Martin MOKREJŠ
2008-05-06 13:08           ` Alan Cox
2008-05-06 14:54             ` Martin MOKREJŠ
2008-05-06 15:04               ` Alan Cox
2008-05-06 16:24                 ` Martin MOKREJŠ
2008-05-06 19:04                   ` Alan Cox
2008-05-06 23:42                     ` Martin MOKREJŠ
2008-05-07  7:25                       ` Alan Cox
2008-05-01 17:28 Martin MOKREJŠ
2008-05-01 19:08 ` Alan Cox
2008-05-01 21:24   ` Martin MOKREJŠ
2008-05-01 23:51   ` Jan Engelhardt
2008-05-02  9:57     ` Alan Cox

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=481BD12D.1030406@shaw.ca \
    --to=hancockr@shaw.ca \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jengelh@medozas.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmokrejs@ribosome.natur.cuni.cz \
    /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