From: Tejun Heo <tj@kernel.org>
To: Alex Vandiver <alex@chmrr.net>
Cc: linux-ide <linux-ide@vger.kernel.org>
Subject: Re: Intermittent SATA failures ("link offline, clearing class 1 to NONE")
Date: Mon, 21 Dec 2009 13:50:15 +0900 [thread overview]
Message-ID: <4B2EFE87.6000206@kernel.org> (raw)
In-Reply-To: <1261167192-sup-3861@utwig>
Hello,
On 12/19/2009 08:26 AM, Alex Vandiver wrote:
> On 12/03/2009 09:19 AM, Tejun Heo wrote:
>> 1. Change sata_deb_timing_hotplug to sata_deb_timing_long in
>> ata_piix.c::piidx_sidpr_hardreset() and see whether it solves the
>> problem?
>
> Nope -- in fact, _three_ of the drives failed to come up once, with
> this change.
Wow, that's unexpected. Can you please post log of this with the
debugging patch applied?
>> 2. Switch the controller into ahci mode in BIOS if possible and see
>> whether the problem goes away.
>
> Sadly, the BIOS doesn't have an option for this.
Ah... that's sad.
>> 3. Try kernel parameter "libata.force=nohrst" and see whether it makes
>> any difference.
>
> I wasn't able to replicate the problem with this kernel parameter.
> dmesg for such a boot is attached.
Alright, thanks for verifying.
>> 4. You can tell libata to reset the port by running the following command.
>>
>> echo "- - -" > /sys/class/scsi_host/hostN/scan
>>
>> N would be 0 or 1 on your configuration. Can you please run the
>> above command repeatedly and see whether it triggers a reset
>> failure? If so, the above will be far more convenient way to test
>> than rebooting repeatedly.
>
> I wasn't able to get this to fail, sadly. If the boot _had_ failed,
> however, this technique did bring the drive online.
Hmmm... interesting. So, the boot time probing is somehow different
from probing initiated by manual scan (they both use hardreset). Can
you please post log of manual scans with debug patch applied?
Thanks.
--
tejun
next prev parent reply other threads:[~2009-12-21 4:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-12 19:43 Intermittent SATA failures ("link offline, clearing class 1 to NONE") Alex Vandiver
2009-12-01 6:04 ` Tejun Heo
2009-12-01 7:37 ` Alex Vandiver
2009-12-01 8:12 ` Tejun Heo
2009-12-01 8:31 ` Tejun Heo
2009-12-01 22:02 ` Alex Vandiver
2009-12-02 1:43 ` Tejun Heo
2009-12-02 17:45 ` Alex Vandiver
2009-12-03 0:19 ` Tejun Heo
2009-12-03 0:42 ` Tejun Heo
2009-12-18 23:26 ` Alex Vandiver
2009-12-21 4:50 ` Tejun Heo [this message]
2009-12-21 19:13 ` Alex Vandiver
2009-12-22 0:06 ` Tejun Heo
[not found] <r2qf7a305db1004270252le438bd88vb3ca3d9b753651a9@mail.gmail.com>
[not found] ` <g2lf7a305db1004270255t5d50de0n1dc21fdc7b191d92@mail.gmail.com>
2010-05-17 9:52 ` 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=4B2EFE87.6000206@kernel.org \
--to=tj@kernel.org \
--cc=alex@chmrr.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).