This story has been making the rounds over the weekend, and it's a little disconcerting. According to Hardware.info, which cites both a "reliable source" and an "internal document" from an Intel partner, systems based on Intel's next-gen Haswell processors have a problem with USB 3.0 device support.
In the document, Intel purportedly informs manufacturers that a system with Haswell inside, when waking from S3 sleep mode, will experience issues with devices connected through USB 3.0. For example this would result in blank pages displaying in Acrobat Reader PDFs or video playback stopping, rather than continuing.
Haswell isn't due out for several months, though, so surely the problem will be resolved then... right?
Well, maybe not. Hardware.info says a "future processor stepping" will take care of the problem, but Intel has made its partners agree to "accept this issue" before receiving shipments of CPUs. In other words, it sounds like the first wave of Haswell systems to hit the market might be affected by this issue.
If the problem is a recent discovery, that may be the only way around a delay. Intel has set a mid-year release time frame for Haswell's debut, and the desktop release is expected to take place on June 2 at the Computex trade show in Taipei. That would leave barely three months for a re-spin, validation, and enough shipments to ensure PC makers have sufficient volume for the launch—likely far too little time.
|Samsung's Portable SSD T3 reviewed||7|
|TR BBQ Day Shortbread||24|
|Watch the "second-10th" TR BBQ live in 360 degrees right now||11|
|G.Skill hooks up the TR BBQ with some giveaway goodies||12|
|We threw a Minecraft party to test Samsung's Gear VR headset||9|
|Deals of the week: cheap solid-state storage and more||23|
|Sapphire Nitro+ Radeon RX 480 hot-rods Polaris 10||63|
|AMD gets back in the black with its second-quarter financials||42|
|Nvidia unveils a Pascal-powered Titan X with 11 TFLOPS on tap||195|
|I'll...just review the thin air on my desk where a GTX 1060 would fit, since that's what we have.||+116|