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: Mon, 08 Feb 2010 11:40:58 +0900 [thread overview]
Message-ID: <4B6F79BA.6010003@kernel.org> (raw)
In-Reply-To: <4B6E46DA.9040308@teksavvy.com>
Hello,
On 02/07/2010 01:51 PM, Mark Lord wrote:
> Tim Small wrote:
>> Mark Lord wrote:
>>> My theory on the problem when I first had it here, was that doing
>>> a FLUSH_CACHE[_EXT] before any PIO command (eg. SMART) should prevent
>>> the problem. This was never explored further (by me or others).
>>>
>>
>> Would using "option libata force=pio4" be a simple way to start to test
>> this hypothesis?
> ..
>
> Yup. If the hypothesis is FALSE, then you'll still see trouble.
> Otherwise, it *might* be correct. ;)
But that would be a big *might*. The effect of PIO is a bit too
drastic to indicate postivity (as opposed to ruling out stuff).
Anyways, yeap, no harm in trying.
--
tejun
next prev parent reply other threads:[~2010-02-08 2:35 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
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 [this message]
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=4B6F79BA.6010003@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).