linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Tejun Heo <htejun@gmail.com>
Cc: IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: [PATCH] libata: give devices one last chance even if recovery failed with -EINVAL
Date: Fri, 11 May 2007 18:10:58 -0400	[thread overview]
Message-ID: <4644E9F2.3000706@garzik.org> (raw)
In-Reply-To: <464465BB.5070203@gmail.com>

Tejun Heo wrote:
> After certain errors, some devices report complete garbage on
> IDENTIFY.  This can cause ata_dev_read_id() to fail with -EINVAL
> resulting in immediate disabling of the device.  Give the device one
> last chance after -EINVAL to allow recovery from such situations.  As
> -EINVAL is triggered very rarely, this shouldn't cause any noticeable
> affect on more common error paths.
> 
> Signed-off-by: Tejun Heo <htejun@gmail.com>
> Cc: Harald Dunkel <harald.dunkel@t-online.de>

applied



      reply	other threads:[~2007-05-11 22:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-11 12:46 [PATCH] libata: give devices one last chance even if recovery failed with -EINVAL Tejun Heo
2007-05-11 22:10 ` 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=4644E9F2.3000706@garzik.org \
    --to=jeff@garzik.org \
    --cc=htejun@gmail.com \
    --cc=linux-ide@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).