From: Tejun Heo <tj@kernel.org>
To: Mark Lord <kernel@teksavvy.com>
Cc: Tim Small <tim@buttersideup.com>,
Justin Piszcz <jpiszcz@lucidpixels.com>,
"smartmontools-support@lists.sourceforge.net"
<smartmontools-support@lists.sourceforge.net>,
linux-ide@vger.kernel.org
Subject: Re: [smartmontools-support] SATA drive reset/disable events on ICH7 ata_piix when polling SMART info
Date: Sat, 06 Feb 2010 12:39:31 +0900 [thread overview]
Message-ID: <4B6CE473.7060901@kernel.org> (raw)
In-Reply-To: <4B6C91F3.5090809@teksavvy.com>
Hello,
On 02/06/2010 06:47 AM, Mark Lord wrote:
>> 2. A few failures were seen with the Seagate drives as well (see last
>> bits of the email), similarly with no apparent bad SMART attributes.
> ..
>
> I have observed (and reported) the same issue in the past,
> on Hitachi and Seagate drives.
>
> The only constants seem to be libata and ICH7/8.
> We must have a bug somewhere in there.
In piix mode or ahci mode? If in piix mode, ich7 and 8 would behave
quite differently. ICH8 has SIDPR so it can hardreset while 7 can't.
ICH SIDPR access had a hardware problem where write to SControl to
clear DET is sometimes ignored which led to occassional hardreset
failure which got fixed recently. The reason why ich's are involved
in those incidents could just be that they are extremely popular.
Things to try after such completely drive shutdown are...
* Disconnect the drive from the host but do not remove power.
Reconnect the drive to a different port and/or controller, does the
drive work there?
* Power-cycle the drive (and issue manual rescan if necessary). Does
the drive get recognized again?
* Disconnect the drive and connect a different drive to the port.
Does the port work?
* Soft reset the machine. Can BIOS recognize the drive?
In many cases I've seen, it's usually that the drive's firmware is
completely hung and only power cycling the drive brought it back. But
then again, there have been some number of cases which didn't get
diagnosed properly, so it's definitely possible that we're doing
something wrong in the driver.
Anyways, if it happens again, please try the above and try to find out
whether the controller or the drive is hung. Also, please keep in
mind that timeouts on 0xEA (flush) is very often indicative of power
related issues. FLUSH spikes power consumption and surprisingly many
PSUs fail to sustain proper voltage over that, so powering up a
separate PSU and connecting only the hard drive to it and see what
happens is often interesting too.
Thanks.
--
tejun
next prev parent reply other threads:[~2010-02-06 8:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-05 14:07 SATA drive reset/disable events on ICH7 ata_piix when polling SMART info Tim Small
2010-02-05 14:17 ` [smartmontools-support] " Justin Piszcz
2010-02-05 14:31 ` Tim Small
2010-02-05 14:48 ` Justin Piszcz
2010-02-05 21:47 ` Mark Lord
2010-02-06 3:39 ` Tejun Heo [this message]
2010-02-06 15:26 ` Tim Small
2010-02-06 17:30 ` Mark Lord
2010-02-06 22:22 ` Tim Small
2010-02-07 4:51 ` Mark Lord
2010-02-08 2:40 ` Tejun Heo
2010-02-08 13:03 ` Tim Small
2010-02-08 2:49 ` 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=4B6CE473.7060901@kernel.org \
--to=tj@kernel.org \
--cc=jpiszcz@lucidpixels.com \
--cc=kernel@teksavvy.com \
--cc=linux-ide@vger.kernel.org \
--cc=smartmontools-support@lists.sourceforge.net \
--cc=tim@buttersideup.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).