From: Peter Favrholdt <linux-ide@how.dk>
To: Tejun Heo <tj@kernel.org>, linux-ide@vger.kernel.org
Subject: Re: [PATCH #upstream-fixes] sata_promise: request follow-up SRST
Date: Sun, 23 Nov 2008 23:38:31 +0100 [thread overview]
Message-ID: <4929DB67.1090702@how.dk> (raw)
In-Reply-To: <49263F80.2060607@kernel.org>
Hi Tejun and list,
This mail just to say I'm alive and testing the patch but so far no
errors (on my hardware).
Tejun Heo wrote:
> sata_promise hardreset doesn't seem to be able to acquire the initial
> D2H Reg FIS after hardreset leading to hardreset timeouts. Request
> follow-up SRST.
>
> http://article.gmane.org/gmane.linux.ide/36186
>
> Signed-off-by: Tejun Heo <tj@kernel.org>
> ---
> Peter, can you please test this one too? It's essentially the same
> code just slightly prettier. Mikael, what do you think about this?
I'm still testing the new patch (on 2.6.27.7), but so far I haven't had
any failures - it seems my hardware has started to behave well - very
unfortunate ;-)
I'll keep on testing - hopefully I'll see some of the usual errors soon
- and the new patch recovers alright.
Best regards,
I'm still testing the new patch (on 2.6.27.7), but so far I haven't had
any failures - it seems my hardware has started to behave well - very
unfortunate ;-)
> Jeff, please commit only after Peter's verification and Mikael's ACK.
I'll keep on testing - hopefully I'll see some of the usual errors soon
- and the new patch will recover alright. I'll keep you updated.
Best regards,
Peter
> drivers/ata/sata_promise.c | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/ata/sata_promise.c b/drivers/ata/sata_promise.c
> index ba9a257..917038a 100644
> --- a/drivers/ata/sata_promise.c
> +++ b/drivers/ata/sata_promise.c
> @@ -710,7 +710,12 @@ static int pdc_sata_hardreset(struct ata_link *link, unsigned int *class,
> unsigned long deadline)
> {
> pdc_reset_port(link->ap);
> - return sata_sff_hardreset(link, class, deadline);
> +
> + /* sata_promise can't reliably acquire the first D2H Reg FIS
> + * after hardreset. Do non-waiting hardreset and request
> + * follow-up SRST.
> + */
> + return sata_std_hardreset(link, class, deadline);
> }
>
> static void pdc_error_handler(struct ata_port *ap)
next prev parent reply other threads:[~2008-11-23 22:38 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-13 21:21 FYI: BUG in SATA Promise 300 TX4 (2.6.24 - 2.6.27-3) w/Linux Linda Walsh
2008-11-16 6:04 ` Tejun Heo
2008-11-16 11:08 ` Mikael Pettersson
2008-11-16 14:24 ` Tejun Heo
2008-11-16 16:48 ` Brad Campbell
2008-11-17 2:01 ` Tejun Heo
2008-11-16 17:34 ` Peter Favrholdt
2008-11-16 17:39 ` Peter Favrholdt
2008-11-17 2:01 ` Tejun Heo
2008-11-17 11:47 ` Peter Favrholdt
2008-11-18 1:11 ` Tejun Heo
2008-11-18 18:03 ` Peter Favrholdt
2008-11-19 1:55 ` Tejun Heo
2008-11-20 10:22 ` Peter Favrholdt
2008-11-20 11:10 ` Mikael Pettersson
2008-11-21 4:42 ` Tejun Heo
2008-11-21 4:56 ` [PATCH #upstream-fixes] sata_promise: request follow-up SRST Tejun Heo
2008-11-22 16:30 ` Mikael Pettersson
2008-11-23 22:38 ` Peter Favrholdt [this message]
2008-11-25 13:00 ` Peter Favrholdt
2008-11-26 2:46 ` Tejun Heo
2008-11-26 8:12 ` Peter Favrholdt
2008-11-26 23:07 ` Peter Favrholdt
2008-11-25 17:27 ` Jeff Garzik
2008-11-25 21:17 ` Mikael Pettersson
2008-11-29 21:50 ` Mikael Pettersson
2008-11-30 15:06 ` Peter Favrholdt
2009-02-10 4:30 ` Jeff Garzik
2009-02-10 17:28 ` Mikael Pettersson
2009-02-10 21:13 ` Jeff Garzik
2009-02-23 12:17 ` [PATCH #upstream-fixes] sata_promise: request follow-up SRST - it works Peter Favrholdt
-- strict thread matches above, loose matches on Subject: below --
2009-09-25 5:24 [PATCH #upstream-fixes] sata_promise: request follow-up SRST Walter Hutchins
2009-09-26 2:57 ` Robert Hancock
2009-09-26 18:42 ` Walter Hutchins
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=4929DB67.1090702@how.dk \
--to=linux-ide@how.dk \
--cc=linux-ide@vger.kernel.org \
--cc=tj@kernel.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).