From: Tejun Heo <tj@kernel.org>
To: Kyle McMartin <kyle@mcmartin.ca>
Cc: Jeff Garzik <jeff@garzik.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-ide@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [git patches] libata updates for 2.6.37
Date: Tue, 30 Nov 2010 17:29:06 +0100 [thread overview]
Message-ID: <4CF52652.4030802@kernel.org> (raw)
In-Reply-To: <20101130153839.GM15818@bombadil.infradead.org>
On 11/30/2010 04:38 PM, Kyle McMartin wrote:
> On Tue, Nov 30, 2010 at 03:13:58PM +0100, Tejun Heo wrote:
>>> Tejun, any ideas how I can debug this?
>>
>> Hmm... DIPM commands are failing with AC_ERR_OTHER. Other than DIPM
>> not being configured and speed capped at 1.5Gbps, the machine works
>> fine afterwards, right? Are you up for applying debug patches?
>>
>
> Yup, it's chugging along happily, though I notice kernel builds are
> taking a minute or two longer (but I don't bother to time them so it's
> purely subjective.)
>
> Be happy to apply any debug patches, but I plan on replacing the drive
> with a faster one at some point in the next few weeks.
Can you please apply the following patch and report the resulting
kernel log? You're on ahci, right?
diff --git a/drivers/ata/libahci.c b/drivers/ata/libahci.c
index ebc08d6..b1c39db 100644
--- a/drivers/ata/libahci.c
+++ b/drivers/ata/libahci.c
@@ -1560,6 +1560,10 @@ static void ahci_error_intr(struct ata_port *ap, u32 irq_stat)
}
/* okay, let's hand over to EH */
+ if (active_qc && ata_tag_internal(active_qc->tag))
+ ata_dev_printk(active_qc->dev, KERN_WARNING,
+ "ahci: internal command failure, irq_stat=0x%x\n",
+ irq_stat);
if (irq_stat & PORT_IRQ_FREEZE)
ata_port_freeze(ap);
diff --git a/drivers/ata/libata-core.c b/drivers/ata/libata-core.c
index 7f77c67..7cf236b 100644
--- a/drivers/ata/libata-core.c
+++ b/drivers/ata/libata-core.c
@@ -1668,6 +1668,10 @@ unsigned ata_exec_internal_sg(struct ata_device *dev,
/* perform minimal error analysis */
if (qc->flags & ATA_QCFLAG_FAILED) {
+ ata_dev_printk(dev, KERN_WARNING,
+ "internal command failure: stat=0x%x ehi_desc=\"%s\"\n",
+ qc->tf.command, dev->link->eh_info.desc);
+
if (qc->result_tf.command & (ATA_ERR | ATA_DF))
qc->err_mask |= AC_ERR_DEV;
next prev parent reply other threads:[~2010-11-30 16:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-22 1:23 [git patches] libata updates for 2.6.37 Jeff Garzik
2010-11-29 18:07 ` Kyle McMartin
2010-11-30 14:13 ` Tejun Heo
2010-11-30 15:38 ` Kyle McMartin
2010-11-30 16:29 ` Tejun Heo [this message]
2010-11-30 16:31 ` Kyle McMartin
2010-11-30 17:53 ` Kyle McMartin
2010-11-30 21:09 ` Kyle McMartin
2010-12-01 11:17 ` Tejun Heo
2010-12-01 12:44 ` Kyle McMartin
2010-12-01 14:19 ` Tejun Heo
2010-12-01 15:50 ` Kyle McMartin
2010-12-01 20:09 ` Kyle McMartin
2010-12-02 10:17 ` Tejun Heo
2010-12-02 21:23 ` Kyle McMartin
2010-12-03 10:10 ` Tejun Heo
2010-12-03 11:59 ` Kyle McMartin
2010-12-06 16:07 ` Kyle McMartin
2010-12-06 17:46 ` Tejun Heo
2010-12-02 12:56 ` debug kernel using two laptops without serial port Stanley Gan
2010-12-02 13:17 ` Borislav Petkov
2010-12-02 14:41 ` 答复: " Stanley Gan
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=4CF52652.4030802@kernel.org \
--to=tj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=jeff@garzik.org \
--cc=kyle@mcmartin.ca \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 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.