linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: fengxiangjun <fengxiangjun@neusoft.com>
To: Tejun Heo <tj@kernel.org>
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 15:45:11 +0800 (CST)	[thread overview]
Message-ID: <alpine.LNX.2.00.0912241535340.1682@darkstar.example.net> (raw)
In-Reply-To: <4B331957.7030906@kernel.org>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1879 bytes --]


Hi, I can not capture the full failing boot log.
The kernel panic, and shift + pageup does not work. 

With output to serial console, the problem goes away.

I think with an initrd, I can reproduce the problem and capture the full 
failing boot log.
But with an initrd, there's no problem. Every thing works fine.

Thanks.

On Thu, 24 Dec 2009, Tejun Heo wrote:

> 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
> 
---------------------------------------------------------------------------------------------------
Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s) 
is intended only for the use of the intended recipient and may be confidential and/or privileged of 
Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication is 
not the intended recipient, unauthorized use, forwarding, printing,  storing, disclosure or copying 
is strictly prohibited, and may be unlawful.If you have received this communication in error,please 
immediately notify the sender by return e-mail, and delete the original message and all copies from 
your system. Thank you. 
---------------------------------------------------------------------------------------------------

  reply	other threads:[~2009-12-24  7:43 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 [this message]
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=alpine.LNX.2.00.0912241535340.1682@darkstar.example.net \
    --to=fengxiangjun@neusoft.com \
    --cc=hancockrwd@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@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).