From: Tejun Heo <tj@kernel.org>
To: fengxiangjun <fengxiangjun@neusoft.com>
Cc: Robert Hancock <hancockrwd@gmail.com>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: 2.6.32.2 SATA link detect failed, 2.6.32.1 works fine
Date: Mon, 28 Dec 2009 19:02:46 +0900 [thread overview]
Message-ID: <4B388246.3040100@kernel.org> (raw)
In-Reply-To: <alpine.LNX.2.00.0912260919490.1729@darkstar.example.net>
Hello,
On 12/26/2009 10:25 AM, fengxiangjun wrote:
>> Can you please try this one? Retry logic was wrong in the original
>> patch. With this patch, you should see one "link resume succeeded
>> after %d retries" message when the original kernel would have failed
>> probe. Can you please test this patch and post boot log with such
>> message?
>
> Just reboot 3 times, and test STR, every thing works fine.
> And the 3 reboots have the same message:
>
> ata1.00: link resume succeeded after 1 retries
Cool, does it ever boot without the message?
--
tejun
next prev parent reply other threads:[~2009-12-28 10:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-21 11:12 2.6.32.2 SATA link detect failed, 2.6.32.1 works fine fengxiangjun
2009-12-22 0:31 ` Robert Hancock
2009-12-22 1:02 ` fengxiangjun
2009-12-22 1:08 ` Robert Hancock
2009-12-22 2:02 ` fengxiangjun
2009-12-23 8:55 ` Tejun Heo
2009-12-23 9:29 ` fengxiangjun
2009-12-23 12:02 ` Bjarke Istrup Pedersen
2009-12-24 1:21 ` fengxiangjun
2009-12-24 7:33 ` Tejun Heo
2009-12-24 7:45 ` fengxiangjun
2009-12-24 7:51 ` Tejun Heo
2009-12-24 7:58 ` fengxiangjun
2009-12-24 12:15 ` fengxiangjun
2009-12-24 12:40 ` Tejun Heo
2009-12-25 1:35 ` fengxiangjun
2009-12-25 13:39 ` Tejun Heo
2009-12-26 1:25 ` fengxiangjun
2009-12-28 10:02 ` Tejun Heo [this message]
2009-12-29 1:08 ` fengxiangjun
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=4B388246.3040100@kernel.org \
--to=tj@kernel.org \
--cc=fengxiangjun@neusoft.com \
--cc=hancockrwd@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.