From: Tejun Heo <htejun@gmail.com>
To: Christian Mueller <Christian.Mueller@wdc.com>
Cc: 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>,
Mikael Pettersson <mikpe@it.uu.se>
Subject: Re: [smartmontools-support] inactive SATA drives won't stay in standby or sleep, PATA models did. (fwd)
Date: Wed, 08 Oct 2008 09:28:11 +0900 [thread overview]
Message-ID: <48EBFE9B.9070503@gmail.com> (raw)
In-Reply-To: <D73D40172004714D95D7A84AC3E68EC802282133@wdscexbe03.sc.wdc.com>
(cc'ing linux-ide and Mikael Pettersson)
Christian Mueller wrote:
> The messages I saw on the screen.
If the drive doesn't wake up and times out the smart command while
suspended (which probably is a bug in the firmware but it also can be
the controller's fault), then after the timeout, the driver should kick
in and reset the drive which will wake up the device and retry the
command. It's not the prettiest picture but it's still gonna work. In
Linda's case, it looks like the controller (sata_promise) went bonkers
on hardreset and requires power cycle to get back to working state.
That's why I asked Linda to try another controller.
Anyways, if you're seeing a similar problem, the driver or controller
probably can't do proper reset after timeout and I can't really help
with SAS driver on FreeBSD. :-P
Mikael, the original thread is the following.
http://article.gmane.org/gmane.linux.utilities.smartmontools/5842
Any ideas why hardreset doesn't work after SMART command timed out?
Thanks.
--
tejun
next parent reply other threads:[~2008-10-08 0:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <D73D40172004714D95D7A84AC3E68EC802282133@wdscexbe03.sc.wdc.com>
2008-10-08 0:28 ` Tejun Heo [this message]
2008-10-12 14:55 ` [smartmontools-support] inactive SATA drives won't stay in standby or sleep, PATA models did. (fwd) 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
2008-10-21 8:55 ` 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=48EBFE9B.9070503@gmail.com \
--to=htejun@gmail.com \
--cc=Christian.Mueller@wdc.com \
--cc=ballen@gravity.phys.uwm.edu \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@it.uu.se \
--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;
as well as URLs for NNTP newsgroup(s).