All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Lord <liml@rtr.ca>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: IDE/ATA development list <linux-ide@vger.kernel.org>,
	Jens Axboe <axboe@suse.de>, Ric Wheeler <ric@emc.com>
Subject: Re: libata EH appears to be NFG up to 2.6.17 (at least).
Date: Thu, 6 Jul 2006 17:24:13 -0400	[thread overview]
Message-ID: <200607061724.13448.liml@rtr.ca> (raw)
In-Reply-To: <44AD77D5.90905@rtr.ca>

On Thursday 06 July 2006 16:51, Mark Lord wrote:
>..
> All drivers, all architectures.  Dunno about 2.6.18-rc1 yet.
>
> This patch (below) appears to fix it, but I really need your opinion
> on its correctness.  My apologies in advance for the likely bad whitespace,
> as I don't currently have access to my usual patch-mailer at present.

Whoops.. got the wrong function when regenerating the patch.
Here it is again, on the correct lines:

Enable libata-scsi to report correct sense data on errors.

Signed-off-by:  Mark Lord <mlord@pobox.com>
---
--- linux/drivers/scsi/libata-scsi.c.orig	2006-07-06 17:09:54.000000000 -0400
+++ linux/drivers/scsi/libata-scsi.c	2006-07-06 17:17:43.000000000 -0400
@@ -667,6 +667,13 @@
 	qc->ap->ops->tf_read(qc->ap, tf);
 
 	/*
+	 * Restore the error bit, which got cleared when the
+	 * interrupt handler first read the ata_status.
+	 */
+	if (qc->err_mask & AC_ERR_DEV)
+		tf->command |= ATA_ERR;
+
+	/*
 	 * Use ata_to_sense_error() to map status register bits
 	 * onto sense key, asc & ascq.
 	 */

  reply	other threads:[~2006-07-06 21:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-06 20:37 libata EH appears to be NFG up to 2.6.17 (at least) Mark Lord
2006-07-06 20:47 ` Jeff Garzik
2006-07-06 20:51   ` Mark Lord
2006-07-06 21:24     ` Mark Lord [this message]
2006-07-06 22:09       ` Jeff Garzik
2006-07-06 23:22         ` Ric Wheeler
2006-07-07 13:03         ` Mark Lord
2006-07-08 16:56           ` Tejun Heo

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=200607061724.13448.liml@rtr.ca \
    --to=liml@rtr.ca \
    --cc=axboe@suse.de \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=ric@emc.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.