starlight@xxxxxxxxxxx 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@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
