"In the document, Intel purportedly informs manufacturers that
BTW: Doesn't anyone find it strange that Intel considers it ok to release Haswell with such a hardware bug?
Have you actualy read the article before downplaying it as a rumour
because it doesnt suit your usual Intel magnificencing?..
They say that they did read in official docs...
This could cost Intel 10's of millions of dollars. Maybe 100's of millions of dollars. 10's of 100's of millions of dollars. 100's of 10's of millions of dollars.
Oh no! This horrible bug might force slobs like Dennis Nedry to manage their peripherals. What a crime.
Mumak said:It's not the CPU, but the chipset (Lynx Point). And the problem doesn't occur on all USB3 devices, only certain ones depending on the level and magnitude of a signal during wake up from U3.
Not at all. Processors ship with errata. Impressively large lists of errata. Intel will issue a microcode fix before Haswell even ships and this will be the only time anyone ever hears of it.
This, though I suspect most people will ignore your post and keep arguing about this relative non-issue.
What is a microcode fix?Not at all. Processors ship with errata. Impressively large lists of errata. Intel will issue a microcode fix before Haswell even ships and this will be the only time anyone ever hears of it.
What is a microcode fix?
Isn't the production stepping already out?Depends if this a bug with an pre-production stepping that they're sending out to partners for validation/review which will be fixed in a production stepping.
Isn't the production stepping already out?
Isn't the production stepping already out?
Production stepping of what? Note that the latest info is that the HW bug is in the chipset (Lynx Point) and not the CPU (Haswell).
Virtually everything short of the 6 series degradation bug can be fixed with a microcode workaround. There have been USB issues in the past and that's exactly how they were dealt with.But where did you read that this can be fixed with a microcode fix? Not everything can be fixed that way you know...
Isn't the production stepping already out?
That's not what it said though. It says the issue could make applications relying on USB 3.0 to freeze when resuming from S3. That's a whole different issue from the device itself not awakening altogether.
Now that I think about it, perhaps it is a non-issue. How many people expect video to start playing as soon as you awake your computer? And out of that only when the video is contained in a USB 3.0 device?
It takes two months to manufacture a chip and by now
they have a few millions at most.