linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Lord <liml@rtr.ca>
To: Tejun Heo <htejun@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	michal.k.k.piotrowski@gmail.com, bryan@arbores.ca,
	linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: Stardom SATA HSM violation
Date: Fri, 07 Sep 2007 09:40:46 -0400	[thread overview]
Message-ID: <46E154DE.2060602@rtr.ca> (raw)
In-Reply-To: <46E0A253.7060803@gmail.com>

Tejun Heo wrote:
> Hello,
> 
> Mark Lord wrote:
>> I reported a very similar bug back a few releases ago.
>> Anyone who wants to try it themselves, can do this with hdparm-7.7 (from
>> sourceforge):
>>
>>    hdparm --drq-hsm-error /dev/sda
>>
>> Whether or not it hangs the machine does depend upon exactly which SATA
>> LLD is used,
>> and what model/revision of drive is installed.  But if it hangs for you
>> (eg. Tejun),
>> then you now have a way to reproduce a HSM error "on demand" for
>> testing.  :)
> 
> Neat.  Is this the FIFO-draining issue?

Yeah, that's the one.  And I still patch my own kernels to
automatically drain up to 512 words from the FIFO when this happens.

Works like a charm.  Patch below for demonstration purposes.

Signed-Off-By:  Mark Lord <mlord@pobox.com>
---

--- linux/drivers/ata/libata-sff.c.orig	2007-04-26 12:02:46.000000000 -0400
+++ linux/drivers/ata/libata-sff.c	2007-04-29 08:29:27.000000000 -0400
@@ -413,6 +413,24 @@
 	ap->ops->irq_on(ap);
 }
 
+static void ata_drain_fifo (struct ata_port *ap, struct ata_queued_cmd *qc)
+{
+	u8 stat = ata_chk_status(ap);
+	/*
+	 * Try to clear stuck DRQ if necessary.
+	 */
+	if ((stat & ATA_DRQ) && (!qc || qc->dma_dir != DMA_TO_DEVICE)) {
+		unsigned int i, limit = 512;
+		printk("Draining up to %u words from data FIFO.\n", limit);
+		for (i = 0; i < limit ; ++i) {
+			ioread16(ap->ioaddr.data_addr);
+			if (!(ata_chk_status(ap) & ATA_DRQ))
+				break;
+		}
+		printk("Drained %u/%u words.\n", i, limit);
+	}
+}
+
 /**
  *	ata_bmdma_drive_eh - Perform EH with given methods for BMDMA controller
  *	@ap: port to handle error for
@@ -469,7 +487,7 @@
 	}
 
 	ata_altstatus(ap);
-	ata_chk_status(ap);
+	ata_drain_fifo(ap, qc);
 	ap->ops->irq_clear(ap);
 
 	spin_unlock_irqrestore(ap->lock, flags);

  reply	other threads:[~2007-09-07 13:40 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <46CFA08E.6090604@arbores.ca>
2007-08-26 23:10 ` Stardom SATA HSM violation Michal Piotrowski
2007-09-03  8:53   ` Tejun Heo
2007-09-05 16:53     ` Andrew Morton
2007-09-05 17:23       ` Mark Lord
2007-09-05 19:38         ` Andrew Morton
2007-09-05 23:03           ` Mark Lord
2007-09-07  0:58         ` Tejun Heo
2007-09-07 13:40           ` Mark Lord [this message]
2007-09-27  7:05             ` Tejun Heo
2007-09-27 18:37               ` Alan Cox
2007-09-27 23:32                 ` Tejun Heo
2007-09-27 23:42                   ` Jeff Garzik
2007-09-27 23:52                     ` Tejun Heo
2007-09-28  3:56                       ` [PATCH] libata drain fifo on stuck DRQ " Mark Lord
2007-09-28  9:48                         ` Tejun Heo
2007-09-28  9:56                           ` Andrew Morton
2007-09-28 10:01                             ` Tejun Heo
2007-09-28 10:27                         ` Alan Cox
2007-09-28 13:41                           ` [PATCH] libata drain fifo on stuck DRQ HSM violation (try#2) Mark Lord
2007-09-29  6:24                             ` Jeff Garzik
2007-09-29  1:05                           ` [PATCH] libata drain fifo on stuck DRQ HSM violation Jeff Garzik
2007-09-29  6:28                             ` Alan Cox
2007-09-29 12:34                               ` Mark Lord
2007-09-28  3:52                   ` Stardom SATA " Mark Lord
2007-09-06 15:00     ` Bryan Woods
2007-09-07  0:58       ` 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=46E154DE.2060602@rtr.ca \
    --to=liml@rtr.ca \
    --cc=akpm@linux-foundation.org \
    --cc=bryan@arbores.ca \
    --cc=htejun@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.k.k.piotrowski@gmail.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 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).