mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: fengxiangjun <fengxiangjun@neusoft.com>
To: Robert Hancock <hancockrwd@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.32.2 SATA link detect failed, 2.6.32.1 works fine
Date: Tue, 22 Dec 2009 09:02:57 +0800 (CST)	[thread overview]
Message-ID: <alpine.LNX.2.00.0912220859060.1686@darkstar.example.net> (raw)
In-Reply-To: <4B30134C.1050609@gmail.com>


Yeah, running 2.6.32.1 now, no problem.

dmesg shows:

ata1.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

When booting 2.6.32.2 with the same config, I get

ata1.00: SATA link down (SStatus 0 SControl 301)

Weird.

On Mon, 21 Dec 2009, Robert Hancock wrote:

> On 12/21/2009 05:12 AM, fengxiangjun wrote:
> > 
> > Hi,
> > 
> > after upgrading to 2.6.32.2,
> > with the attached config,
> > kernel booting always(just tried 10+ times) failed at:
> > 
> > ata1.00: SATA link down (SStatus 0 SControl 301)
> > ...
> > VFS: Cannot open root device ...
> 
> There were no libata changes in 2.6.32.2 that should have affected this. Are
> you sure the .config is unchanged? Have you rechecked that 2.6.31.1 still
> works?
> 
---------------------------------------------------------------------------------------------------
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-22  1:00 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-21 11:12 fengxiangjun
2009-12-22  0:31 ` Robert Hancock
2009-12-22  1:02   ` fengxiangjun [this message]
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
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.0912220859060.1686@darkstar.example.net \
    --to=fengxiangjun@neusoft.com \
    --cc=hancockrwd@gmail.com \
    --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

Powered by JetHome