linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Paul Check <paul@thechecks.ca>
Cc: linux-ide@vger.kernel.org
Subject: Re: Intermittent SATA link down SStatus 0
Date: Thu, 15 Jul 2010 11:20:03 +0200	[thread overview]
Message-ID: <4C3ED2C3.9050907@kernel.org> (raw)
In-Reply-To: <6cb5020f769580a1f431ed5bb8709b6a.squirrel@thechecks.ca>

Hello,

On 07/15/2010 02:43 AM, Paul Check wrote:
> Ok, well we didn't have to wait long. Once again one of my drives failed
> to appear. This time it was a different drive than the times before.
>
> I have attached the output from dmesg. Can you tell me from this output
> what the problem is?

SStatus and SControl are behaving erratically.  I'm not yet sure why
that's happening yet.

[    2.562157] ata4.01: SATA link up <unknown> (SStatus 300 SControl 123)

Hmm... it looks like SStatus and SControl are swapped here.  Maybe
there's a race condition in SIDPR code.  I'll look into it a bit more.

Thanks.

-- 
tejun

  reply	other threads:[~2010-07-15  9:20 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-21 15:57 Intermittent SATA link down SStatus 0 Paul Check
2010-01-21 16:28 ` Paul Check
2010-01-21 16:35 ` Paul Check
2010-01-21 16:49 ` Jeff Garzik
2010-01-21 16:55   ` Paul Check
2010-01-21 17:11 ` Alan Cox
2010-01-21 17:24   ` Paul Check
2010-01-21 17:36     ` Paul Check
2010-01-21 19:24 ` Paul Check
2010-01-21 21:08   ` Paul Check
2010-01-25  5:06 ` Tejun Heo
2010-02-05  3:29   ` Tim
2010-02-09  5:32     ` Paul Check
2010-07-12 16:32       ` Paul Check
2010-07-12 16:36         ` Paul Check
2010-07-14 12:26           ` Tejun Heo
2010-07-14 17:58             ` Paul Check
2010-07-14 23:36               ` Tejun Heo
2010-07-15  0:43                 ` Paul Check
2010-07-15  9:20                   ` Tejun Heo [this message]
2010-07-15  9:29                     ` Tejun Heo
2010-07-15 17:06                       ` Paul Check

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=4C3ED2C3.9050907@kernel.org \
    --to=tj@kernel.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=paul@thechecks.ca \
    /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).