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: Thu, 24 Dec 2009 16:33:43 +0900 [thread overview]
Message-ID: <4B331957.7030906@kernel.org> (raw)
In-Reply-To: <alpine.LNX.2.00.0912231719440.1694@darkstar.example.net>
On 12/23/2009 06:29 PM, fengxiangjun wrote:
>
> Hi,
>
> with this patch, the problem still exists.
>
> ata1.01: XXX debounce start, SStatus=4
> ata1.01: XXX debounce done, SStatus=4, DET stable for 520 msecs
> ata1.00: SATA link down (SStatus 0 SControl 301)
> ata1.01: SATA link down (SStatus 0 Scontrol 300)
> ...
> VFS; cannot open root device ...
>
> The kernel just panic, and I can't see what's the messege printing before
> that.
>
> So, I tried 'console=ttyS0 console=tty1'，full dmesg attached。
Can you please capture full failing log? In the attached log, ata1.00
is detected successfully.
Thanks.
--
tejun
next prev parent reply other threads:[~2009-12-24 7:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.LNX.2.00.0912211855460.1689@darkstar.example.net>
[not found] ` <4B30134C.1050609@gmail.com>
[not found] ` <alpine.LNX.2.00.0912220859060.1686@darkstar.example.net>
2009-12-22 1:08 ` 2.6.32.2 SATA link detect failed, 2.6.32.1 works fine 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 [this message]
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
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=4B331957.7030906@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 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).