From: "Paul Check" <paul@thechecks.ca>
To: Tejun Heo <tj@kernel.org>
Cc: Paul Check <paul@thechecks.ca>, linux-ide@vger.kernel.org
Subject: Re: Intermittent SATA link down SStatus 0
Date: Wed, 14 Jul 2010 13:58:10 -0400 [thread overview]
Message-ID: <0d9ccbbb9ed0fb46dc9497888cd92c6e.squirrel@thechecks.ca> (raw)
In-Reply-To: <4C3DACFF.2060504@kernel.org>
I applied your patch to the 2.6.34 kernel, and on my very first reboot had
a drive missing. What information do you want? Just /var/log/messages?
I don't want to keep rebooting forever. Was this patch supposed to fix the
problem, or just give you information to debug? Is the problem even known?
Regards, Paul
> Hello,
>
> On 07/12/2010 06:36 PM, Paul Check wrote:
>>> Tejun & Co:
>>>
>>> I have finally upgraded to the 2.6.34 kernel, and I am still having
>>> problems with some of my drives not coming up some of the time
>>> (different
>>> drives, at different times, never more than one).
>>>
>>> Here are some lines from /var/log/messages on the most recent boot
>>> below.
>>> Do you have any suggestions for this? I'm getting tired of having to
>>> reconstitute my raid 30-50% of the time, and will try anything to see
>>> if
>>> it fixes. Note the "link up (unknown)" and "link down" lines. I don't
>>> know
>>> what should appear, but I have 4 hard drives and one optical drive
>>> plugged
>>> into 5 of the 6 SATA ports on the board.
> ...
>>> Jul 12 12:25:22 min kernel: [ 2.078489] ata2.01: SATA link up
>>> <unknown>
>>> (SStatus 300 SControl 123)
>
> Hmm, yeah, it seems like SCR access via SIDPR is more flaky than
> covered by the previous commit. There's another thread where similar
> problem is being debugged. Can you please do the following? I'm
> attaching patch here too.
>
> http://thread.gmane.org/gmane.linux.kernel/1005983/focus=46749
>
> Thanks.
>
> --
> tejun
>
next prev parent reply other threads:[~2010-07-14 17:58 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 [this message]
2010-07-14 23:36 ` Tejun Heo
2010-07-15 0:43 ` Paul Check
2010-07-15 9:20 ` Tejun Heo
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=0d9ccbbb9ed0fb46dc9497888cd92c6e.squirrel@thechecks.ca \
--to=paul@thechecks.ca \
--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).