Featured Articles

LG G Watch R ships in two weeks

LG G Watch R ships in two weeks

The LG G Watch R, the first Android Wear watch with a truly round face, is coming soon and judging by…

More...
LG unveils NUCLUN big.LITTLE SoC

LG unveils NUCLUN big.LITTLE SoC

LG has officially announced its first smartphone SoC, the NUCLUN, formerly known as the Odin.

More...
Microsoft moves 2.4 million Xbox Ones

Microsoft moves 2.4 million Xbox Ones

Microsoft has announced that it move 2.4 million consoles in fiscal year 2015 Q1. The announcement came with the latest financial…

More...
Gainward GTX 970 Phantom previewed

Gainward GTX 970 Phantom previewed

Nvidia has released two new graphics cards based on its latest Maxwell GPU architecture. The Geforce GTX 970 and Geforce GTX…

More...
EVGA GTX 970 SC ACX 2.0 reviewed

EVGA GTX 970 SC ACX 2.0 reviewed

Nvidia has released two new graphics cards based on its latest Maxwell GPU architecture. The Geforce GTX 970 and Geforce GTX…

More...
Frontpage Slideshow | Copyright © 2006-2010 orks, a business unit of Nuevvo Webware Ltd.
Monday, 04 March 2013 13:07

Intel Haswell has USB 3.0 issues

Written by Slobodan Simic



Not serious as Cougar Point SATA bug

According to a report over at Hardware.info that managed to get their hands on an internal Intel document, it appears that Intel's Haswell platform might have a problem with its USB 3.0 host controller.

Although it is not as serious as the Cougar Point SATA 3Gbps bug, the USB 3.0 controller on Haswell platform will have issues with the S3 sleep mode and devices that are connected via USB 3.0 port. Apparently, when waking from S3 sleep, applications that are accesssing the data from, for example, USB 3.0 storage device might freeze and force the user to reopen them manually.

Thankfully, the bug will be more of a nuisance rather than a problem as any loss of data is excluded. Intel does not plan to delay the launch and it is still scheduled for mid-2013, according to an Intel representative comment for Hardware.info. Intel is apparently still resarching what other consequences this issue could possibly have and plans to resolve the problem in a future CPU stepping.

You can check out more here.


Last modified on Tuesday, 05 March 2013 22:56
blog comments powered by Disqus

 

Facebook activity

Latest Commented Articles

Recent Comments