From: Tejun Heo <htejun@gmail.com>
To: Mark Paulus <mark.paulus@verizonbusiness.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: sata_sil issue on 2.6.22
Date: Wed, 28 Nov 2007 10:21:34 +0900 [thread overview]
Message-ID: <474CC29E.8020102@gmail.com> (raw)
In-Reply-To: <47434526.7010304@verizonbusiness.com>
[-- Attachment #1: Type: text/plain, Size: 1140 bytes --]
Hello,
Mark Paulus wrote:
> sata_sil 0000:02:0b.0: version 2.2
> ACPI: PCI Interrupt 0000:02:0b.0[A] -> GSI 22 (level, low) -> IRQ 18
> scsi0 : sata_sil
> scsi1 : sata_sil
> ata1: SATA max UDMA/100 cmd 0xe0812080 ctl 0xe081208a bmdma 0xe0812000
> irq 18
> ata2: SATA max UDMA/100 cmd 0xe08120c0 ctl 0xe08120ca bmdma 0xe0812008
> irq 18
> ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
> ata1.00: ATA-5: ST310216A, 3.01, max UDMA/100
> ata1.00: 19541088 sectors, multi 16: LBA ata1.00: applying bridge limits
> ata1.00: failed to IDENTIFY (I/O error, err_mask=0x40)
> ata1.00: revalidation failed (errno=-5)
> ata1: failed to recover some devices, retrying in 5 secs
> ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
> ata1.00: failed to set xfermode (err_mask=0x40)
> ata1.00: limiting speed to UDMA/100:PIO3
> ata1: failed to recover some devices, retrying in 5 secs
> ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
> ata1.00: failed to set xfermode (err_mask=0x40)
It looks like for some reason the port is being frozen repeatedly. Can
you please apply the attached patch and post the dmesg?
Thanks.
--
tejun
[-- Attachment #2: debug.patch --]
[-- Type: text/x-patch, Size: 703 bytes --]
---
drivers/ata/sata_sil.c | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
Index: tree0/drivers/ata/sata_sil.c
===================================================================
--- tree0.orig/drivers/ata/sata_sil.c
+++ tree0/drivers/ata/sata_sil.c
@@ -390,11 +390,15 @@ static void sil_host_intr(struct ata_por
ap->eh_info.serror |= serror;
}
+ ata_port_printk(ap, KERN_INFO, "XXX SATA_IRQ, serror=0x%x\n",
+ serror);
goto freeze;
}
- if (unlikely(!qc))
+ if (unlikely(!qc)) {
+ ata_port_printk(ap, KERN_INFO, "XXX DMA completion w/o qc\n");
goto freeze;
+ }
if (unlikely(qc->tf.flags & ATA_TFLAG_POLLING)) {
/* this sometimes happens, just clear IRQ */
next prev parent reply other threads:[~2007-11-28 1:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-20 20:35 sata_sil issue on 2.6.22 Mark Paulus
2007-11-28 1:21 ` Tejun Heo [this message]
2007-11-30 15:56 ` Mark Paulus
2007-12-04 2:54 ` Tejun Heo
2007-12-05 14:29 ` Mark Paulus
2007-12-05 14:33 ` Tejun Heo
2007-12-05 14:49 ` Mark Paulus
2007-12-06 0:25 ` Tejun Heo
2007-12-06 2:10 ` 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=474CC29E.8020102@gmail.com \
--to=htejun@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=mark.paulus@verizonbusiness.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).