linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Robert Hancock <hancockrwd@gmail.com>
Cc: Mark Lord <kernel@teksavvy.com>, Seed <seedrubbish@gmail.com>,
	Jeff Garzik <jgarzik@pobox.com>,
	IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: [BUG] libahci returns stale result tf much of the time.
Date: Mon, 04 Oct 2010 11:18:03 +0200	[thread overview]
Message-ID: <4CA99BCB.8080904@gmail.com> (raw)
In-Reply-To: <4C9D33C0.8050900@gmail.com>

Hello,

On 09/25/2010 01:26 AM, Robert Hancock wrote:
>> And here's an example of the bug, which should work (as a demo)
>> for most folks out there with the same controller ahci / JMB360:
>>
>> Here, I'll use hdparm to do a "set acoustic" command
>> on a drive which does NOT have the "Acoustic Management" feature set.
>> Just look for the fd fd fd strings in the returned data,
>> and notice how the final IDENTIFY at the end works, but returns
>> bad ATA status 0x51 from the stale result_tf:
> 
> The d2h_fis area is supposed to be updated by the controller with
> the last FIS received from the device. Maybe this controller just
> isn't doing that for some reason?

Hmm... one possibility is that the controller takes some time to
update the area and the driver is reading it off too early.  Maybe
adding a delay would resolve the issue?  Mark, do you know whether
this problem is isolated to JMB360?

Thanks.

-- 
tejun

  reply	other threads:[~2010-10-04  9:18 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-24  5:34 [BUG] libahci returns stale result tf much of the time Mark Lord
2010-09-24  5:49 ` Seed
2010-09-24  6:27   ` Mark Lord
2010-09-24  7:01     ` Seed
2010-09-24 13:11       ` Mark Lord
2010-09-24 13:24         ` Mark Lord
2010-09-24 23:26           ` Robert Hancock
2010-10-04  9:18             ` Tejun Heo [this message]
2010-10-04 17:01               ` Mark Lord
2010-10-04 17:06                 ` Mark Lord
2010-10-04 17:31                   ` Mark Lord
2010-10-04 18:50                     ` Mark Lord
2010-10-04 19:27                       ` Jeff Garzik
2010-10-04 19:35                         ` Mark Lord
2010-10-04 19:42                           ` Jeff Garzik
2010-10-04 19:51                             ` Mark Lord
2010-10-05  7:07                               ` Tejun Heo
2010-10-05 14:06                                 ` Mark Lord
2010-10-05 16:06                                   ` Tejun Heo
2010-10-06  1:00                                     ` Robert Hancock
2010-10-14  8:53                                       ` [PATCH #upstream-fixes] libahci: fix result_tf handling after an ATA PIO data-in command Tejun Heo
2010-10-14 21:38                                         ` Mark Lord
2010-10-15  0:24                                           ` Robert Hancock
2010-10-15  8:45                                             ` Tejun Heo
2010-10-15 22:14                                               ` Mark Lord
2010-10-15  0:32                                         ` Robert Hancock
2010-10-15  8:45                                           ` Tejun Heo
2010-10-15  9:00                                         ` [PATCH UPDATED " 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=4CA99BCB.8080904@gmail.com \
    --to=htejun@gmail.com \
    --cc=hancockrwd@gmail.com \
    --cc=jgarzik@pobox.com \
    --cc=kernel@teksavvy.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=seedrubbish@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).