linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robert Hancock <hancockrwd@gmail.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Marc Bowes <marcbowes@gmail.com>, linux-ide@vger.kernel.org
Subject: Re: SATA: link online but device misclassified
Date: Thu, 18 Jun 2009 19:38:16 -0600	[thread overview]
Message-ID: <4A3AEC08.4060507@gmail.com> (raw)
In-Reply-To: <1245165697.3965.40.camel@mulgrave.site>

On 06/16/2009 09:21 AM, James Bottomley wrote:
> On Tue, 2009-06-16 at 17:03 +0200, Marc Bowes wrote:
>> Sorry to bother, but this is really bugging me! I can't seem to find anybody
>> else with the same problem. What steps should I be taking to figure this
>> out? I'm thinking I should be trying other kernel versions and/or plugging
>> drives in different places. I don't think the motherboard is faulty, and I
>> seem to be getting good speeds (~70mbs) to all four drives.
>
> Well, those are on the AHCI built in controller. The one with the slow
> response is the empty JMicron 20360/20363.  But why this should be so,
> I've no idea ... it looks like the AHCI driver can't tell the phys are
> empty for some reason, which could be due to many things.

I would suspect it's a hardware problem that we can't do much about.. 
For some reason the controller is reporting the SATA link is online at 
3Gbps when there's actually nothing connected. We try to repeatedly 
reset the "device" as it doesn't respond properly, until we finally give up.

Can you disable that JMicron controller in the BIOS somehow?

  parent reply	other threads:[~2009-06-19  1:37 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-11  0:15 SATA: link online but device misclassified Marc Bowes
2009-06-11  4:27 ` Robert Hancock
2009-06-11  9:31   ` Marc Bowes
2009-06-11 19:01     ` James Bottomley
2009-06-11 19:32       ` Marc Bowes
     [not found]         ` <cfa4e840906160759m31db333cr555104ca0e3c6255@mail.gmail.com>
2009-06-16 15:03           ` Marc Bowes
2009-06-16 15:21             ` James Bottomley
     [not found]               ` <cfa4e840906160946qc998331p308624ac10f15060@mail.gmail.com>
     [not found]                 ` <1245171448.3965.46.camel@mulgrave.site>
2009-06-16 18:13                   ` Marc Bowes
2009-06-19  1:38               ` Robert Hancock [this message]
2009-06-19  4:00                 ` Tejun Heo
2009-06-19  9:38                   ` Marc Bowes
2009-06-19  9:44                     ` Marc Bowes
2009-06-20 12:34                     ` Tejun Heo
2009-06-20 13:13                       ` Marc Bowes
2009-06-25 13:54                         ` Tejun Heo
2009-06-29 10:20                         ` Tejun Heo
2009-07-01  8:07                           ` Marc Bowes
2009-07-01 23:31                             ` Tejun Heo
2009-07-02  9:22                               ` Marc Bowes
2009-07-08  4:14                                 ` Tejun Heo
     [not found] <cfa4e840906101331q71532d72v5361a72e9b77ce63@mail.gmail.com>
2009-06-10 20:34 ` Matthew Wilcox
2009-06-10 20:40   ` Marc Bowes

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=4A3AEC08.4060507@gmail.com \
    --to=hancockrwd@gmail.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=marcbowes@gmail.com \
    /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).