linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
To: linux-ide@vger.kernel.org
Subject: Re: unexpected downspeed of AHCI controller on Intel    Seaburg 5400
Date: Tue, 18 Nov 2008 20:04:42 -0600	[thread overview]
Message-ID: <4923743A.2050903@shaw.ca> (raw)
In-Reply-To: <6.2.5.6.2.20081118154009.01c8a2d0@binnacle.cx>

starlight@binnacle.cx wrote:
> [prior incomplete message was sent accidently]
> 
> Have a relatively recent HP DL160 G5 incorporating the 
> Seaburg 5400 chipset.  Appears the 5400 is a MCM including
> a 631xESB/632xESB I/O controller.
> 
> Running kernel 2.6.27.1.  Latest HP BIOS.
> 
> Strangely the SATA controller seems to be reporting that
> it can only run at 1.5 Gbps instead of 3 Gbps.
> 
> ahci 0000:00:1f.2: version 3.0
> ahci 0000:00:1f.2: PCI INT B -> GSI 19 (level, low) -> IRQ 19
> ahci 0000:00:1f.2: AHCI 0001.0100 32 slots 6 ports 1.5 Gbps 0x3f impl SATA mode

That comes right out of the controller's registers, so presumably it is 
telling the truth. That particular value is only used for display, 
though - the actual negotiated speed is determined from other registers. 
So if the controller says it can only do 1.5 and the drives all 
negotiated at 1.5, well, that's likely all it can do..

> ahci 0000:00:1f.2: flags: 64bit ncq pm led slum part
> ahci 0000:00:1f.2: setting latency timer to 64
> 
> Looked at the AHCI specification and Intel datasheets for both 
> the 5400 and the 631xESB/632xESB.  The latter shows the register 
> but does not include 3 Gpbs in the enumeration.  SATA-II support 
> is stated in general for the device however.  The SATA links all 
> are reported as running at 1.5 Gbps.

It doesn't necessarily mean anything that it supports SATA II, that's 
just a revision of the spec and it defines support for 3 Gbps, but 
doesn't require it.

> 
> Definitely did pull the rate-limit jumpers off the Seagate
> ES.2 drives.
> 
> details:
> 
> http://binnacle.cx/file/ahci_seaburg_downspeed_dmesg.txt
> http://binnacle.cx/file/ahci_seaburg_downspeed_dmidecode.txt
> http://binnacle.cx/file/ahci_seaburg_downspeed_hdparm-I.txt
> http://binnacle.cx/file/ahci_seaburg_downspeed_lspci-vv.txt
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ide" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 


  reply	other threads:[~2008-11-19  2:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-18 20:44 unexpected downspeed of AHCI controller on Intel Seaburg 5400 starlight
2008-11-19  2:04 ` Robert Hancock [this message]
2008-11-19  2:06   ` starlight
2008-11-24  5:18     ` Tejun Heo
2008-11-24  5:32       ` starlight
2008-11-24  5:40         ` Tejun Heo
  -- strict thread matches above, loose matches on Subject: below --
2008-11-18 20:22 starlight

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=4923743A.2050903@shaw.ca \
    --to=hancockr@shaw.ca \
    --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).