From: Alex Vandiver <alex@chmrr.net>
To: Tejun Heo <tj@kernel.org>
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 14:13:59 -0500 [thread overview]
Message-ID: <1261422681-sup-4043@utwig> (raw)
In-Reply-To: <4B2EFE87.6000206@kernel.org>
At Sun Dec 20 23:50:15 -0500 2009, Tejun Heo wrote:
> Wow, that's unexpected. Can you please post log of this with the
> debugging patch applied?
I've only been able to replicate this once, and I didn't manage to
save its dmesg, sadly. I'll see if I can get it to crop up again,
though.
> 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?
The output of a manual scan is:
[ 255.236938] ata1.00: hard resetting link
[ 255.465422] ata1.00: XXX debounce start, SStatus=123
[ 257.551239] ata1.00: XXX debounce done, SStatus=123, DET stable for 2090 msecs
[ 257.551246] ata1.01: hard resetting link
[ 257.780776] ata1.01: XXX debounce start, SStatus=123
[ 259.866589] ata1.01: XXX debounce done, SStatus=123, DET stable for 2090 msecs
[ 260.026328] ata1.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 260.026342] ata1.01: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 260.087511] ata1.00: configured for UDMA/133
[ 260.127736] ata1.01: configured for UDMA/133
[ 260.127740] ata1: EH complete
- Alex
--
Networking -- only one letter away from not working
next prev parent reply other threads:[~2009-12-21 19:14 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
2009-12-21 19:13 ` Alex Vandiver [this message]
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=1261422681-sup-4043@utwig \
--to=alex@chmrr.net \
--cc=linux-ide@vger.kernel.org \
--cc=tj@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).