From: Tejun Heo <htejun@gmail.com>
To: ric@emc.com
Cc: Jeff Garzik <jeff@garzik.org>,
linux-ide@vger.kernel.org, Mark Lord <mlord@pobox.com>,
Jens Axboe <axboe@suse.de>
Subject: Re: [RFT] major libata update
Date: Wed, 17 May 2006 08:44:54 +0900 [thread overview]
Message-ID: <446A63F6.5030706@gmail.com> (raw)
In-Reply-To: <446A1A21.80501@emc.com>
[-- Attachment #1: Type: text/plain, Size: 2137 bytes --]
Ric Wheeler wrote:
> c001n01: 0: [ OK ]
> ata3: spurious interrupt (irq_stat 0x8 active_tag -84148995 sactive
> 0x2000000f)
> ata3: spurious SDB FIS 004040a1:10000000 ap->qc_active=2000000f
> qc_active=2000000f
> ata1: spurious interrupt (irq_stat 0x8 active_tag -84148995 sactive
> 0xfffc0)
> ata1: spurious SDB FIS 004040a1:00000020 ap->qc_active=000fffc0
> qc_active=000fffc0
> ata2: spurious interrupt (irq_stat 0x8 active_tag -84148995 sactive
> 0x7fffff3f)
> ata2: spurious SDB FIS 004040a1:00000080 ap->qc_active=7fffff3f
> qc_active=7fffff3f
> ata1: spurious interrupt (irq_stat 0x8 active_tag -84148995 sactive
> 0x7fffff9f)
> ata1: spurious SDB FIS 004040a1:00000040 ap->qc_active=7fffff9f
> qc_active=7fffff9f
> c001n03: 0: [ OK ]
> ata1: spurious interrupt (irq_stat 0x8 active_tag -84148995 sactive
> 0x7ffe7fff)
> ata1: spurious SDB FIS 004040a1:00010000 ap->qc_active=7ffe7fff
> qc_active=7ffe7fff
> c001n04: 0: [ OK ]
> ata3: spurious interrupt (irq_stat 0x8 active_tag -84148995 sactive 0x31)
> ata3: spurious SDB FIS 004040a1:00000008 ap->qc_active=00000031
> qc_active=00000031
> ata3: spurious interrupt (irq_stat 0x8 active_tag -84148995 sactive
> 0x7fff800f)
> ata3: spurious SDB FIS 004040a1:00004000 ap->qc_active=7fff800f
> qc_active=7fff800f
> c001n06: 1: [ FAIL ]
> c001n07: 0: [ OK ]
> ata1: spurious interrupt (irq_stat 0x8 active_tag -84148995 sactive
> 0x7ffffcff)
> ata1: spurious SDB FIS 004040a1:00000200 ap->qc_active=7ffffcff
> qc_active=7ffffcff
> c001n08: 0: [ OK ]
> ata1: spurious interrupt (irq_stat 0x8 active_tag -84148995 sactive
> 0x4fffffff)
> ata1: spurious SDB FIS 004040a1:20000000 ap->qc_active=4fffffff
> qc_active=4fffffff
Hmmm.. The drive is issuing SDB FIS which completes already completed
tags. This could be dangerous. Depending on timing, it might end up
finishing a command which occupied the slot which hasn't been processed
yet. If a drive does this, NCQ shouldn't be enabled for it. Can you
post full boot dmesg?
I'm attaching slightly modified version of the debug patch just in case.
It will probably show the same thing.
--
tejun
[-- Attachment #2: patch --]
[-- Type: text/plain, Size: 1042 bytes --]
diff --git a/drivers/scsi/ahci.c b/drivers/scsi/ahci.c
index 45fd71d..f9eeb15 100644
--- a/drivers/scsi/ahci.c
+++ b/drivers/scsi/ahci.c
@@ -876,6 +876,7 @@ static void ahci_host_intr(struct ata_po
struct ata_eh_info *ehi = &ap->eh_info;
u32 status, qc_active;
int rc;
+ u32 orig_qc_active = ap->qc_active;
status = readl(port_mmio + PORT_IRQ_STAT);
writel(status, port_mmio + PORT_IRQ_STAT);
@@ -916,10 +917,19 @@ static void ahci_host_intr(struct ata_po
return;
}
- if (ata_ratelimit())
+ if (ata_ratelimit()) {
ata_port_printk(ap, KERN_INFO, "spurious interrupt "
"(irq_stat 0x%x active_tag %d sactive 0x%x)\n",
status, ap->active_tag, ap->sactive);
+ if (status & PORT_IRQ_SDB_FIS) {
+ struct ahci_port_priv *pp = ap->private_data;
+ u32 *sdb_fis = pp->rx_fis + 0x58;
+
+ ata_port_printk(ap, KERN_INFO, "spurious SDB FIS "
+ "%08x:%08x orig_qc_active=%08x qc_active=%08x\n",
+ sdb_fis[0], sdb_fis[1], orig_qc_active, qc_active);
+ }
+ }
}
static void ahci_irq_clear(struct ata_port *ap)
next prev parent reply other threads:[~2006-05-16 23:44 UTC|newest]
Thread overview: 115+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-15 17:00 [RFT] major libata update Jeff Garzik
2006-05-15 17:18 ` Andrew Morton
2006-05-15 18:06 ` Jeff Garzik
2006-05-15 19:06 ` Arkadiusz Miskiewicz
2006-05-15 20:45 ` Jeff Garzik
2006-05-15 19:33 ` Mark Lord
2006-05-15 22:52 ` Tejun Heo
2006-05-15 18:15 ` Jeff Garzik
2006-05-15 18:27 ` Andrew Morton
2006-05-15 18:44 ` Jeff Garzik
2006-05-15 18:37 ` Alan Cox
2006-05-15 17:19 ` Alan Cox
2006-05-15 17:13 ` Jeff Garzik
2006-05-15 18:29 ` Tomasz Torcz
2006-05-15 18:43 ` Jeff Garzik
2006-05-15 23:32 ` Tejun Heo
2006-05-15 23:49 ` Jeff Garzik
2006-05-16 0:04 ` Tejun Heo
2006-05-16 2:15 ` Tejun Heo
2006-05-15 19:15 ` Jeff Garzik
2006-05-15 23:02 ` Wakko Warner
2006-05-15 23:00 ` Jeff Garzik
2006-05-15 23:13 ` Wakko Warner
2006-05-15 23:19 ` Jeff Garzik
2006-05-15 23:40 ` Alan Cox
2006-05-15 23:50 ` Wakko Warner
2006-05-15 23:38 ` Alan Cox
2006-05-15 23:47 ` Wakko Warner
2006-05-15 23:45 ` Jeff Garzik
2006-05-15 23:30 ` Avuton Olrich
2006-05-15 23:36 ` Tejun Heo
2006-05-15 23:54 ` Jeff Garzik
2006-05-16 0:08 ` Avuton Olrich
2006-05-16 3:36 ` Avuton Olrich
2006-05-16 3:51 ` Jeff Garzik
2006-05-16 4:33 ` Avuton Olrich
2006-05-16 14:57 ` Linus Torvalds
2006-05-17 15:25 ` OGAWA Hirofumi
2006-05-17 23:40 ` Linus Torvalds
2006-05-17 23:48 ` Jeff Garzik
2006-05-18 1:48 ` Alan Cox
2006-05-17 23:49 ` Linus Torvalds
2006-05-16 15:02 ` Jeff Garzik
2006-05-16 3:55 ` Tejun Heo
2006-05-16 4:37 ` Avuton Olrich
2006-05-16 11:36 ` Ric Wheeler
2006-05-16 14:25 ` Jeff Garzik
2006-05-16 15:24 ` Tejun Heo
2006-05-16 18:29 ` Ric Wheeler
2006-05-16 21:41 ` Ric Wheeler
2006-05-16 22:02 ` Jeff Garzik
2006-05-16 23:11 ` Eric D. Mudama
2006-05-17 2:13 ` Ric Wheeler
2006-05-16 23:23 ` Tejun Heo
2006-05-17 2:09 ` Ric Wheeler
2006-05-16 23:44 ` Tejun Heo [this message]
2006-05-16 23:53 ` Jeff Garzik
2006-05-17 0:00 ` Jeff Garzik
2006-05-17 0:29 ` Tejun Heo
2006-05-17 1:08 ` Jeff Garzik
2006-05-17 1:27 ` Tejun Heo
2006-05-17 2:26 ` Jeff Garzik
2006-05-17 3:05 ` Tejun Heo
2006-05-22 7:19 ` Jeff Garzik
2006-05-23 13:59 ` Tejun Heo
2006-05-17 0:31 ` Jeff Garzik
2006-05-17 0:50 ` Tejun Heo
2006-05-17 0:57 ` Tejun Heo
2006-05-17 2:22 ` Ric Wheeler
2006-05-17 1:37 ` Tejun Heo
2006-05-17 3:57 ` Ric Wheeler
2006-05-17 4:44 ` Tejun Heo
2006-05-17 11:30 ` Ric Wheeler
2006-05-17 20:45 ` Ric Wheeler
2006-05-17 21:01 ` Mark Lord
2006-05-17 21:04 ` Jeff Garzik
2006-05-17 21:50 ` Tejun Heo
2006-05-17 21:56 ` Mark Lord
2006-05-17 22:00 ` Jeff Garzik
2006-05-17 22:03 ` Mark Lord
2006-05-17 22:13 ` Jeff Garzik
2006-05-18 3:33 ` Ric Wheeler
2006-05-18 3:26 ` Tejun Heo
2006-05-18 11:58 ` Ric Wheeler
2006-05-18 12:52 ` Mark Lord
2006-05-18 13:22 ` Ric Wheeler
2006-05-18 13:37 ` Jens Axboe
2006-05-17 1:13 ` Jeff Garzik
2006-05-17 1:14 ` Jeff Garzik
2006-05-17 2:16 ` Ric Wheeler
2006-05-16 23:34 ` Jeff Garzik
2006-05-16 23:53 ` Tejun Heo
2006-05-17 2:05 ` Andrew Morton
2006-05-17 4:49 ` Tejun Heo
2006-05-17 4:56 ` Andrew Morton
2006-05-17 5:14 ` Tejun Heo
2006-05-17 6:35 ` Tejun Heo
2006-05-18 11:24 ` Albert Lee
2006-05-18 11:33 ` Tejun Heo
2006-05-19 10:37 ` Albert Lee
2006-05-19 11:03 ` Tejun Heo
2006-05-22 3:51 ` [PATCH 1/1] libata: use polling pio for identify device Albert Lee
2006-05-22 6:24 ` Jeff Garzik
2006-05-23 2:27 ` Albert Lee
2006-05-18 23:07 ` [RFT] major libata update Andrew Morton
2006-05-19 1:14 ` Tejun Heo
2006-05-19 2:06 ` Jeff Garzik
2006-05-19 2:16 ` Tejun Heo
2006-05-22 7:22 ` Jeff Garzik
2006-05-21 23:51 ` Michael Sterrett -Mr. Bones.-
2006-05-22 2:42 ` Tejun Heo
2006-05-22 3:42 ` Michael Sterrett -Mr. Bones.-
2006-05-22 6:23 ` Michael Sterrett -Mr. Bones.-
-- strict thread matches above, loose matches on Subject: below --
2006-05-17 7:35 Matthieu CASTET
2006-05-18 0:36 Brown, Len
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=446A63F6.5030706@gmail.com \
--to=htejun@gmail.com \
--cc=axboe@suse.de \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=mlord@pobox.com \
--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 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).