I recently put together a new PC and thought I would share my journey through the medium of Flickr.
Anyone interested, link is below...
Jump to content
Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.Create Account How it Works
It’s Limited to 3Gbps Ports Only
Interestingly enough the problem doesn’t affect ports 0 & 1 on the 6-series chipset. Remember that Intel has two 6Gbps ports and four 3Gbps ports on P67/H67, only the latter four are impacted by this problem.
If you’re a current Sandy Bridge user and want to be sure you don’t have any problems until you can get replacement hardware, stick to using the 6Gbps ports on your board (which should be the first two ports).
The Failure Manifested
I asked Intel how we’d know if we had a failure on our hands. The symptoms are pretty simple to check for. Intel says you’d see an increase in bit error rates on a SATA link over time. Transfers will retry if there is an error but eventually, if the error rate is high enough, you’ll see reduced performance as the controller spends more time retrying than it does sending actual data.
Ultimately you could see a full disconnect - your SATA drive(s) would not longer be visible at POST or you’d see a drive letter disappear in Windows.
The problem in the chipset was traced back to a transistor in the 3Gbps PLL clocking tree. The aforementioned transistor has a very thin gate oxide, which allows you to turn it on with a very low voltage. Unfortunately in this case Intel biased the transistor with too high of a voltage, resulting in higher than expected leakage current. Depending on the physical characteristics of the transistor the leakage current here can increase over time which can ultimately result in this failure on the 3Gbps ports. The fact that the 3Gbps and 6Gbps circuits have their own independent clocking trees is what ensures that this problem is limited to only ports 2 - 5 off the controller.
You can coax the problem out earlier by testing the PCH at increased voltage and temperature levels. By increasing one or both of these values you can simulate load over time and that’s how the problem was initially discovered. Intel believes that any current issues users have with SATA performance/compatibility/reliability are likely unrelated to the hardware bug.
One fix for this type of a problem would be to scale down the voltage applied across the problematic transistor. In this case there’s a much simpler option. The source of the problem is actually not even a key part of the 6-series chipset design, it’s remnant of an earlier design that’s no longer needed. In our Sandy Bridge review I pointed out the fair amount of design reuse that was done in creating the 6-series chipset. The solution Intel has devised is to simply remove voltage to the transistor. The chip is functionally no different, but by permanently disabling the transistor the problem will never arise.
To make matters worse, the problem was inserted at the B-stepping of the 6-series chipsets. Earlier steppings (such as what we previewed last summer) didn’t have the problem. Unfortunately for Intel, only B-stepping chipsets shipped to customers. Since the fix involves cutting off voltage to a transistor it will be fixed with a new spin of metal and you’ll get a new associated stepping (presumably C-stepping?).
0 members, 0 guests, 0 anonymous users
Community Forum Software by IP.Board
Licensed to: Geeks to Go, Inc.