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.
Politics : Formerly About Advanced Micro Devices

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: Tenchusatsu who wrote (81794)12/2/1999 5:54:00 PM
From: Petz  Read Replies (1) of 1572218
 
<A much more serious Coppermine bug than "boot hang.">

Tench: Relax, Petz. If there wasn't a workaround already implemented for this bug, it would indeed have been deemed
much more serious than Dell's "boot hang."

If you want to get a little more technical, look at the description of the bug: "Snoop Request May Cause DBSY#
hang." Snoop requests happen all the time on the FSB, even on single-processor systems, although multi-processor systems exhibit a higher amount of such snoop traffic. There is no way on earth that a bug of this severity would have escaped unnoticed until now, or else owners of Coppermine-based workstations would have experienced on the order of one system crash per day.

Tenchusatsu

Exactly my point!
Let me get this straight, Tenchusatsu. Your argument is that, because the bug is so serious, it must not be serious.

Then you argue that there "must be a workaround," when Intel itself said a month ago, that a BIOS fix is POSSIBLE, but in the next month did not implement such a BIOS fix.
OCTOBER ERRATA: "BIOS fix is possible"
NOVEMBER ERRATA: "BIOS fix is possible", i.e., no change.

NO BIOS FIXES YET, THE BUG IS STILL THERE.

Petz
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext