Re: unexpected downspeed of AHCI controller on Intel Seaburg 5400

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Thank you for explaining how it works.  Have resigned to living 
with 1.5G.  A reason exists to run the ES.2s at their full 
sequential 100 Mbytes/sec (800 Mbits/sec), and I had hoped that 
lowering the latency on the link might squeeze a bit more 
performance.  But 1.5 is good enough.



At 14:18 11/24/2008 +0900, Tejun Heo wrote:
>starlight@xxxxxxxxxxx wrote:
>> Is it possible for the BIOS to tell the chip to not negogiate 
>> above 1.5 Gbps?  I'm wondering if HP might have done this to 
>> prevent the bug below from happening.  If so it would be
>> nice for the driver to put it back to 3 Gbps.
>
>The standard way to put that limit is to use SControl but it isn't doing
>that, as far as ahci is concerned, it's free to negotiate any speed but
>is negotiating 1.5Gbps.  Maybe they capped using some hidden register to
>workaround the erratum.  At any rate, it doesn't really matter unless
>you're gonna hang multiple devices to a single port using PMP.
>
>Thanks.
>
>-- 
>tejun

--
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

[Index of Archives]     [Linux Filesystems]     [Linux SCSI]     [Linux RAID]     [Git]     [Kernel Newbies]     [Linux Newbie]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Samba]     [Device Mapper]

  Powered by Linux