SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Technology Stocks : Advanced Micro Devices - Moderated (AMD) -- Ignore unavailable to you. Want to Upgrade?


To: Windsock who wrote (244061)12/6/2007 6:04:05 PM
From: Dan3Respond to of 275872
 
Re: Do you plan to install the BIOS fix for your Barcelona systems and take the performance hit similar to the one seen by Core 2 / Xeon buyers who had to install Intel's patch?

I've requested the new bios from Tyan (they don't have it available yet) and will install it the day it becomes available.

Us early adopters deal with these issues. They're a fact of life.

Intel has released a BIOS patch for Windows machines running Core 2 and Xeon 3000/5000 chips that addresses potential unpredictable system behavior.

The update is recommended for users running an Intel Core2 Duo E4000 and E6000, Intel Core2 Quad Q6600, Intel Core2 Extreme X6800 and QX6700, Dual-COre Intel Xeon 5100 and Quad-Core Intel Xeon 5300.

HP lists the "microcode reliability update" as a critical fix that can "leave a workstation in an unstable condition, which could potentially result in system lockups or failures, or data corruption or loss." HP reports the issue was found in a synthetic test environment during quality control testing.

Symptoms include mouse and keyboard failure, Windows Blue Screen of Death, and Linux generating a kernel panic.

While news of the patch has circulated suggesting catastrophic importance, Intel spokesman Nick Knupffer said the probability of encountering an issue is low, and has not been reported in any commercial situations or real-world environments.

channelregister.co.uk



To: Windsock who wrote (244061)12/6/2007 7:03:38 PM
From: PetzRead Replies (1) | Respond to of 275872
 
Windsock, has one person, anywhere, ever demonstrated a computational error caused by this erratum?

Has one person even demonstrated a crash?

If the answer to Q1 is no, then Dan has no reason to fix the BIOS if his systems aren't crashing, does he.

That was a statement, not a question.

Petz