From: Mikael Pettersson <mikpe@it.uu.se>
To: Mikael Pettersson <mikpe@it.uu.se>
Cc: Tejun Heo <htejun@gmail.com>,
Christian Mueller <Christian.Mueller@wdc.com>,
Bruce Allen <ballen@gravity.phys.uwm.edu>,
Smartmontools Mailing List
<smartmontools-support@lists.sourceforge.net>,
LKML <linux-kernel@vger.kernel.org>,
IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: [smartmontools-support] inactive SATA drives won't stay in standby or sleep, PATA models did. (fwd)
Date: Tue, 21 Oct 2008 09:59:47 +0200 [thread overview]
Message-ID: <18685.35827.914278.413151@harpo.it.uu.se> (raw)
In-Reply-To: <18683.50533.786782.474536@harpo.it.uu.se>
On Mon, 20 Oct 2008 01:40:21 +0200, Mikael Pettersson wrote:
>On Mon, 13 Oct 2008 14:16:24 +0900, Tejun Heo wrote:
>>Mikael Pettersson wrote:
>>> - hardreset in sata_promise seems broken. I'll take a closer look
>>> at that in about a week's time (I'll be busy with other work the
>>> next couple of days).
>>
>>This looks like a rather serious problem, so please take a look at
>>this.
>
>I've done more tests now, and the problem is that errors detected
>outside of sata_promise itself, typically timeouts, don't trigger
>the pdc_reset_port() call needed to bring the ATA engine behind the
>port back to sanity.
I did a round of regression tests which identified another
related but different problem.
In kernels 2.6.24 and 2.6.25 sata_promise would actually recover
from the timeouts, while in kernels 2.6.26 and 2.6.27 it would not.
Before 2.6.26 sata_promise explicitly used sata_std_hardreset, but
in the "make reset related methods proper port operations" commit
(a1efdaba2dbd6fb89e23a87b66d3f4dd92c9f5af), Tejun changed sata_promise
to use the hardreset it now inherits from ata_sff_port_ops, namely
sata_sff_hardreset. This change looks accidental. The main difference
between these two procedures is that the sff version will poll the
legacy status register until the port becomes ready.
Changing sata_promise to use sata_std_hardreset in 2.6.26/.27
makes the EH after the timeouts much more reliable. Not as
tidy as with the previous ->prereset fix, but still working.
/Mikael
next prev parent reply other threads:[~2008-10-21 8:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <48EBFB63.20506@gmail.com>
2008-10-08 0:20 ` Christian Mueller
2008-10-08 0:28 ` Tejun Heo
2008-10-12 14:55 ` Mikael Pettersson
2008-10-13 5:16 ` Tejun Heo
2008-10-13 7:03 ` Mikael Pettersson
2008-10-13 7:08 ` Tejun Heo
2008-10-19 23:40 ` Mikael Pettersson
2008-10-21 4:18 ` Tejun Heo
2008-10-21 7:56 ` Mikael Pettersson
2008-10-21 9:02 ` Tejun Heo
2008-10-21 9:30 ` Mikael Pettersson
2008-10-21 7:59 ` Mikael Pettersson [this message]
2008-10-21 8:55 ` Tejun Heo
[not found] <Pine.LNX.4.64.0809142159550.18213@gc.phys.uwm.edu>
[not found] ` <48E1B8F8.3090205@gmail.com>
[not found] ` <48E26BDA.8080804@tlinx.org>
[not found] ` <48E26E61.2010705@gmail.com>
[not found] ` <48E34BC8.3050009@tlinx.org>
[not found] ` <48E6DE07.70706@gmail.com>
2008-10-07 0:37 ` Linda Walsh
2008-10-07 1:08 ` Tejun Heo
2008-10-07 1:36 ` Linda Walsh
2008-10-07 1:42 ` Tejun Heo
2008-10-07 10:13 ` Linda Walsh
2008-10-07 22:27 ` Linda Walsh
2008-10-07 23:59 ` 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=18685.35827.914278.413151@harpo.it.uu.se \
--to=mikpe@it.uu.se \
--cc=Christian.Mueller@wdc.com \
--cc=ballen@gravity.phys.uwm.edu \
--cc=htejun@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=smartmontools-support@lists.sourceforge.net \
/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
all inboxes | Powered by JetHome®