All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Mikael Pettersson <mikpe@it.uu.se>
Cc: linux-ide@vger.kernel.org,
	thomas schorpp <thomas.schorpp@googlemail.com>
Subject: Re: [PATCH 2.6.33-rc3] sata_promise: don't classify overruns as HSM errors
Date: Tue, 12 Jan 2010 14:38:31 -0500	[thread overview]
Message-ID: <4B4CCFB7.6090108@pobox.com> (raw)
In-Reply-To: <19273.998.753256.526176@pilspetsen.it.uu.se>

On 01/09/2010 05:32 PM, Mikael Pettersson wrote:
> When sata_promise encounters an overrun or underrun error it
> translates that to a libata AC_ERR_HSM, causing a hard reset.
> Since over/under-runs were thought to be rare and transient,
> this action seemed reasonable.
>
> Unfortunately it turns out that the controller throws overrun
> errors when e.g. hal polls a CD or DVD writer containing blank
> media, causing long sequences of hard resets and retries before
> EH finally gives up.
>
> This patch updates sata_promise to classify over/under-runs as
> AC_ERR_OTHER instead. This allows libata EH and upper layers to
> retry or fail the operation as they see fit without the disruption
> caused by repeated hard resets.
>
> This fixes a problem using a DVD-RAM drive with sata_promise,
> reported by Thomas Schorpp. I also tested it on a DVD-RW drive.
>
> Signed-off-by: Mikael Pettersson<mikpe@it.uu.se>
> Tested-by: thomas schorpp<thomas.schorpp@googlemail.com>
> ---
>   drivers/ata/sata_promise.c |    2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)

applied



      reply	other threads:[~2010-01-12 19:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-09 22:32 [PATCH 2.6.33-rc3] sata_promise: don't classify overruns as HSM errors Mikael Pettersson
2010-01-12 19:38 ` Jeff Garzik [this message]

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=4B4CCFB7.6090108@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=mikpe@it.uu.se \
    --cc=thomas.schorpp@googlemail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.