From: Tejun Heo <htejun@gmail.com>
To: Andrew Henry <adhenry@bredband.net>
Cc: linux-ide@vger.kernel.org
Subject: Re: 2.6.25: sata_sil freezes, hard resets port.
Date: Tue, 10 Jun 2008 12:18:58 +0900 [thread overview]
Message-ID: <484DF2A2.103@gmail.com> (raw)
In-Reply-To: <4846F3EA.2050408@bredband.net>
Andrew Henry wrote:
> Any news with this? I start to understand that this really is a missing
> function in the sata_sil driver: driver does not work well with power
> saving modes/standby on eSATA drives.
>
> I have created a cron script to 'ping' the drives usng sdparm -C start
> /dev/sdX every 3 minutes and the drives have been operating with RAID1
> and dmcrypt for 4 days non-stop without error.
>
> It does seem that this fault I am experiencing is only caused by
> incomplete driver. Can someone please acknowledge this?
It looks like bad interaction with link power saving to me. libata
currently inhibits all link power saving and doesn't configure device
side power saving either, so the link should never enter powersaving
mode but some "green" drives are known to take extreme measures to cut
down on power. At any rate, the drive and link should wake up when the
controller strobes the link w/ PHY reset no matter in which PS mode it's
in. I can't think of any good solution at the moment. Can you please
post the outputs of dmesg after the wake up failure (fdisk -l) and
"hdparm --Istdout /dev/sdX"?
--
tejun
next prev parent reply other threads:[~2008-06-10 3:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-04 19:58 2.6.25: sata_sil freezes, hard resets port Andrew Henry
2008-06-10 3:18 ` Tejun Heo [this message]
2008-06-11 18:42 ` Andrew Henry
2008-06-12 1:46 ` Tejun Heo
-- strict thread matches above, loose matches on Subject: below --
2009-01-13 9:50 Henry, Andrew
2008-09-10 13:23 Henry, Andrew
2008-09-29 2:59 ` Tejun Heo
2008-05-30 18:25 Andrew Henry
2008-05-30 8:26 Andrew Henry
[not found] <3ECBDC05781B3D48ABD520A01ABF2F9B12C589D4FA@SE-EX008.groupinfra.com>
2008-05-30 5:15 ` 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=484DF2A2.103@gmail.com \
--to=htejun@gmail.com \
--cc=adhenry@bredband.net \
--cc=linux-ide@vger.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).