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: Wed, 01 Dec 2010 12:17:52 +0100 [thread overview]
Message-ID: <4CF62EE0.7040607@kernel.org> (raw)
In-Reply-To: <20101130210938.GF25668@bombadil.infradead.org>
Hello,
On 11/30/2010 10:09 PM, Kyle McMartin wrote:
>> Ok, running it, I haven't seen the issue across three suspends... Will
>> update when it inevitably happens.
>
> [10273.011241] ata1.00: internal command failure: stat=0xef
> ehi_desc="irq_stat 0x00400001, PHY RDY changed"
Hmmm, so it's a timing problem. For some reason, a PHY event is being
reported after reset is complete which unfortunately gets reported
while DIPM command is in progress. Hmmm... what's broken is that the
PHY event happens after reset is complete. Can you please attach the
output of "lspci -nn" and "hdparm -I /dev/sda"? Looks a lot like a
timing issue. Maybe we'll have to add a delay somewhere. :-(
--
tejun
next prev parent reply other threads:[~2010-12-01 11:17 UTC|newest]
Thread overview: 19+ 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
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 [this message]
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
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=4CF62EE0.7040607@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 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).