I just got off the phone with Intel’s Steve Smith (VP and Director of Intel Client PC Operations and Enabling) and got some more detail on this morning’s 6-series chipset/SATA bug.

The Problem

Cougar Point (Intel’s 6-series chipsets: H67/P67) has two sets of SATA ports: four that support 3Gbps operation, and two that support 6Gbps operation. Each set of ports requires its own PLL source.

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?).

While Steve wouldn’t go into greater detail he kept mentioning that this bug was completely an oversight. It sounds to me like an engineer did something without thinking and this was the result. This is a bit different from my initial take on the problem. Intel originally characterized the issue as purely statistical, but the source sounds a lot more like a design problem rather than completely random chance.

It’s Notta Recall

Intel has shipped around 8 million 6-series chipsets since the launch at CES. It also committed to setting aside $700 million to deal with the repair and replacement of any affected chipsets. That works out to be $87.50 per chipset if there are 8 million affected chipsets in the market, nearly the cost of an entire motherboard. Now the funds have to cover supplying the new chipset, bringing in the affected motherboard and repairing it or sending out a new one. Intel can eat the cost of the chipset, leaving the $87.50 for shipping, labor and time, as well as any other consideration Intel provides the OEM with (here’s $5, don’t hate us too much). At the end of the day it seems like enough money to handle the problem. However Intel was very careful to point out that this is not a full blown recall. The why is simple.

If you have a desktop system with six SATA ports driven off of P67/H67 chipset, there’s a chance (at least 5%) that during normal use some of the 3Gbps ports will stop working over the course of 3 years. The longer you use the ports, the higher that percentage will be. If you fall into this category, chances are your motherboard manufacturer will set up some sort of an exchange where you get a fixed board. The motherboard manufacturer could simply desolder your 6-series chipset and replace it with a newer stepping if it wanted to be frugal.

If you have a notebook system with only two SATA ports however, the scenario is a little less clear. Notebooks don’t have tons of storage bays and thus they don’t always use all of the ports a chipset offers. If a notebook design only uses ports 0 & 1 off the chipset (the unaffected ports), then the end user would never encounter an issue and the notebook may not even be recalled. In fact, if there are notebook designs currently in the pipeline that only use ports 0 & 1 they may not be delayed by today’s announcement. This is the only source of hope if you’re looking for an unaffected release schedule for your dual-core SNB notebook.

Final Words

Intel maintains that Sandy Bridge CPUs are not affected, and current users are highly unlikely to encounter the issue even under heavy loads. So far Intel has only been able to document the issue after running extended testing at high temperatures (in a thermal chamber) and voltages. My recommendation is to try to only use ports 0 & 1 (the 6Gbps ports) on your 6-series motherboard until you get a replacement in place.

OEMs and motherboard manufacturers are going to be talking to Intel over the next week to figure out the next steps. Intel plans to deliver fixed silicon to its partners at the end of February, however it’ll still take time for the motherboard makers to turn those chips into products. I wouldn’t expect replacements until March at the earliest.

I maintain that the best gesture of goodwill on Intel’s part would be to enable motherboard manufacturers to replace P67/H67 motherboards with Z68 boards for those users who want them.



View All Comments

  • makercab - Tuesday, February 1, 2011 - link

    Here's a question. Just got the i7-2600 last week to build new unit. Still in box. Anyone know of a way to send it for replacement BEFORE installation? Reply
  • mapesdhs - Tuesday, February 1, 2011 - link

    Live in the UK and have an absolute 7-day right of return. ;D

  • valenti - Tuesday, February 1, 2011 - link

    I would suggest you just go ahead and build your system. Use the SATA6G ports first. If you need more than two, add a $20 expansion card for more SATA ports. Enjoy the system and when the replacement info comes out, worry about it then.

    I just picked up Sandy Bridge components last Friday. Assembled the system on Sunday. Intel can pry it from my cold, dead hands. It folds proteins like a demon.

    Why sit on your very fast parts for a month (realistically it will take that long for a new motherboard)? It is really a minor issue, now that we know what the problem is.
  • cbass64 - Tuesday, February 1, 2011 - link

    Why would you replace your 2600? Reply
  • Touche - Tuesday, February 1, 2011 - link

    If it's a transistor that fails and causes a problem, but it isn't important and not used anyway so the fix is to disable it, what makes it a problem if it "disables itself" by failing? Reply
  • dcollins - Tuesday, February 1, 2011 - link

    About a week ago, I ordered a Vostro 460 desktop with a new Sandy Bridge processor. When the news came out about the recall yesterday, I called Dell to see whether my order would be delayed. The tech told me that my expected shipping date had been postponed a week, but did not have any details about the recall. Then, my order unexpectedly shipped this morning.

    I guess Dell was not effected by the recall; maybe they were only using the SATA 6GB ports or maybe they were using the A stepping or maybe they just didn't care and shipped the broken chipset. Either way, I'm not going to take any chances: I am going to ensure that the two hard drives (one SSD) are installed on the 6GB sata ports. To make room, I will need to move the CD drive to one of the 3GB ports because it is used less so it should be less affected by the bug.
  • Squuiid - Tuesday, February 1, 2011 - link

    Having worked with Dell for years and years, I'm going with the latter, "they just didn't care and shipped the broken chipset."

    Dell suck:
  • JasperJanssen - Tuesday, February 1, 2011 - link

    Dell may suck, but so does every other vendor. Reply
  • banzaigtv - Wednesday, February 2, 2011 - link

    HP doesn't really suck. Their Pavilion PCs use quality parts and are built to last, not to mention energy-efficient (probably why they use 300W PSUs). If you order an SB unit from HP.com, the estimated build date will just be delayed until March 1 to allow HP time to receive the updated hardware. Reply
  • banzaigtv - Wednesday, February 2, 2011 - link

    That's weird. Dell has removed the XPS 8300 from its website and is not available for retail at electronics stores either. For those of you who have not ordered already, you can purchase the AMD-based XPS 7100 or Nehalem Core-based XPS 9100 though. Reply

Log in

Don't have an account? Sign up now