linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jan Beulich" <jbeulich@novell.com>
To: Tejun Heo <htejun@gmail.com>
Cc: jgarzik@pobox.com, linux-ide@vger.kernel.org
Subject: Re: AHCI driver preferring nr_ports over port map
Date: Tue, 05 Feb 2008 07:47:07 +0000	[thread overview]
Message-ID: <47A8228B.76E4.0078.0@novell.com> (raw)
In-Reply-To: <47A71538.50803@gmail.com>

>Yes, we can be more smart if necessary.  I don't know.  The hardware is
>clearly violating the spec which requires those two values to agree.

So are you saying the ESB2 spec is violating a higher level spec? I know
almost nothing about AHCI, so please forgive that question...

>What status values are you seeing?  Hardware vendors usually don't get
>n_ports wrong from the start, they probably have forgotten to decrement
>it by one when one of the ports is plugged for some reason.  I bet the
>silicon for the port is there and reporting offline PHY, right?

This is output from our SLE10SP2 kernel, the output is similar for others:

<6>scsi2 : ahci
<6>ata3: SATA link down (SStatus 0 SControl 300)
<6>scsi3 : ahci
<6>ata4: SATA link down (SStatus 0 SControl 300)
<6>scsi4 : ahci
<6>ata5: SATA link down (SStatus 4 SControl 300)
<6>scsi5 : ahci
<6>ata6: SATA link down (SStatus 0 SControl 0)

Even the message relating to ata5 seems a little dubious to me, as it's
not in sync with what the other unused ports say (and also not in sync
with what I see on other boxes - SStatus is always 0 for such ports).

Jan


  reply	other threads:[~2008-02-05  7:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-04 13:24 AHCI driver preferring nr_ports over port map Jan Beulich
2008-02-04 13:38 ` Tejun Heo
2008-02-05  7:47   ` Jan Beulich [this message]
2008-02-05 12:21     ` Tejun Heo
2008-02-05 12:40       ` Jan Beulich
2008-02-05 13:17         ` Tejun Heo
2008-02-05 14:51           ` Jan Beulich
  -- strict thread matches above, loose matches on Subject: below --
2008-02-04 13:10 Jan Beulich
2008-02-04 13:16 ` Tejun Heo
2008-02-01 15:12 Jan Beulich
2008-02-02  8:16 ` Tejun Heo

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=47A8228B.76E4.0078.0@novell.com \
    --to=jbeulich@novell.com \
    --cc=htejun@gmail.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@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).